-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Got "sorry, but this version only supports 100 named groups" while installing #3187
Comments
This is due to eliben/pycparser#148 |
OpenStack Kolla failing with the same error |
As a temporary workaround (please do not use this in perpetuity, you will regret it) you should be able to do |
@reaperhulk Still getting |
|
Same problem here. |
Does not work for me (--no-binary pycparse too). May be exists hack to fix it in developer machine? |
As with @lukashes neither |
@BTheunissen did you try |
@eka Apologies, I did initially but I messed up my original response, now edited. |
Same problem here |
Worked after pycparser reinstall. |
For those with problems with --no-binary, that options is on latest versions of pip, try to upgrade pip |
Thanks for the work around! We appreciate it over here. |
I also started having this problem this morning. |
What about forcing the pyparser requirement to a known and stable version? |
@xavierhardy
|
We don't directly depend on pycparser so we can't pin it. |
@pporada-gl, yes, I've seen it, I'm just suggesting a cleaner and longer-term workaround. If you add in your project dependencies (before
That fixes it too. Up to you to choose which workaround you prefer. Or using the shell pip install pycparser==2.13 |
Pinning the version does nothing because nothing prevents someone from uploading a bad wheel with the same version number. |
It's the version right before, the broken wheel is 2.14, but I get your point. |
Upstream has resolved this issue. If you have a local wheel cached you may need to delete I think. |
It looks like pycparser v2.15 was released a couple hours ago and I started receiving this same error again. The workaround for me was to install pycparser==2.14. |
eliben/pycparser#151 is the correct upstream bug to follow for resolution of this issue. |
Thanks @xavierhardy @alex - pinning version fixed issue for me. FWIW - was seeing it happen during upgrade of Ansible from |
Causing AssertionError: sorry, but this version only supports 100 named groups There is a bug with PyCParser - See pyca/cryptography#3187
Don't use the wheels provided by pycparser because they are inconsistent with the source. See: - eliben/pycparser#148 - pyca/cryptography#3187
pycparser 2.16 has been released and resolves this issue (again) |
Hello,
When I tried to install
cryptography
globally withpip install cryptography
on Ubuntu, I got the following error:Seems like there are other users having this bug recently as well: https://community.letsencrypt.org/t/certbot-auto-fails-while-setting-up-virtual-environment-complains-about-package-hashes/20529
I'm using a fresh installation of Ubuntu 16.04, with Python 2.7.12 and pip 8.1.2.
Thanks.
The text was updated successfully, but these errors were encountered: