EnvGap
Remove universal=1 from setup.cfg to avoid bogus wheel filenames claiming Python 2 support?
envgap__marshmallow-code__marshmallow-1860
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
afe4ddfa173ce717af281130a7532509de297d1e- Manifest
setup.cfg- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
marshmallow-code/marshmallow #1860 · read the original issue
https://github.com/marshmallow-code/marshmallow/blob/3.13.0/setup.cfg has "universal=1" in the "bdist_wheel" section, for back when you still supported Python 2 (pre mm3.0). That now produces a wheel name like "marshmallow-3.13.0-py2.py3-none-any.whl", which claims to support Python 2, but of course does not. I think standard "pip" 2.7 via PyPI gets around this by checking the setup.py "python_requires" or something. But I've got one setup where I'm pointing pip-compile at a cache of wheel files including a Marshmallow 3 wheel, and it collects the Marshmallow 3 wheel with that "py2.py3" fragment as most recent even with Python 2, and then dies when setup.py is eventually run for it. Could that universal=1 be removed so that the resulting wheel filenames don't claim Python 2 compatibility?
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]