[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-11-05 Thread Florent Xicluna
Changes by Florent Xicluna florent.xicl...@gmail.com: -- nosy: +flox ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9516 ___ ___ Python-bugs-list

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-06-29 Thread Ned Deily
Changes by Ned Deily n...@acm.org: -- status: pending - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9516 ___ ___ Python-bugs-list mailing

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-06-28 Thread Ned Deily
Ned Deily n...@acm.org added the comment: While I am a little concerned about applying these fixes, it is clear that the previous behavior was broken and the initial set of patches as applied did not improve matters. The only risk I can see is that there is a slight chance that there *might*

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-06-18 Thread Georg Brandl
Georg Brandl ge...@python.org added the comment: Can the 3.2 part of this be resolved this weekend? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9516 ___

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-06-18 Thread Ned Deily
Ned Deily n...@acm.org added the comment: I would like Ronald's take on it (also, I expect to be off-line for the weekend). Note, as it stands now, 3.2.1 (without any further patches) would have the same less than ideal behavior as 2.7.2. -- ___

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-06-18 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: I agree with Ned, the changes to the environment should only be done in subprocesses started by distutils. The patch looks fine, but I haven't tested the patches yet. -- ___ Python tracker

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-06-13 Thread Ned Deily
Ned Deily n...@acm.org added the comment: There are several issues here now. With the patches as now applied, when running the tests with standard OS X installer Pythons, I saw occasional failures of the new test_deployment_target test case (Unexpected target). After ensuring that the

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-06-13 Thread Ned Deily
Changes by Ned Deily n...@acm.org: Added file: http://bugs.python.org/file22352/issue9516_v3_distutils.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9516 ___

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-06-13 Thread Ned Deily
Changes by Ned Deily n...@acm.org: Added file: http://bugs.python.org/file22353/issue9516_v3_test_distutils_27.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9516 ___

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-06-13 Thread Ned Deily
Changes by Ned Deily n...@acm.org: Added file: http://bugs.python.org/file22354/issue9516_v3_distutils_27.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9516 ___

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-06-13 Thread Ned Deily
Changes by Ned Deily n...@acm.org: Added file: http://bugs.python.org/file22355/issue9516_v3_test_packaging.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9516 ___

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-06-13 Thread Ned Deily
Changes by Ned Deily n...@acm.org: Added file: http://bugs.python.org/file22356/issue9516_v3_packaging.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9516 ___

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-06-03 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: I ported the patch to packaging. Please test. -- components: +Distutils2 nosy: +alexis status: closed - open versions: -Python 2.7, Python 3.2 Added file: http://bugs.python.org/file22232/darwin-target-sysconfig-p7g.diff

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-05-18 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: Don’t you get ResourceWarnings from the popens and the unclosed file? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9516 ___

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-05-15 Thread Roundup Robot
Roundup Robot devnull@devnull added the comment: New changeset 9874f213edb2 by Ronald Oussoren in branch '2.7': Issue #9516: avoid errors in sysconfig when MACOSX_DEPLOYMENT_TARGET is set in shell. http://hg.python.org/cpython/rev/9874f213edb2 New changeset 5b108229a978 by Ronald Oussoren in

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-05-15 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: I've applied the patches to 3.3, 3.2 and 2.7 -- resolution: - fixed stage: commit review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-05-14 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: Attached the backport to 2.7 for my v2 patch. -- Added file: http://bugs.python.org/file21997/issue9516-v2-python2.7.patch ___ Python tracker rep...@bugs.python.org

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-05-13 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: I'll apply the patch late tonight (I won't be home until at least 22:30 CEST) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9516

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-05-13 Thread Ronald Oussoren
Changes by Ronald Oussoren ronaldousso...@mac.com: -- versions: -Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9516 ___ ___

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-05-12 Thread Georg Brandl
Georg Brandl ge...@python.org added the comment: I trust this patch does the right thing -- can you apply it before the rc this weekend? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9516

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-05-07 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: I've attached a v2 of the patch which adresses Éric's comments. I haven't changed the CompileError handling though, that would change a test failure into a test error. IMHO test errors should only happend due to bugs in the test code.

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-05-07 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: I haven't changed the CompileError handling though, that would change a test failure into a test error. Ah, thanks for correcting my mistake. -- ___ Python tracker rep...@bugs.python.org

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-05-03 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: This issue is very annoying when you use python's with different deployment targets and should IMHO be fixed in the next release. -- nosy: +benjamin.peterson, georg.brandl priority: normal - release blocker

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-05-03 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: Looks acceptable to me. A few details in the code could be improved: +@unittest.skipUnless(sys.platform == 'darwin', 'MacOSX test') Skip messages generally use another form, like “test relevant only on Mac OS X”. +finally: +

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-03-18 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo title: sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3but 10.5 during configure - sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure ___

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-03-14 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: Tarek: could you comment on this patch, in particular: is it OK to commit this to 2.7, 3.2 and head? (I haven't checked yet if the patch still applies cleanly, will do that later today) --

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-03-12 Thread Ned Deily
Ned Deily n...@acm.org added the comment: Another way this issue can show up: when building Python itself. If Parser/Python.asdl needs to be built (as with a new source checkout), the makefile target executes a python script (Parser/asdl_c.py) via /usr/bin/env python (a bootstrap dependency).

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2011-01-26 Thread Arif Amirani
Changes by Arif Amirani arif.amir...@gmail.com: -- nosy: +kontinuity ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9516 ___ ___ Python-bugs-list

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2010-09-16 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: I've attached a patch for 3.2 that should fix the issue. The patch adds a couple of testcases (1 for sysconfig and 1 for distutils.command.build_ext), adjust a couple more and implements the following functional changes: 1)

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2010-09-15 Thread Stonewall Ballard
Stonewall Ballard ston...@gmail.com added the comment: I just ran into this with Python 2.7, installed using port. I'm using python to process a text file in an Xcode 3.2 Script build step, and it's throwing the error because my Xcode target has a base sdk of 10.5. -- nosy: +stoneyb

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2010-08-18 Thread Sridhar Ratnakumar
Sridhar Ratnakumar sridh...@activestate.com added the comment: On 2010-08-17, at 9:01 PM, Ronald Oussoren wrote: I now understand why my script fails, and it is caused by this issue. The sysconfig.py code has another major issue: the use of os.putenv. This changes the environment, without

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2010-08-17 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: I can reproduce this with a script that builds and installs a couple of python versions, annoyingly enough I don't understand why that code fails. In particular, in my script the run of python that fails is started with this code:

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2010-08-17 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: This (untested) patch should fix the issue: Index: Lib/sysconfig.py === --- Lib/sysconfig.py(revision 84147) +++ Lib/sysconfig.py(working copy) @@ -295,9 +295,8 @@

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2010-08-17 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: I now understand why my script fails, and it is caused by this issue. The sysconfig.py code has another major issue: the use of os.putenv. This changes the environment, without changing os.environ. The use of os.putenv should be

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2010-08-11 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: Assigning to myself because I intend to work on this. More questions: does the error occur on the 10.6 machine you used to do the build or another machine? Is MACOSX_DEPLOYMENT_TARGET set in the environment when you run the command

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2010-08-11 Thread Sridhar Ratnakumar
Sridhar Ratnakumar sridh...@activestate.com added the comment: Another machine. Is MACOSX_DEPLOYMENT_TARGET set in the environment when you run the command that gives the error message? I don't think I had this environment set when I saw the above error message. I had to set

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2010-08-11 Thread Sridhar Ratnakumar
Sridhar Ratnakumar sridh...@activestate.com added the comment: Looks like reply-by-email stripped some parts of the message. does the error occur on the 10.6 machine you used to do the build or another machine? Another 10.6 machine. -- ___

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2010-08-11 Thread Sridhar Ratnakumar
Sridhar Ratnakumar sridh...@activestate.com added the comment: Even simply invoking the interpreter raises this exception! $ MACOSX_DEPLOYMENT_TARGET=10.3 python2.7 [...] IOError: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure $ --

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2010-08-10 Thread R. David Murray
Changes by R. David Murray rdmur...@bitdance.com: -- versions: -Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9516 ___ ___

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2010-08-09 Thread Sridhar Ratnakumar
Sridhar Ratnakumar sridh...@activestate.com added the comment: We build ActivePython 2.7 on Mac as follows: $ export MACOSX_DEPLOYMENT_TARGET=10.5 $ ./configure --enable-framework --enable-universalsdk=/Developer/SDKs/MacOSX10.5.sdk/ --with-universal-archs=intel $ make (the

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2010-08-07 Thread Ronald Oussoren
Ronald Oussoren ronaldousso...@mac.com added the comment: I agree that this behavior wrong, this should only trigger an error when building packages. How did you build python? I guess something like this: $ export MACOSX_DEPLOYMENT_TARGET=10.5 $ configure --enable-framework $ make install

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2010-08-06 Thread R. David Murray
Changes by R. David Murray rdmur...@bitdance.com: -- nosy: +ronaldoussoren ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9516 ___ ___

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2010-08-04 Thread Sridhar Ratnakumar
New submission from Sridhar Ratnakumar sridh...@activestate.com: I cannot find correct repro steps for this, but: /Library/Frameworks/Python.framework/Versions/2.7/bin/python -B -s -c import sys;print('%d.%d' % tuple(sys.version_info)[:2]) Traceback (most recent call last): File

[issue9516] sysconfig: $MACOSX_DEPLOYMENT_TARGET mismatch: now 10.3 but 10.5 during configure

2010-08-04 Thread Sridhar Ratnakumar
Changes by Sridhar Ratnakumar sridh...@activestate.com: -- components: +Macintosh versions: +Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9516 ___