Summary: | tahoe fails to build with python-2.6.4-r1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Oisin O Malley <ninja.gofer> |
Component: | New packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | howard_b_golden |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Oisin O Malley
2010-03-10 03:18:27 UTC
I'm getting the "byte-compiling is disabled" messages from python-2.6.5. I found that, on my system, /usr/portage/profiles/make.defaults contains: PYTHONDONTWRITEBYTECODE="1" I'm puzzled that this is the case. Is there some good reason for this that I'm overlooking? It's not a bug in Python. (In reply to comment #2) > It's not a bug in Python. Arfrever, respectfully, it would help me (and others IMO), if you would explain your reasoning a bit when you close bugs as invalid. The obvious, unanswered questions are: What is it that caused the traceback? Is it a bug in something else? Is it a misconfiguration? How should a user proceed who gets this result? Etc. Also, my question in comment #1 wasn't answered. If this isn't a good place to answer, I will open a separate bug for it. (Thank you for all you do. I know you work very hard on this as a volunteer. My suggestion is that you communicate your knowledge to the rest of us a bit more. Thanks again.) It might be a bug in tahoe or setuptools, but I haven't previously seen it (and I reinstalled many packages using setuptools), so I would assume that it's a bug in tahoe. If you can find a different package, which doesn't misuses setuptools and has similar problem, then report a bug in setuptools. PYTHONDONTWRITEBYTECODE="1" is to avoid sandbox violations during installation of some packages. It was this bug in distribute: http://bitbucket.org/tarek/distribute/issue/147/respect-the-sysdont_write_bytecode-flag |