Skip to content

gh-133307: Add new Pdb config location $XDG_CONFIG_HOME/pdb/.pdbrc #133733

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

makukha
Copy link

@makukha makukha commented May 9, 2025

@bedevere-app
Copy link

bedevere-app bot commented May 9, 2025

Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.

@makukha makukha changed the title gh-133307: Added new .pdbrc location, "$XDG_CONFIG_HOME/pdb/.pdbrc" May 9, 2025
@gaogaotiantian
Copy link
Member

I'm a -1 on this one. We don't have anything in CPython that's using $XDG_CONFIG_HOME for now. We do have a few cases where we read config files from home dir like IDLE or netrc. This increases the maintenance effort, introduces some inconsistency, without much benefits. I understand that this method stores the user data/config per app instead of per user, but if we really need to do that, we should do it for the whole Python, not just pdb - then it would probably be a PEP-level change.

I think you need to at least get some supports from other people - users from d.p.o. and/or some core devs. That would show that people are interested in this feataure. At this moment I'm not fully convinced that we should have this.

@makukha
Copy link
Author

makukha commented May 9, 2025

@gaogaotiantian thank you for the detailed response! Could you please keep this PR open for a week or two? I'll drop a post in Discourse and get back here.

@gaogaotiantian
Copy link
Member

I won't close this PR. Feel free to gather some opinions and promote this again in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants