Christian Heimes added the comment:

I'm able to reproduce the problem on Ubuntu. It's probably caused by
their compile step in python2.5.postinst:

        cd /usr/lib/python2.5
        files=$(dpkg -L python2.5 | sed -n
'/\.py$/s,^/usr/lib/python2.5/,,p')
        /usr/bin/python2.5 /usr/lib/python2.5/py_compile.py $files
        if grep -sq '^byte-compile[^#]*optimize'
/etc/python/debian_config; then
            /usr/bin/python2.5 -O /usr/lib/python2.5/py_compile.py $files
        fi

It's compiling the py files relative to /usr/lib/python2.5. Please note
that the behavior of py_compile.py is intended. The relative path is
useful for people who pack the compiled files into a zip file or egg file.

----------
nosy: +tiran
resolution:  -> works for me
status: open -> pending

__________________________________
Tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue1665>
__________________________________
_______________________________________________
Python-bugs-list mailing list 
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to