1 |
OK, I've got the new twisted ebuild almost ready. I have the tests |
2 |
working, only diabling the network test group and one other that was |
3 |
disabled in the split pkg ebuild. |
4 |
|
5 |
But, the twisted-r1 postrm function is not working correctly. I have |
6 |
been overriding it in the ebuild so far. It seems that there is an |
7 |
EPYTHON issue... |
8 |
|
9 |
I'll let the traceback speak for itself. |
10 |
|
11 |
* python2_7: running distutils-r1_run_phase twisted-r1_update_plugin_cache |
12 |
* python3_4: running distutils-r1_run_phase twisted-r1_update_plugin_cache |
13 |
Traceback (most recent call last): |
14 |
File "<string>", line 1, in <module> |
15 |
File "/usr/lib64/python3.4/distutils/sysconfig.py", line 13, in <module> |
16 |
import re |
17 |
File "/usr/lib64/python3.4/re.py", line 336, in <module> |
18 |
import copyreg |
19 |
File "/usr/lib64/python2.7/site-packages/copyreg/__init__.py", line 7, in <module> |
20 |
raise ImportError('This package should not be accessible on Python 3. ' |
21 |
ImportError: This package should not be accessible on Python 3. |
22 |
Either you are trying to run from the python-future src folder or your installation |
23 |
of python-future is corrupted. |
24 |
|
25 |
|
26 |
|
27 |
What I can't figure out is of it isn't EPYTHON that is screwed up, how the hell is |
28 |
this happening... a simple py3.4 import re causes the 3.4 re.py to try and import a |
29 |
py2.7 version of copyreq. |
30 |
|
31 |
I can't reproduce this in a terminal window with py3.4 session. "import re" is fine and |
32 |
works correctly. So, it can't be a bad python install. |
33 |
|
34 |
I'll work on pushing the changes to the twisted ebuilds in the morning to my buildbot-dev overlay. |
35 |
But I have attached the WIP ebuild for 16.3.0. You can grab the files dir from [1] if you want |
36 |
to try emerging it. |
37 |
|
38 |
[1] https://github.com/dol-sen/buildbot-dev/tree/master/dev-python/twisted/files |
39 |
-- |
40 |
Brian Dolbec <dolsen> |