| Git Clone URL: | https://aur.archlinux.org/python2-pycparser.git (read-only, click to copy) |
|---|---|
| Package Base: | python2-pycparser |
| Description: | C parser and AST generator written in Python |
| Upstream URL: | https://github.com/eliben/pycparser |
| Licenses: | BSD |
| Submitter: | bionade24 |
| Maintainer: | matthewq337 |
| Last Packager: | matthewq337 |
| Votes: | 8 |
| Popularity: | 0.030871 |
| First Submitted: | 2022-01-08 16:10 (UTC) |
| Last Updated: | 2024-06-30 19:35 (UTC) |
If this:
pacman -Rdd python2-pycparser
yay python2-pycparser
does not work for you, make sure that you don't have old versions of pycparser somewhere on your system, e.g.:
/usr/lib/python2.7/site-packages/
$HOME/.local/lib/python2.7/site-packages/
For the sanity of us all, this package should probably build (or run tests) with an adjusted python library path, prioritizing it's own code over existing alternatives.
@holyArch "holyArch commented on 2022-02-01 14:40 (CET) (edited on 2022-02-01 14:41 (CET) by holyArch)" works for me. Thx
Building failed for me
====================================================================== FAIL: test_all_examples (tests.test_examples.TestExamplesSucceed)
Traceback (most recent call last): File "/home/xavier/.cache/yay/python2-pycparser/src/pycparser-release_v2.21/tests/test_examples.py", line 29, in test_all_examples rc, 0, 'example "{}" failed with stdout =\n{}'.format(filename, stdout)) AssertionError: example "using_cpp_libc.py" failed with stdout =
Ran 130 tests in 1.050s
FAILED (failures=1) ==> ERROR: A failure occurred in check(). Aborting... -> error making: python2-pycparser
This worked for me:
pacman -Rdd python2-pycparser
yay python2-pycparser
When it shows "Packages to cleanBuild?", choose python2-pycparser.
Thanks, df8o yay --needed -S fakepkg sudo fakepkg python2-pycparser sudo pacman -Rdd python2-pycparser yay -S python2-pycparser
@bionade24 hmm i think i mixed up the tabs or sth i just noticed somehow i got the PKGBUILD for python-pycparser and not python2-pycparser ... i guess i posted in the wrong one sry
df8oe solution works removing and reinstalling.... so cant we force this uninstall in the PKGBUILD ? that would be a proper fix, i still think the PKGBUILD should be responsible as much as possible to guaranteeed an update path
I can confirm df8oe's solution works flawlessly. Thanks a lot!
@micsnare Just follow the guide to build in a clean chroot.
@boscowitch: There isn't "python " at any place in this PKGBUILD, it's all "python2 ". Also be aware that misusing the out of date flag for bug reports violates the AUR rules.
Are you sure that the clean chroot is the reason ?
not maybe a python3 installation, default in my arch for python is version 3 python2 is version2
the PKGBUILD seems to use python so 3 even though this is a python2 package
I downloaded the PKGBUILD, replaced all python with python2 and build it manually with makepkg and it works flawless!
So i would flag this package out of date since as far as i know the new default python version in arch is 3.
see ( sudo pacman -S python warning: python-3.10.1-2 is up to date -- reinstalling )
Pinned Comments
bionade24 commented on 2022-01-08 20:34 (UTC) (edited on 2022-01-08 20:40 (UTC) by bionade24)
If building the package fails for you, either build in a clean chroot or disable the tests, but at your own risk that the functionality will be faulty.
This package builds fine in a clean chroot: https://abs-cd.oscloud.info/cd_manager/python2-pycparser
This package is also available in my unofficial user repo: https://wiki.archlinux.org/title/Unofficial_user_repositories#oscloud