GitPython wheel includes "py2" in filename, but doesn't support Python 2 #898
Description
Activity
2.1.12specifiesRequires-Python: >=3.0, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*2.1.11specifiesRequires-Python: >=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*The changelog however does not mention removal of
2.7support:Python 2.7 support was dropped in #312
Perhaps doing this in a patch version was a bit heavy handed?
BTW, python 2 support was kind of dropped in 2.1.11 7f08b77#diff-c276fc3c4df38382ec884e59657b869dR125 (when using a unicode branch/tag name that will fail)
@olivierlefloch I absolutely agree, and apologies, and I have just released
v2.1.13which returns python 2 support.I am trying to cut a new release
v3.0.0which removes python 2 support, if I can manage to figure out all the places to edit to make that happen. For now I don't know how to turn off thepy2.part in the whl filename, but I will keep trying 😅.Reacted by Santos Gallegos@Byron
I did a quick experiment on the tip of master, and it appears that if you updatesetup.cfgto[bdist_wheel] universal=0then the python tag will be just
py3instead ofpy2.py3and the resulting wheel filename isGitPython-2.1.13-py3-none-any.whl. Assuming you are building with Python 3.You would still want to update
setup.pyas you did before, to changepython_requiresandclassifiers.- ghost added a commit that references this issue
on Aug 11, 2019
I'm not sure the proper conventions for using wheel to distribute packages, but the current artifact on PyPI is called
GitPython-2.1.12-py2.py3-none-any.whl, implying support for Python 2. Although it's true that the "Meta" section on PyPI specifies Python >=3.0.Is it possible to configure wheel to name it just with
py3instead?