[issue5408] test_osx_env failing

2009-03-04 Thread Benjamin Peterson
Changes by Benjamin Peterson : -- status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue5408] test_osx_env failing

2009-03-04 Thread Benjamin Peterson
Benjamin Peterson added the comment: Thumbs up here! Thanks. ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue5408] test_osx_env failing

2009-03-04 Thread Ronald Oussoren
Ronald Oussoren added the comment: The effect on sys.executable is always present, the test is only valid for a framework build because that's the only build that can find sys.prefix without looking at sys.executable. Setting PYTHONEXECUTABLE with a non- framework build is only valid if the v

[issue5408] test_osx_env failing

2009-03-04 Thread Ned Deily
Ned Deily added the comment: I don't have strong feelings about it one way or the other. As far as I can tell from the code and testing and the documented behavior, the effect on sys.executable is independent of whether it is a framework build or not. But I'm fine with narrowing the scope o

[issue5408] test_osx_env failing

2009-03-04 Thread Ronald Oussoren
Ronald Oussoren added the comment: Committed my fix as r70179 (3.x) and r70180 (30-maint). Benjamin: can you confirm this actually fixes the issue with a non- framework build, I don't know if I'll be able to test that before the first 3.1a release. -- resolution: -> fixed status: ope

[issue5408] test_osx_env failing

2009-03-04 Thread Ronald Oussoren
Ronald Oussoren added the comment: Ned: IMHO your patch is not correct. test_osx_env tests behaviour that's only valid for a framework build, and should therefore only run when testing a framework build. The easiest way to accomplish that is to change the test in test_osx_env.main to: if

[issue5408] test_osx_env failing

2009-03-02 Thread Ned Deily
Ned Deily added the comment: ANALYSISIn a non-framework build, when PYTHONEXECUTABLE is set to a invalid value, getpath.c is unable to determine appropriate values for sys.prefix and sys.path so the interpreter fails in initialization. SOLUTIONSimplif

[issue5408] test_osx_env failing

2009-03-02 Thread Ned Deily
Ned Deily added the comment: It appears the test doesn't work correctly for non-framework builds, something I didn't test. A patch is forthcoming. ___ Python tracker ___ ___

[issue5408] test_osx_env failing

2009-03-02 Thread Ronald Oussoren
Ronald Oussoren added the comment: Is this a standard unix build or a framework build? ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue5408] test_osx_env failing

2009-03-02 Thread Ned Deily
Changes by Ned Deily : -- nosy: +nad ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mail

[issue5408] test_osx_env failing

2009-03-02 Thread Benjamin Peterson
New submission from Benjamin Peterson : Mac OS 10.4 PPC debug build test_osx_env [31492 refs] Could not find platform independent libraries Could not find platform dependent libraries Consider setting $PYTHONHOME to [:] Fatal Python error: Py_Initialize: can't initialize sys standard streams I