Message299456
Terry, the Windows implementation calls GetModuleFileNameW to get the executable's fully-qualified path from the loader. However, depending on how Python is started, this could be a \\?\ path, which leads to a bug in the startup code that determines the prefix path based on the landmark "lib\os.py". Probably the easiest solution would be to normalize the executable path to remove the \\?\ or \\.\ prefix. This prefix isn't useful here anyway since Windows doesn't properly support running programs from long paths, not even in Windows 10. I'll open a new issue for this. |
|
Date |
User |
Action |
Args |
2017-07-29 05:36:54 | eryksun | set | recipients:
+ eryksun, terry.reedy, vstinner, serhiy.storchaka |
2017-07-29 05:36:54 | eryksun | set | messageid: <1501306614.37.0.902030491795.issue31030@psf.upfronthosting.co.za> |
2017-07-29 05:36:54 | eryksun | link | issue31030 messages |
2017-07-29 05:36:53 | eryksun | create | |
|