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

Special case os.devnull for PIP_CONFIG_FILE to mean 'no config file' #1543

Closed
wants to merge 1 commit into from

Conversation

Projects
None yet
2 participants
@pfmoore
Copy link
Member

pfmoore commented Feb 7, 2014

Workaround for Python bug http://bugs.python.org/issue20053 (issue with ensurepip not being able to isolate itself from a user config file)

Longer term, a proper pip "isolated mode" is the better approach.

@dstufft

This comment has been minimized.

Copy link
Member

dstufft commented Feb 7, 2014

This needs to go into the 1.5.X branch

@pfmoore

This comment has been minimized.

Copy link
Member Author

pfmoore commented Feb 7, 2014

Bah. Apologies. I'll rebase and resubmit.

@pfmoore pfmoore closed this Feb 7, 2014

@pfmoore pfmoore deleted the pfmoore:devnull branch Feb 7, 2014

@pfmoore

This comment has been minimized.

Copy link
Member Author

pfmoore commented Feb 7, 2014

Actually, the rebase has merge conflicts :-( I have a develop branch, then a devnull branch off that, and a 1.5.X branch. I think that to move devnull to be based off 1.5.X rather than off develop I do git rebase --onto 1.5.X develop devnull but I have conflicts (which is correct).

It'll be easier just to delete and recreate the branch. New PR incoming...

@pfmoore

This comment has been minimized.

Copy link
Member Author

pfmoore commented Feb 7, 2014

New PR #1544.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.