-
Notifications
You must be signed in to change notification settings - Fork 232
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
"Edit preferences" comes up every time I use pdb #139
Comments
Wow, I finally solved this right after submitting this issue. Somehow my ~/.config/pudb folder was owned by root. Running sudo chown -R stewartr:stewartr ~/.config/pudb fixed the problem. It would have been nice if pudb told me it was getting permission denied when trying to write files though. |
Right. The preferences are opened when the welcome message hasn't been seen before. It looks like if the config file can't be loaded, then some defaults are used, which include showing the welcome message. Probably the except at Line 56 in 1b3ee78
|
Actually it looks like ConfigParser itself ignores errors (so that |
You could stat the config file. |
Sure. But it seems like unreadable config files is one of the use cases of having multiple config paths. I could be wrong about that though. |
I was more suggesting noticing a non-writable config file in $HOME and warning about it. |
I'm encountering this issue too on two different *buntu-based machines. I m using it running unit tests with tox 2.7 inside a virtual env. Permissions should not be a problem:
Nothing is written to that file while pudb is active or after it is closed. |
@belugame can you try removing the |
@asmeurer Thank you, configparser shadowed an IOError indeed that is in my project setup.
|
We should probably remove that line. |
I assume there is a way to fix this, but I haven't found this after 15 minutes. It would be great if the Edit Preferences page told you how to suppress it on the next pudb launch.
The text was updated successfully, but these errors were encountered: