Sridhar Ratnakumar <sridh...@activestate.com> added the comment: [pitrou] > Can you explain why this is a problem in Python? > Can't lib/python3.2/config-3.2m/Makefile simply be > provided by virtualenv (by copying it, I guess)?
Yes, I believe virtualenv already does that (or symlinks to it). Python 3.2 changed the path to config and include directories for some reason, viz. $ ls -d /opt/ActivePython-3.*/lib/python3.?/*config*/ /opt/ActivePython-3.1/lib/python3.1/config/ /opt/ActivePython-3.2/lib/python3.2/config-3.2m/ $ and: $ ls -d /opt/ActivePython-3.*/include/python3.?* /opt/ActivePython-3.1/include/python3.1 /opt/ActivePython-3.2/include/python3.2m $ It is possible that virtualenv is hardcoding the relative path to 'config' (and 'include') directories and thus failing to find the new 'config-3.2m' dir. If that is the case, this is not a problem with Python. Although msg129372 does point to a Python bug, it may or may not be related to the virtualenv issue noted earlier. Given that virtualenv doesn't officially Python 3 and virtualenv5 is more of a hack, I haven't investigated into this much. Does that answer your question? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11320> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
