[issue24923] Append system paths in setup.py instead of prepending

Irit Katriel added the comment: Fixed in Python 3 (in https://github.com/python/cpython/commit/807bd0a8a47191f7aa25cd9d5619bbc46a3f2a2a). Too late for 2.7. -- nosy: +iritkatriel resolution: -> fixed stage: patch review -> resolved status: open -> closed

[issue24923] Append system paths in setup.py instead of prepending

Chris Hogan added the comment: Zach, 3.x had the desired behavior. We didn't have to make any changes. -- ___ Python tracker ___

[issue24923] Append system paths in setup.py instead of prepending

Zachary Ware added the comment: In that case, does this patch do what you want it to do? -- stage: -> patch review Added file: http://bugs.python.org/file41710/issue24923.diff ___ Python tracker

[issue24923] Append system paths in setup.py instead of prepending

Chris Hogan added the comment: I should be able to try it out today or tomorrow. I'll let you know. -- ___ Python tracker ___

[issue24923] Append system paths in setup.py instead of prepending

Changes by R. David Murray : -- nosy: +r.david.murray ___ Python tracker ___ ___

[issue24923] Append system paths in setup.py instead of prepending

Zachary Ware added the comment: I've been doing some research on this, the below is pretty much a brain-dump. Related issues: issue232609, issue420565, issue10520. This looks to me like the ideal solution is to assign a priority to each entry and sort by that priority before using it; give

[issue24923] Append system paths in setup.py instead of prepending

New submission from Chris Hogan: Setup.py evaluates what's given in LDFLAGS and CPPFLAGS and CFLAGS. These variables are the usual mechanism to communicate custom paths/libs/defs to a build process. However, setup.py puts system paths in front of custom paths which makes it impossible to use