| Summary: | dev-python/snakeoil fails to build | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Markos Chandras (RETIRED) <hwoarang> |
| Component: | New packages | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | ferringb |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --ifno
build.log |
||
|
Description
Markos Chandras (RETIRED)
2010-03-03 13:29:10 UTC
Created attachment 221929 [details]
emerge --ifno
Created attachment 221931 [details]
build.log
Your py3k is busted up for some reason- no idea why you've got an xrange in lib2to3, but you do, and it doesn't belong there. Snakeoil isn't at fault here, just is what's triggering the breakage. I am open to suggestions May I suggest dropping xrange in favor of range with a little performance loss in the process (in some cases though) or update to the latest py3k to see if this is a bug in lib2to3.
Best regards,
(In reply to comment #5) > May I suggest dropping xrange in favor of range with a little performance > loss in the process (in some cases though) or update to the latest py3k to see > if this is a bug in lib2to3. range is xrange in py3k, and 2to3 converts xrange to range. Note also that 2to3 also does *not* come with xrange invocations w/in it's MultiprocessRefactoringTool.refactor method. What's interesting to me is that I recognize that 'for i in xrange(num_processes)' line- it's part of processes = [multiprocessing.Process(target=self._child) for i in range(num_processes)] Which is about 70 lines further down the file then his TB states. So... something happened to his py3k install (any 2to3 user, which there are several, would trigger this when invoked w/ 2to3 -j >1). As stated in irc, re-emerge your py3k, specifically one from gentoo-x86 repo. If you're getting your dev-lang/python-3.1 from somewhere else, they're patching it with stuff they shouldn't. Rebuilding python-3.1.1 fixed it Thanks |