Fix for issue 5085 (--user set in config causes pip wheel to fail)

[pfmoore]

No description provided.

[pradyunsg]

#4575 comes to mind but that's a little to big to wait on, maybe? I had a WIP PR for it, with a long checklist.

Otherwise, we can add a comment + document that --no-user is for internal use only, for now. Also, maybe try out and check if optparse is helpful and shows an error or something on --no-user --user or --user --no-user?

[pfmoore]

Yeah, I think #4575 is too much to rush into pip 10. Agreed I'm OK with this being a bit of a hack for now. Ideally we should switch to a better option parser (argparse or maybe click) in the longer term, so if this is a temporary workaround for limitations of optparse, I'm willing to live with it.

Ultimately, the fact that a user currently has no way of overriding a user=true setting in their config file is a problem - just not one that anyone has encountered in real life until now. I wonder if anyone has reported anything like this in relation to Debian's switch to --user by default, no time right now but I'll do a search maybe tomorrow.

[anntzer]

fwiw --foo and --no-foo is a pretty standard scheme for boolean flags, with the standard convention that the last flag wins (but #4575 does looks nicer).

[pfmoore]

@anntzer Yes, that's what I'd expect - but optparse doesn't seem to implement that behaviour by default. I'll experiment a bit more tomorrow. Hopefully I missed something...

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.