[issue10881] test_site and macframework builds fails

Ned Deily added the comment: P.S. I forgot to mention that one of the 2.7 test_site failures was due to the PYTHONUSERBASE env variable having no effect with OS X framework builds. That had been fixed in 3.x; it's now back ported. -- ___ Python tr

[issue10881] test_site and macframework builds fails

Ned Deily added the comment: Thanks, Vinay, for your analysis. I adapted it for the applied fix. For 2.7, there were two additional test_site failures that are fixed by back porting minor fixes to site.py and sysconfig.py from 3.x. Applied in 2.7 (for 2.7.3), 3.2 (for 3.2.3), and default (

[issue10881] test_site and macframework builds fails

Roundup Robot added the comment: New changeset 82c4f094f811 by Ned Deily in branch '2.7': Issue #10881: Fix test_site failures with OS X framework builds. http://hg.python.org/cpython/rev/82c4f094f811 New changeset 013cba2eb008 by Ned Deily in branch '3.2': Issue #10881: Fix test_site failure w

[issue10881] test_site and macframework builds fails

Ronald Oussoren added the comment: On 11 Oct, 2011, at 22:28, Ned Deily wrote: > > Ned Deily added the comment: > > I forgot to mention that one advantage of using another framework and root > location, say, under your home directory somewhere, is that it is unnecessary > to use sudo. And

[issue10881] test_site and macframework builds fails

Ned Deily added the comment: I forgot to mention that one advantage of using another framework and root location, say, under your home directory somewhere, is that it is unnecessary to use sudo. And you don't need to use the special target in any case, simply "make install". -- ___

[issue10881] test_site and macframework builds fails

Ned Deily added the comment: > sudo make frameworkinstall While that shouldn't affect the Apple-supplied system Pythons, be aware that with default ./configure settings this will overwrite any third-party Python installs (like from the python.org installers) of the version in question in /

[issue10881] test_site and macframework builds fails

Vinay Sajip added the comment: IIRC what I did was clone the repo, configure and build, then sudo make frameworkinstall For me (on Leopard), this installed Python 3.3 in /Library/Frameworks/Python.framework, leaving my system Python (2.5.1) alone. Then you can just invoke the regression test

[issue10881] test_site and macframework builds fails

Bryce Verdier added the comment: I would like to help by reviewing the patch, however I'm unsure about how to do the framework aspect of this. Can someone send me instructions or a link on how I would set this up to test? Thanks in advance, -- nosy: +louiscipher

[issue10881] test_site and macframework builds fails

Changes by Éric Araujo : -- keywords: +needs review, patch stage: needs patch -> patch review ___ Python tracker ___ ___ Python-bugs-l

[issue10881] test_site and macframework builds fails

Vinay Sajip added the comment: This is now fixed in pythonv, see https://bitbucket.org/vinay.sajip/pythonv/changeset/a59a3868d185/raw/pythonv-a59a3868d185.diff -- ___ Python tracker __

[issue10881] test_site and macframework builds fails

Éric Araujo added the comment: Hem, I should have re-read Vinay’s message before posting :) Marking as easy. -- keywords: +easy stage: -> needs patch versions: +Python 2.7, Python 3.3 ___ Python tracker

[issue10881] test_site and macframework builds fails

Éric Araujo added the comment: How can we detect framework builds from Python code? Maybe there is a variable in sysconfig? -- nosy: +eric.araujo superseder: pep-0370 on osx duplicates existing functionality -> ___ Python tracker

[issue10881] test_site and macframework builds fails

Vinay Sajip added the comment: I'd like to reopen this, as it doesn't seem to be a duplicate of #8084. Specifically, test_getsitepackages in test_sitepackages appears to be wrong, since it has a correct test for platform builds later in the method, but the failure occurs earlier because the p

[issue10881] test_site and macframework builds fails

Changes by Stephen Hansen : -- superseder: -> pep-0370 on osx duplicates existing functionality ___ Python tracker ___ ___ Python-bug

[issue10881] test_site and macframework builds fails

Stephen Hansen added the comment: ... oops! Apparently dupe. Forgot to search first. Ignore. -- resolution: -> duplicate status: open -> closed ___ Python tracker ___ _

[issue10881] test_site and macframework builds fails

New submission from Stephen Hansen : With the latest from branches/py3k, in a framework build, I get: Wimp:build pythonbuildbot$ ./python.exe -m test.regrtest test_site [1/1] test_site test test_site failed -- Traceback (most recent call last): File "/Users/pythonbuildbot/32test/build/Lib/test