[issue8236] ./configure: ImportError: No module named asdl (when run from buildout's python)

2010-03-29 Thread R. David Murray
R. David Murray added the comment: That sounds like the likely explanation. -- resolution: -> works for me stage: -> committed/rejected status: open -> closed ___ Python tracker __

[issue8236] ./configure: ImportError: No module named asdl (when run from buildout's python)

2010-03-29 Thread Sridhar Ratnakumar
Sridhar Ratnakumar added the comment: > why is your buildout python failing to support that import? I believe it is because "" (current directory) is not in sys.path for buildout python. Buildout explicitly sets sys.path. Perhaps that's why. Feel free to close this issue. -- ___

[issue8236] ./configure: ImportError: No module named asdl (when run from buildout's python)

2010-03-29 Thread R. David Murray
R. David Murray added the comment: Python is used to build python. Theoretically you should be able to avoid that rebuild. cf the following thread: http://mail.python.org/pipermail/python-dev/2006-April/063511.html and the referenced issue 1465408. asdl_c.py is going to be importing asdl.py

[issue8236] ./configure: ImportError: No module named asdl (when run from buildout's python)

2010-03-27 Thread Sridhar Ratnakumar
Sridhar Ratnakumar added the comment: I am not sure how "import asdl" works. -- ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue8236] ./configure: ImportError: No module named asdl (when run from buildout's python)

2010-03-27 Thread Sridhar Ratnakumar
Sridhar Ratnakumar added the comment: Ah, I see what is happening. My $PATH has a buildout's python (bin/python) path. Apparently that is messing up with sys.path. Using /usr/local/bin/python, for instance, in $PATH does not give this problem. -- title: ./configure: ImportError: No mo

[issue8236] ./configure: ImportError: No module named asdl

2010-03-27 Thread Sridhar Ratnakumar
Sridhar Ratnakumar added the comment: I didn't have to run 'make distclean', because this is a fresh clone. $ hg clone http://code.python.org/hg/branches/release2.6-maint/ $ cd release2.6-maint $ ./configure --prefix=`pwd`/i $ make ./Parser/asdl_c.py -h ./Include ./Parser/Python.asdl Traceback

[issue8236] ./configure: ImportError: No module named asdl

2010-03-26 Thread R. David Murray
R. David Murray added the comment: I can't reproduce this on 2.6 maint on Linux 32 bit (Gentoo). Did you try doing a make distclean before redoing the configure/make? -- nosy: +benjamin.peterson, r.david.murray priority: -> high ___ Python tracker

[issue8236] ./configure: ImportError: No module named asdl

2010-03-25 Thread Sridhar Ratnakumar
Changes by Sridhar Ratnakumar : Added file: http://bugs.python.org/file16665/pyconfig.h ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue8236] ./configure: ImportError: No module named asdl

2010-03-25 Thread Sridhar Ratnakumar
Changes by Sridhar Ratnakumar : Added file: http://bugs.python.org/file16664/config.log ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue8236] ./configure: ImportError: No module named asdl

2010-03-25 Thread Sridhar Ratnakumar
New submission from Sridhar Ratnakumar : I'm seeing this error with 2.6 and 3.1 maint branches (not sure about 2.7) on both Linux & Mac 32-bit builds. Does not happen on Linux 64-bit though. Also this is possibly caused by a recent commit, as we never saw this issue before. [...] creating Make