Re: [gentoo-python] twisted-r1.eclass postrm failure for new twisted ebuilds

[Mike Gilbert]

On Thu, Sep 29, 2016 at 3:06 AM, Brian Dolbec <dolsen@g.o> wrote:
>
> OK, I've got the new twisted ebuild almost ready.  I have the tests
> working, only diabling the network test group and one other that was
> disabled in the split pkg ebuild.
>
> But, the twisted-r1 postrm function is not working correctly.  I have
> been overriding it in the ebuild so far.  It seems that there is an
> EPYTHON issue...
>
> I'll let the traceback speak for itself.
>
>  * python2_7: running distutils-r1_run_phase twisted-r1_update_plugin_cache
>  * python3_4: running distutils-r1_run_phase twisted-r1_update_plugin_cache
> Traceback (most recent call last):
>   File "<string>", line 1, in <module>
>   File "/usr/lib64/python3.4/distutils/sysconfig.py", line 13, in <module>
>     import re
>   File "/usr/lib64/python3.4/re.py", line 336, in <module>
>     import copyreg
>   File "/usr/lib64/python2.7/site-packages/copyreg/__init__.py", line 7, in <module>
>     raise ImportError('This package should not be accessible on Python 3. '
> ImportError: This package should not be accessible on Python 3.
> Either you are trying to run from the python-future src folder or your installation
>  of python-future is corrupted.
>
>
>
> What I can't figure out is of it isn't EPYTHON that is screwed up, how the hell is
> this happening...  a simple py3.4 import re causes the 3.4 re.py to try and import a
> py2.7 version of copyreq.
>
> I can't reproduce this in a terminal window with py3.4 session.  "import re" is fine and
> works correctly.  So, it can't be a bad python install.

See portage bug 595028.

https://bugs.gentoo.org/show_bug.cgi?id=595028

You can workaround the problem by adding something like this to any
pkg_* functions.

cd "${HOME}"