[issue27516] Wrong initialization of python path with embeddable distribution

Steve Dower added the comment: This has changed for 3.6 and won't be changing again for 3.5. See https://docs.python.org/3.6/using/windows.html#finding-modules for info on the new support. -- resolution: -> out of date stage: -> resolved status: open -> closed

[issue27516] Wrong initialization of python path with embeddable distribution

Changes by Denny Weinberg : -- nosy: +Denny Weinberg ___ Python tracker ___

[issue27516] Wrong initialization of python path with embeddable distribution

Eryk Sun added the comment: It looks like you haven't copied pyvenv.cfg to your application directory, so Python isn't using the "applocal" configuration. That's why you're seeing the default paths that are relative to the current directory. It's also why PYTHONPATH and PYTHONHOME aren't

[issue27516] Wrong initialization of python path with embeddable distribution

Steve Dower added the comment: Environment variables shouldn't make any different to the embeddable distro - it is designed to ignore them. Have you modified it at all? The path is not as clean as I'd like it to be, but the initialization changes necessary are too significant for 3.5 at this

[issue27516] Wrong initialization of python path with embeddable distribution

Palm Kevin added the comment: BTW: Is there a good reason, the folder-of-the-executable is added to the python-path? I don't see any... -- ___ Python tracker

[issue27516] Wrong initialization of python path with embeddable distribution

Changes by Ned Deily : -- components: +Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware ___ Python tracker ___

[issue27516] Wrong initialization of python path with embeddable distribution

New submission from Palm Kevin: The way the python path is initialized with the embeddable python distribution makes no sense for me. If no environment variable PYTHONPATH is set, then the path is initialized like this: [python352]\python35.zip;.\DLLs;.\lib;[folder_of_executable] -->