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

Invalid Configuration File causes a traceback + crash #4893

Closed
pradyunsg opened this issue Nov 28, 2017 · 3 comments · Fixed by #5798
Closed

Invalid Configuration File causes a traceback + crash #4893

pradyunsg opened this issue Nov 28, 2017 · 3 comments · Fixed by #5798
Assignees
Labels
auto-locked Outdated issues that have been locked by automation C: configuration Configuration management and loading kind: crash For situations where pip crashes type: bug A confirmed bug or unintended behavior
Milestone

Comments

@pradyunsg
Copy link
Member

Coming from #4892

If any configuration file can't be read from, pip crashes with a traceback. While the traceback points at the relevant line, it would be nicer to print a better error message (and no traceback).

@pradyunsg pradyunsg added kind: crash For situations where pip crashes C: configuration Configuration management and loading labels Nov 28, 2017
@pradyunsg pradyunsg added this to the Print Better Error Messages milestone Nov 28, 2017
@pradyunsg pradyunsg self-assigned this Nov 28, 2017
@fishd
Copy link

fishd commented Feb 13, 2018

I've been fiddling with a fix for this and I would like to work on a pull request for it.

@pradyunsg
Copy link
Member Author

Go ahead! =)

@pradyunsg pradyunsg added type: bug A confirmed bug or unintended behavior and removed type: bug A confirmed bug or unintended behavior labels May 11, 2018
@pradyunsg pradyunsg modified the milestones: Print Better Error Messages, 18.1 Sep 18, 2018
@lock
Copy link

lock bot commented May 31, 2019

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.

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label May 31, 2019
@lock lock bot locked as resolved and limited conversation to collaborators May 31, 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 C: configuration Configuration management and loading kind: crash For situations where pip crashes type: bug A confirmed bug or unintended behavior
Projects
None yet
2 participants