[issue35856] bundled pip syntaxwarning

Pradyun Gedam added the comment: Closing this sounds reasonable to me! There are a couple of pending PRs for updating the pip, in the current versions of CPython. That's being tracked separately so likely don't need this to stay open anymore. On Tue, 12 Nov 2019 at 6:20 PM, Inada Naoki wrote

[issue35856] bundled pip syntaxwarning

Change by Inada Naoki : -- resolution: -> third party stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-

[issue35856] bundled pip syntaxwarning

Karthikeyan Singaravelan added the comment: I think this is fixed in pip's side with requests package upgraded with https://github.com/pypa/pip/commit/785ecf476a63e00819ef1b14bc8ee758dc9c12cb#diff-9235561c186d44f2bb0eef8b7f1d57ceR3 using raw string literls. I think we can close this as outdat

[issue35856] bundled pip syntaxwarning

Karthikeyan Singaravelan added the comment: This needs to be updated in vendor files for pip repo and then updating the files in CPython. The upstream issue on requests is fixed. -- nosy: +dstufft, ncoghlan, xtreak ___ Python tracker

[issue35856] bundled pip syntaxwarning

New submission from Dima Tisnek : It seems that `pip` vendored/bundled with Python3.8 doesn't conform to 3.8 syntax: … ~> /usr/local/bin/python3.8 -m ensurepip /.../tmp.../pip-18.1-py2.py3-none-any.whl/pip/_vendor/requests/status_codes.py:3: SyntaxWarning: invalid escape sequence \o /.../tmp..