Warn on Python 2.7

[dstufft]

Ref: #6148

[pfmoore]

LGTM. Needs some test fixes to cater for the stderr output, though 😉

[dstufft]

Yea, think I've got that sorted now.

[pradyunsg]

I'll defer to @pfmoore to merge this in, if he has the time to take a look and confirm he's okay with the language of the message. :)

[dstufft]

Gonna go ahead and merge this in now since @pfmoore already OK'd the message earlier and I haven't changed the messaging at all besides a grammar fix.

[ncoghlan]

Well worded :)

[pfmoore]

Yep, it's fine with me. Sorry, I just left a "LGTM" comment than a formal approval - I should have done the latter.

[orutherfurd]

Maybe a silly question, but is there an easy way to disable this, other than downgrading pip? I've got cron jobs running that now tell me to upgrade python, which is much more frustrating than it is helpful.

[dstufft]

It uses the Python warnings module, so you can configure it with that, e.g.:

$ pip list
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
Package    Version
---------- -------
pip        19.0.1
setuptools 40.6.3
wheel      0.32.3

$ PYTHONWARNINGS=ignore:::pip._internal.cli.base_command pip list
Package    Version
---------- -------
pip        19.0.1
setuptools 40.6.3
wheel      0.32.3

That'll hide any warning generated by the base command module. I'm not entirely opposed to some general way to acknowledge specific deprecation warnings and silence them, if that sounds useful then I'd encourage you to open a ticket.

[pradyunsg]

I'm not entirely opposed to some general way to acknowledge specific deprecation warnings and silence them, if that sounds useful then I'd encourage you to open a ticket.

There's #6119, which can cover this use case as well.

[ncoghlan]

PYTHONWARNINGS="ignore:DEPRECATION::pip._internal.cli.base_command" should ignore the upgrade warnings specifically.

Edit: The regex syntax I originally had in the message filter only works when defining filters through the Python API, not from the environment. Checks are also only made against the start of the message, not the whole thing. Accordingly, updated to search for the DEPRECATION prefix as recommended by @kylegibson below.

[orutherfurd]

Hey, thanks -- appreciate it.

…

On Wed, Jan 23, 2019 at 9:13 AM Donald Stufft ***@***.***> wrote: It uses the Python warnings module, so you can configure it with that, e.g.: $ pip list DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. Package Version ---------- ------- pip 19.0.1 setuptools 40.6.3 wheel 0.32.3 $ PYTHONWARNINGS=ignore:::pip._internal.cli.base_command pip list Package Version ---------- ------- pip 19.0.1 setuptools 40.6.3 wheel 0.32.3 That'll hide *any* warning generated by the base command module. I'm not entirely opposed to some general way to acknowledge specific deprecation warnings and silence them, if that sounds useful then I'd encourage you to open a ticket. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#6147 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAZJHhbHnOpvv77TV-ffQq2iw74T5JSvks5vGG4igaJpZM4aJTWM> .

[felker]

The environment variable that @ncoghlan recommended did not suppress the warning for me. Is there another way to silence this? I run pip to get Zsh completions on every interactive shell startup, so they are quite bothersome.

pip 19.0.2 from /usr/local/lib/python2.7/site-packages/pip (python 2.7)

[hugovk]

@felker Try double quiet:

 pip -qq install something

(From #6207 (comment))

[felker]

@hugovk thanks, I will use this for now. But doesn't it silence all warnings? Weird that the environment variable didn't work for me...

[hugovk]

@felker Yes. There are three levels of silencing, it'll silence everything at the first two levels.

[kylegibson]

@felker - The environment variable that @ncoghlan recommended also did not work for me. Here's what is currently working for me (pip 19.0.3):

PYTHONWARNINGS=ignore:DEPRECATION::pip._internal.cli.base_command

The second component of the ignore spec is the prefix of the message that is being displayed. The current message is this:

DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.

[ncoghlan]

@kylegibson You're right, I didn't test mine, and it was broken twice over (regex filters aren't accepted via the environment variable, and filters have to match the start of the message, not an arbitrary subsequence)

[pradyunsg]

I'm going to go ahead and lock this PR. We have a place for discussion about Python 2.7 at #6231.