PIP: Python 3 Support about ort HOT 3 CLOSED

Note that the environment markers in requirements.txt files are per-dependency markers, to allow for installing different dependencies depending on the Python version. While we could misuse that, it's not quite what we need.

To reiterate, what we need is a machine-readable way for a project to say "I require Python 3" (or Python 2).

Looks like another option is to use a python_requires directive in a setup.cfg file (not setup.py file, but there seems to be no consensus about that).

Yet another upcoming standard seems to be the pyproject.toml file which may contain a requires-python directive. Did I mention that Python dependency management is a mess?

from ort.

Here's advice on how to detect if Python 3 vs Python 2 is needed: https://stackoverflow.com/questions/40886456/how-to-detect-if-code-is-python-3-compatible. If this works, no manually maintained metadata is required – and such metadata might not be correct anyway. Instead, the required information could be determined automatically as and when required. This would also eliminate any waiting for a standard or a standard that is most widely adopted.

from ort.

Implemented by #1146.

from ort.