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]
--> the distribution folder itself is not in the path ([python352]), an
import of _socket will thus fail !
--> Having DLLs and lib in the path is useless
(Notice, that when the PYTHONHOME is initialized, then the path '[python352]'
is also used for DLLs and lib (instead of '.\')
If the environment variable PYTHONPATH is set, then the path is extended like
this:
[python352]\python35.zip;[folder_of_executable]
--> the distribution folder itself is not in the path ([python352]), an
import of _socket will thus fail !
I would prefer this behavior:
* python path is not initialized anymore with 'DLLs' and 'lib'
* the distribution-folder should always be added to the python-path
----------
messages: 270447
nosy: palm.kevin
priority: normal
severity: normal
status: open
title: Wrong initialization of python path with embeddable distribution
type: enhancement
versions: Python 3.5
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27516>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
