You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the keyword argument python_requires of setup() is not set, and thus it is assumed that this distribution is compatible with all Python versions.
However, I found the following code checking Python compatibility locally in zappa/__init__.py
I think it is a better way to declare Python compatibility by using the keyword argument python_requires than checking compatibility locally for some reasons:
Descriptions in python_requires will be reflected in the metadata
“pip install” can check such metadata on the fly during distribution selection, and prevent from downloading and installing the incompatible package versions.
If the user does not specify any version constraint, pip can automatically choose the latest compatible package version for users.
Way to improve:
modify setup() in setup.py, add python_requires keyword argument:
setup(…
python_requires=">=3.6, <3.10",
…)
Thanks for your attention.
Best regrads,
PyVCEchecker
The text was updated successfully, but these errors were encountered:
Currently, the keyword argument python_requires of setup() is not set, and thus it is assumed that this distribution is compatible with all Python versions.
However, I found the following code checking Python compatibility locally in zappa/__init__.py
I think it is a better way to declare Python compatibility by using the keyword argument python_requires than checking compatibility locally for some reasons:
Way to improve:
modify setup() in setup.py, add python_requires keyword argument:
Thanks for your attention.
Best regrads,
PyVCEchecker
The text was updated successfully, but these errors were encountered: