Fix packaging tags to drop Python version support
envgap__python-jsonschema__jsonschema-845
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- The project already builds and runs before the fix, so there is nothing to repair.
02 / ENVIRONMENT RECIPE
- Base commit
4f4012c0693754f4afdce24788a69a9ec32c912f- Manifest
setup.cfg- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
python-jsonschema/jsonschema #845 · read the original issue
The recent release of JsonSchema 4.0.0 seems to drop support for Python 2 (and Python 3.5 also but it might been dropped before) but pip is having issues getting the right version depending on the Python version. The correct information is in the setup.cfg https://github.com/Julian/jsonschema/blob/main/setup.cfg#L23 I think there are two issues for pip to pick the correct version based on the python version: * The python-requires seems to be correctly packaged in the file `jsonschema-4.0.0.tar.gz` but not in the file `jsonschema-4.0.0-py3-none-any.whl`. It looks like it's missing the correct metadata in the `METADATA` file. It should be a line similar to: `Requires-Python: >=3.7` * For pip to be able to get the correct package version, it needs at least two package versions with the proper package metadata https://packaging.python.org/guides/dropping-older-python-versions/#dropping-a-python-release. I would recommend releasing a version 3.2.1 with the following metadata: `python_requires = ">=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, !=3.4.*"`. I believe once both these actions are done, pip should be happy and users should get the proper version of jsonschema installed. I would be happy to help if needed.
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]