This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eryksun
Recipients eryksun, serhiy.storchaka, terry.reedy, vstinner
Date 2017-07-29.05:36:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1501306614.37.0.902030491795.issue31030@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2017-07-29 05:36:54eryksunsetrecipients: + eryksun, terry.reedy, vstinner, serhiy.storchaka
2017-07-29 05:36:54eryksunsetmessageid: <1501306614.37.0.902030491795.issue31030@psf.upfronthosting.co.za>
2017-07-29 05:36:54eryksunlinkissue31030 messages
2017-07-29 05:36:53eryksuncreate