Summary: | net-im/gajim-0.16.6 (via dev-python/pycryptodome -> dev-python/cffi) w/ dev-python/pycparser-2.17: KeyError: 'pycparser.lextab' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michał Górny <mgorny> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | aidecoe, drobbins, v_2e, yamadharma |
Priority: | Normal | Keywords: | REGRESSION |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://github.com/eliben/pycparser/issues/229 | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=701878 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 611628 |
Description
Michał Górny
2017-03-26 13:27:26 UTC
Works after downgrading pycparser to 2.14. The middle version fails the same. Doesn't happen with dev-python/pycrypto. I wonder if that's a generic bug in pycparser, or sth CFFI-related. Appears to be an issue with pycparser as downgrading to 2.17 resolves the issue. I recommend masking 2.18 until this issue is properly addressed. Is this still an issue? I believe it is no longer. Okay, closing this as I believe this is deprecated and only affects older versions. Please re-open if issue persists with a current system. this bug just recurred (or a similar issue) with pycparser-2.19-r1. In this case, emerge failed: ------------------- copying pycparser/ply/yacc.py -> /var/tmp/portage/dev-python/pycparser-2.19-r1/work/pycparser-2.19-python3_6/lib/pycparser/ply copying pycparser/ply/cpp.py -> /var/tmp/portage/dev-python/pycparser-2.19-r1/work/pycparser-2.19-python3_6/lib/pycparser/ply copying pycparser/ply/__init__.py -> /var/tmp/portage/dev-python/pycparser-2.19-r1/work/pycparser-2.19-python3_6/lib/pycparser/ply ly copying pycparser/_c_ast.cfg -> /var/tmp/portage/dev-python/pycparser-2.19-r1/work/pycparser-2.19-python3_6/lib/pycparser warning: build_py: byte-compiling is disabled, skipping. Traceback (most recent call last): File "_build_tables.py", line 31, in <module> import lextab ModuleNotFoundError: No module named 'lextab' * ERROR: dev-python/pycparser-2.19-r1::gentoo failed (compile phase): ------------------- Can you please re-open? I had the same issue with pycparser-2.18. I'm not sure why it's recurring. Cheers Same here. A temporary fix is to comment out line 27 in pycparser-2.19-r1.ebuild: --- /usr/portage/dev-python/pycparser/pycparser-2.19-r1.ebuild 2019-12-02 03:09:38.000000000 +0000 +++ /tmp/pycparser-2.19-r1.ebuild 2019-12-02 10:39:16.000000000 +0000 @@ -24,7 +24,7 @@ python_prepare_all() { # remove the original files to guarantee their regen - rm pycparser/{c_ast,lextab,yacctab}.py || die + #rm pycparser/{c_ast,lextab,yacctab}.py || die # kill sys.path manipulations to force the tests to use built files sed -i -e '/sys\.path/d' tests/*.py || die This allows pycparser-2.19-r1 to build, but whether it is still correct I do not know. Please, reopen. Failed to emerge pycparcer-2.19-r1: import lextab ModuleNotFoundError: No module named 'lextab' * ERROR: dev-python/pycparser-2.19-r1::gentoo failed (compile phase) (In reply to Sergey Torokhov from comment #10) > Please, reopen. Failed to emerge pycparcer-2.19-r1: > > import lextab > ModuleNotFoundError: No module named 'lextab' > * ERROR: dev-python/pycparser-2.19-r1::gentoo failed (compile phase) Fixed for me after emerging dev-python/{cffi,mako,xcffib,zstandard,cairocffi}. Maybe update one of this packages repairs emerging of pycparser. Maybe it dev-python/mako as it supplies lexer.py (In reply to Sergey Torokhov from comment #11) Happened to me also. This fixed it, indeed: emerge dev-python/mako (In reply to Edmar Wiggers from comment #12) > (In reply to Sergey Torokhov from comment #11) > > Happened to me also. > This fixed it, indeed: > > emerge dev-python/mako emerge dev-python/mako did not help for me. So, I did emerge -u dev-python/cffi, and then it worked. (In reply to hacking from comment #13) > emerge dev-python/mako did not help for me. > So, I did emerge -u dev-python/cffi, and then it worked. It just happened to me again. This time, I just did... emerge dev-python/pycparser ...and it worked. Really seems some odd runtime emerge/compile problem. Note: I do not need dev-python/pycparser by itself, but it gets pulled by other(s) package(s). Same problem here but emerge --oneshot pycparser did not fix it. (In reply to Valmor de Almeida from comment #15) > Same problem here but emerge --oneshot pycparser did not fix it. BTW, the following worked: emerge --oneshot dev-python/mako emerge --oneshot dev-python/pycparser I hit the "No module named lextab" problem during a dev-python/pycparser-2.19-r1 to 2.20 upgrade. All I did to fix it was running "emerge -1 dev-python/pycparser" over and over. On the 5th try it installed fine. The build fails because of some race condition in the build system. bug 701878 is a duplicate. Same here with dev-python/pycparser-2.20. The suggestions to emerge dev-python/mako seemingly fixed it for me. |