Skip to content

bpo-20523: pdb searches for .pdbrc in ~ instead of $HOME#11846

Closed
tdhopper wants to merge 1 commit into
python:3.7from
tdhopper:fix-issue-20523
Closed

bpo-20523: pdb searches for .pdbrc in ~ instead of $HOME#11846
tdhopper wants to merge 1 commit into
python:3.7from
tdhopper:fix-issue-20523

Conversation

@tdhopper

@tdhopper tdhopper commented Feb 13, 2019

Copy link
Copy Markdown
Contributor

Previously pdb checked the $HOME environmental variable
to find the user .pdbrc. If $HOME is not set, the user
.pdbrc would not be found.

Change pdb to use os.path.expanduser('~') to determine
the user's home directory. Thus, if $HOME is not set (as
in tox or on Windows), os.path.expanduser('~') falls
back on other techniques for locating the user's home
directory.

This follows pip's implementation for loading .piprc.

Co-authored-by: Dan Lidral-Porter dlp@aperiodic.org

https://bugs.python.org/issue20523

Previously pdb checked the $HOME environmental variable
to find the user .pdbrc. If $HOME is not set, the user
.pdbrc would not be found.

Change pdb to use `os.path.expanduser('~')` to determine
the user's home directory. Thus, if $HOME is not set (as
in tox or on Windows), os.path.expanduser('~') falls
back on other techniques for locating the user's home
directory.

This follows pip's implementation for loading .piprc.

Co-authored-by: Dan Lidral-Porter <dlp@aperiodic.org>
@the-knights-who-say-ni

Copy link
Copy Markdown

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA).

Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

You can check yourself to see if the CLA has been received.

Thanks again for your contribution, we look forward to reviewing it!

@tdhopper

Copy link
Copy Markdown
Contributor Author

Going to target master

@tdhopper tdhopper closed this Feb 13, 2019
@tdhopper
tdhopper deleted the fix-issue-20523 branch February 13, 2019 22:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants