Should a change in search order of directories in setup.py be backported?
![](https://secure.gravatar.com/avatar/e8600d16ba667cc8d7f00ddc9f254340.jpg?s=120&d=mm&r=g)
I found out that the directories listed in $CPPFLAGS and $LDFLAGS were being added in reverse order in setup.py. That meant having ``-I/foo -I/bar`` was searching /bar first. I fixed setup.py in the trunk so that the declared order if followed instead. But should this be backported? It will change how extensions are compiled if there is more than one version on a machine. Not sure if we want people to suddenly have what they link against change in a micro release. -Brett
![](https://secure.gravatar.com/avatar/107dbd4c05818a538bce7193e5647c7a.jpg?s=120&d=mm&r=g)
Brett> [fix setup.py search order] Brett> But should this be backported? +1. Seems like a bug to me. Skip
![](https://secure.gravatar.com/avatar/3acb8bae5a2b5a28f6fe522a4ea9b873.jpg?s=120&d=mm&r=g)
But should this be backported? It will change how extensions are compiled if there is more than one version on a machine. Not sure if we want people to suddenly have what they link against change in a micro release.
I agree with Skip that this is a bug, so please backport it. Regards, Martin
![](https://secure.gravatar.com/avatar/e8600d16ba667cc8d7f00ddc9f254340.jpg?s=120&d=mm&r=g)
On Feb 3, 2008 12:08 AM, "Martin v. Löwis" <martin@v.loewis.de> wrote:
But should this be backported? It will change how extensions are compiled if there is more than one version on a machine. Not sure if we want people to suddenly have what they link against change in a micro release.
I agree with Skip that this is a bug, so please backport it.
Done in r60548. I also went back and added a Misc/NEWS entry for the trunk. -Brett
participants (3)
-
"Martin v. Löwis"
-
Brett Cannon
-
skip@pobox.com