Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
The warning message for Python 2.7 EOL is shown even for Pythons that are not EOL'ing #6207
PyPy is not EOL'ing on January 1, 2020, but the warning message emitted claims it is.
But as is, I've had a few internal developers ask me whether the message was accurate for us, for which I've had to explain it wasn't, so I figured I'd see whether modifying this message matters to anyone else.
How to Reproduce
(FWIW I've found https://discuss.python.org/t/packaging-and-python-2/662/73 after submitting this, so now I see the "clear statement" is possibly now under discussion :)
@Julian This probably is an oversight and mostly related to the fact that none of the active maintainers uses pypy. As such its support is mostly a best effort. Feel free to open a PR to amend this for pypy, though we may conclude to remove the message altogether judging by the discussion on the discuss.
@gaborbernat there already is one, but yes would love to see the outcome of the discussion -- in the PR, I left in the part of the warning message saying that
added a commit
Feb 11, 2019
Is there a way to permanently disable this (annoying) warning which is polutting the build logs? ... or we should just stop using newer versions of pip to avoid it?
For pip version check we at least had PIP_DISABLE_PIP_VERSION_CHECK to use to diable it but for this one I was not able to find any cli option to diable it.
This gets displayed on each pip call and if you could have lots of them even on a single tox environment, making your build logs like the