[issue6114] distutils build_ext path comparison only based on strings

Éric Araujo added the comment: Thanks for the report and patch. I just tested that When the executable itself is symlinked (not installed, just linked from an existing installation), sys.exec_prefix and sys.executable are different. This means that a unit test (to prevent regressions) will be

[issue6114] distutils build_ext path comparison only based on strings

Éric Araujo added the comment: symlinks are not supported at all on Windows before 3.2, so we’re good, except for cygwin. -- ___ Python tracker ___ _

[issue6114] distutils build_ext path comparison only based on strings

Sven Rebhan added the comment: Of course there is a secret distutils comunity using git! ;-) The three ppl mentioned there found and fixed the problem, that's why. But back to the issue: Can we use a switch or wrapper function to change the test method for this path dependent on the OS? I'm a

[issue6114] distutils build_ext path comparison only based on strings

Éric Araujo added the comment: > The three ppl mentioned there found and fixed the problem, that's why. The real question behind the joke was: Are you part of the same community? Where does this fix come from? > But back to the issue: Can we use a switch or wrapper function to > change the tes

[issue6114] distutils build_ext path comparison only based on strings

Changes by Éric Araujo : -- versions: +3rd party ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue6114] distutils build_ext path comparison only based on strings

Changes by Mark Lawrence : -- versions: -Python 2.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue6114] distutils build_ext path comparison only based on strings

Éric Araujo added the comment: Two people started working on this during the first Montreal sprint. -- versions: +Python 3.3 -Python 3.1 ___ Python tracker ___ __

[issue6114] distutils build_ext path comparison only based on strings

New submission from Sven Rebhan : If python is installed into a symlink'ed directory, the variables "sys.exec_prefix" and "sys.executable" can contain different paths. Therefore, the respective test in build_ext.py fails (line 202) and a wrong library search directory (-L.) is set. The attached

[issue6114] distutils build_ext path comparison only based on strings

Changes by jougs : -- nosy: +jougs ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailma

[issue6114] distutils build_ext path comparison only based on strings

Changes by Tarek Ziadé : -- priority: -> normal resolution: -> accepted versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.5 ___ Python tracker ___

[issue6114] distutils build_ext path comparison only based on strings

Changes by Mark Lawrence : -- components: -Distutils2 nosy: +dstufft versions: +Python 3.4, Python 3.5 -3rd party, Python 3.2, Python 3.3 ___ Python tracker ___ _

[issue6114] distutils build_ext path comparison only based on strings

Steve Dower added the comment: Distutils is now deprecated (see PEP 632) and all tagged issues are being closed. From now until removal, only release blocking issues will be considered for distutils. If this issue does not relate to distutils, please remove the component and reopen it. If y

[issue6114] distutils build_ext path comparison only based on strings

STINNER Victor added the comment: This issue is 10 years old has a patch: it's far from being "newcomer friendly", I remove the "Easy" label. -- keywords: -easy nosy: +vstinner ___ Python tracker __