This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | christian.heimes |
|---|---|
| Recipients | christian.heimes, gvanrossum, thekorn |
| Date | 2007年12月20日.05:00:11 |
| SpamBayes Score | 0.13434714 |
| Marked as misclassified | No |
| Message-id | <1198126812.33.0.376062174776.issue1665@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
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. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2007年12月20日 05:00:12 | christian.heimes | set | spambayes_score: 0.134347 -> 0.13434714 recipients: + christian.heimes, gvanrossum, thekorn |
| 2007年12月20日 05:00:12 | christian.heimes | set | spambayes_score: 0.134347 -> 0.134347 messageid: <1198126812.33.0.376062174776.issue1665@psf.upfronthosting.co.za> |
| 2007年12月20日 05:00:12 | christian.heimes | link | issue1665 messages |
| 2007年12月20日 05:00:11 | christian.heimes | create | |