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
# Get the PyPI package info from the readmethis_directory=path.abspath(path.dirname(__file__))
withopen(path.join(this_directory, "README.md"), encoding="utf-8") asf:
long_description=f.read()
setup.py used a Python3-specific keyword argument encoding for the function open, which lead to installation failure of Inject in Python 2. And there is such a declaration.
classifiers=[
...
"Programming Language :: Python :: 3.7",
"Programming Language :: Python :: 3.8",
"Programming Language :: Python :: 3.9",
"Programming Language :: Python :: 3.10",
...
]
I guess you want to set python>=3.7. And I think it is a better way to declare Python compatibility by using the keyword argument python_requires
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.7",
…)
Thanks for your attention.
Best regrads,
PyVCEchecker
The text was updated successfully, but these errors were encountered:
Hello!
I noticed the code snippet in setup.py
setup.py used a Python3-specific keyword argument encoding for the function open, which lead to installation failure of Inject in Python 2. And there is such a declaration.
I guess you want to set python>=3.7. And I think it is a better way to declare Python compatibility by using the keyword argument python_requires
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: