Bug#397111: Bug#382252: Python PATH problem

[Matthias Klose]

tags 397111 - patch
tags 397111 + wontfix
thanks

Ignoring the .pyc and .pyo files would change the behaviour compared
to upstream; rejecting that patch.  It's explicitely allowed to use
the byte compiled files without the source files. I will close this
report.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#397111: Bug#382252: Python PATH problem

[Sam Morris]

Josselin Mouette wrote:
 mdiff.py does import bdiff which looks for bdiff.so in the same
 directory. On your system, mdiff.py is is
 in /var/lib/python-support/python2.4/mercurial/ which is the correct
 place for packages handled by python-support, while on the user's system
 it is in /usr/lib/python2.4/site-packages/mercurial/. Therefore you need
 to understand how the file ended up in this place.

Wouter Cloetens wrote:
 $ ls -l /usr/lib/python*/site-packages/mercurial/
 
 -rw-r--r-- 1 root root134 Jun  1  2006 __init__.pyc
 -rw-r--r-- 1 root root168 Jun  1  2006 __version__.pyc
 -rw-r--r-- 1 root root   5494 Jun  1  2006 appendfile.pyc
 -rw-r--r-- 1 root root   7589 Jun  1  2006 archival.pyc
 ... etc ...

This is #397111 cropping up again. Python really shouldn't import modules
from .pyc and .pyo files unless the original .py file still exists
alongside them.

-- 
Sam Morris
http://robots.org.uk/

PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078


signature.asc
Description: This is a digitally signed message part