← All tasks
pythondateutil/dateutil #537Not a task: not reproduced

Add python_requires to setup.py

envgap__dateutil__dateutil-537

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.
Not a benchmark task.
  • In a clean container the reported failure did not reproduce, or the known fix did not make the project run.

02 / ENVIRONMENT RECIPE

Base commit
6908ea56db59e65a7e65528146e64ed53db37bdc
Manifest
setup.py
Reproduce
Awaiting issue-specific recipe
Run under trace
Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

dateutil/dateutil #537 · read the original issue
Right now we're just using the trove classifiers, so I think people may end up doing some complicated pinning, which is less than ideal (see #536 and #526). What we need is the `Requires-Python:` metadata in pip. I think this is added through `setup.py`. Here are some examples of people using it:



- [pytest](https://github.com/pytest-dev/pytest/blob/master/setup.py#L86)

- [ipython](https://github.com/ipython/ipython/blob/master/setup.py#L235)



@carreau gave [this talk at PyBay](https://youtu.be/3i6n1RwqQCo?t=660) (link goes to the relevant time - 11 minutes in) where he discusses the `python_requires` option ([slides are here](https://speakerdeck.com/pybay/2017-building-bridges-stopping-python-2-without-damages)), probably best to listen to what he's talking about and avoid or document the pitfalls here.
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
[]