You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
assignee=Noneclosed_at=<Date2019-08-03.14:39:49.796>created_at=<Date2014-02-05.21:57:33.472>labels= ['3.7', '3.8', '3.9', 'type-feature', 'library', 'OS-windows']
title='global .pdbrc on windows 7 not reachable out of the box'updated_at=<Date2019-08-03.14:39:49.795>user='https://bugs.python.org/mbyt'
The global .pdbrc file is determined by the %HOME% environment variable. However, this is not available out of the box on e.g. windows 7 systems. Here only %HOMEDRIVE% and %HOMEPATH% are defined.
Thus the usual approach to have a global .pdbrc file on windows is to define a %HOME% environment variable by hand. This could be avoided if the global .pdbrc would be determined by os.path.expanduser("~/.pdbrc"), which works on current windows and does the magic behind.
There are two possible approaches to improve this situation:
explicitly mention in the docs that on windows a %HOME% varialbe need to be created manually
patch pdb.py to use os.path.expanduser instead (see attached diff)
We have a patch to review or we need a doc patch, unless someone has a different idea to the approaches suggested by the originator. I prefer the idea of changing the code, manually changing environment variables just seems wrong to me, but I won't lose any sleep over it.