Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unescaped space in proxy URL causes "Failed to parse" error in pip 19.2.1 #6839

Closed
davidedb opened this issue Aug 6, 2019 · 1 comment
Closed
Labels
auto-locked Outdated issues that have been locked by automation resolution: duplicate Duplicate of an existing issue/PR

Comments

@davidedb
Copy link

davidedb commented Aug 6, 2019

Environment

  • Pip version: 19.2.1
  • Python version: 3.6.3 and 2.7.4
  • Operating system: RHELS 6.9

Description
After upgrading pip from version 19.1.1 to 19.2.1, I was not able anymore to install any package.
For example, the command pip install upydev terminates immediately with the error message:

ERROR: Could not install packages due to an EnvironmentError: Failed to parse: http://name surname:password@proxy:8080

After some debugging I found out the problem is generated by the presence of a space character in the user login, i.e. between the user name and his surname.

Workaround
Simply replacing the space with the corresponding URL-encoded entity solves the issue.

setenv HTTP_PROXY 'http://name%20surname:password@proxy:8080`
pip install upydev

@triage-new-issues triage-new-issues bot added the S: needs triage Issues/PRs that need to be triaged label Aug 6, 2019
@pradyunsg
Copy link
Member

Thanks for filing this issue @davidedb!

pip's URL authentication handling has become stricter in pip 19.2. This has been brought up in #6775. I would appreciate if you could chime in there, about how it can be made easier to debug this issue for end users.

I'll close this as a duplicate of #6775.

@pradyunsg pradyunsg added the resolution: duplicate Duplicate of an existing issue/PR label Aug 6, 2019
@triage-new-issues triage-new-issues bot removed the S: needs triage Issues/PRs that need to be triaged label Aug 6, 2019
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Sep 5, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Sep 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation resolution: duplicate Duplicate of an existing issue/PR
Projects
None yet
Development

No branches or pull requests

2 participants