pythonimageio/imageio #756Not a task: already works

setup.py "python_requires" is still set to Python 3.5

envgap__imageio__imageio-756

Original GitHub issue ↗Dated source checkout ↗Opened 2022-02-23

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: edbc3caabbaea30bc2c6679e8cbf6c3fd8c2b958
Manifest: setup.py
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

imageio/imageio #756 · read the original issue

https://github.com/imageio/imageio/blob/master/setup.py#L221



I'm using Python 3.6 and now with version 2.16.0 of `imageio` forcing the `numpy` requirement >= 1.20.0, pip is having a hard time resolving dependencies (only on Windows for some reason). pip thinks it can install `imageio` 2.16.0 because it says it's compatible with python 3.5 but `numpy` 1.20.0 requires Python 3.7+.



I'm using the latest version of pip (21.3.1) that is supported on Python 3.6.

For some reason, I don't have any issue resolving dependencies on Linux.



If the "python_requires" had been updated to 3.7+ for the 2.16.0 release of `imageio`, then pip would stick with using version 2.15.0 and there would be no problem.



Can you publish a hotfix to pypi for version 2.16.0 with the "python_requires" set to Python 3.7?

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]