Installing v1.8.0 from sdist fails with old pip versions about python-gssapi

[jborean93]

This version has been yanked from PyPI and I will push a new release under 1.8.1 that restricts python_requires >= 3.7 as that should ship with a new enough pip that supports PEP 517 out of the box. Unfortunately yanking support in pip was introduced around the same time as this stuff so they will still need to constrain the version.

Previous versions did used to include the cythonised files but it caused all sorts of problems with newer Python versions or gcc versions turning warnings into errors over time which would be fixed by newer Cython versions. I incorrect assumed that since PEP 517 support has been out since 2018 that it would be ok but seems like RHEL 8 slipped through the cracks. I'll try to request it to be deleted but there's no guarantees PyPI will accommodate that request.

I've requested the version to be deleted by the PyPI admins but I'm unsure if they will accept the request. Considering there is a python3-gssapi package from DNF on these versions and it's considered poor practice to install packages from pip onto the system Python I am hoping this isn't a common case. If using a venv they can upgrade their pip version to ensure that the yank is respected or even use Python 3.8 that is available through dnf.

[webknjaz]

I've requested the version to be deleted by the PyPI admins but I'm unsure if they will accept the request.

Closing, now that it's removed from https://pypi.org/project/gssapi/#history.

[jborean93]

Yep, the setting the delete the version was a bit lower than where I checked, 1.8.0 has been removed and 1.8.1 will include python_requires='>=3.7' which should avoid this problem.