Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add type-hinting to concurrent decorators. Bump to Python 3.9. #139

Merged
merged 1 commit into from
Nov 9, 2024

Conversation

emiliadecaudin
Copy link
Contributor

I've confirmed before submitting this pull request that all tests pass.

This pull request does two things:

  • It adds type-hinting, using generics, to the thread and process decorators in the concurrent sub-package. This allows users of this package to properly treat the output of a decorated function as a Future or ProcessFuture, respectively, instead of the type-checker treating the function signature as identical to the original function.
  • It increments the minimum supported Python version of this package from 3.6 to 3.9 in order to support the generic type-hinting. The version for the next release will have to be increased regardless given that dataclasses were introduced in 3.7, and I believe going further to 3.9 will still cover many users.

I am a big fan of this package and would be eager to help add more type-hinting for the rest of the package as well as adding mypy/ruff linting!

@JoaquimEsteves
Copy link

Big fan of this PR. However I'm against the bump to 3.9.

This is a library after all, the core functionality is not affected and so bumping will only harm users stuck on older python versions.

There is a way out of this, you could either split the types into a stub file or use typing_extensions like so:

from typing import TYPE_CHECKING:
if TYPE_CHECKING:
    # look ma. No runtime errors on older python!
    from typing_extensions import ...etc


def process(*args, **kwargs) -> Callable:
@overload
def process(func: Callable[[_P], _T]) -> Callable[[_P], common.ProcessFuture[_T]]: ...

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd recommend using the typing.ParamSpec here

@emiliadecaudin
Copy link
Contributor Author

Understood; I don't have experience writing type-safe code before 3.9 so I'm less familiar with how to write proper type hints before the changes introduced in that version. I'm at a conference right now but I will try to dive in after this week and test against 3.7.

@JoaquimEsteves
Copy link

Understood; I don't have experience writing type-safe code before 3.9 so I'm less familiar with how to write proper type hints before the changes introduced in that version. I'm at a conference right now but I will try to dive in after this week and test against 3.7.

I'm not a maintainer of this package. But I'd you'd like I can help out and make a PR targeting your branch.

@noxdafox
Copy link
Owner

noxdafox commented Sep 14, 2024

Hi @emiliadecaudin, thanks for your contribution!

I second @JoaquimEsteves feedback, although Python 3.8 is going EOL in October, it would be great to still support older versions as this module is used by quite few projects.

This does not mean we have to backport this feature in previous versions. We simply need to support the case in which an older Python interpreter is used.

As type hints are a non functional feature, we can definitely skip support for older Python versions. Just make this functionality optional. 😉

@@ -26,8 +26,9 @@ def __init__(self, msg, code=0):
super(ProcessExpired, self).__init__(msg)
self.exitcode = code

_T = TypeVar("_T")
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here you could do:

try:
    from typing import TypeVar
    _T = TypeVar("_T")
except ImportError:
    _T = "GenericType"

Have not tested it but it might be enough of a change to support old interpreters.

from concurrent.futures import CancelledError, TimeoutError

from pebble import common

_P = TypeVar("_P")
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as here.

As this logic is common for both process and thread decorators, I would place it into pebble.common.types and use it around so we don't clutter the whole code base with backwards compatible supporting logic (try/excepts etc...).

@@ -24,7 +24,7 @@ def package_version():
url="https://github.com/noxdafox/pebble",
packages=find_packages(exclude=["test"]),
long_description=open(os.path.join(CWD, 'README.rst')).read(),
python_requires=">=3.6",
python_requires=">=3.9",
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As said, let's try to support 3.6 until possible. Type hinting is not a functional feature hence it does not justify dropping backwards compatibility.

Keep in mind that we use semver here. Hence, by doing the above, we should bump Pebble version to 6.0.0. Not sure it's the right choice. 😄

@noxdafox
Copy link
Owner

noxdafox commented Oct 1, 2024

@emiliadecaudin are you planning to continue working on this? Otherwise I could merge and try to bring the backwards compatibility in myself. 🙂

@noxdafox
Copy link
Owner

noxdafox commented Nov 9, 2024

Merging this, I will finish the work. Thanks for your contribution @emiliadecaudin!

@noxdafox noxdafox merged commit 347be2c into noxdafox:master Nov 9, 2024
0 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants