-
Notifications
You must be signed in to change notification settings - Fork 51
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
Unable to install the latest pysqlite3-binary #40
Comments
On debian 10:
Not sure what to tell you. |
For others who may find this: I had the same issue trying to install pysqlite3-binary 0.5.0 on Python 3.8.10 on Ubuntu 20.04. Upgrading pip with |
@pypa is determined to make everything complicated apparently. What a joke of an organization. |
I had a similar issue, and I found that centos 7 which @hiteshthavnani was using has glibc 2.17:
So, a Was there a conscious decision to drop |
Pypa have declared that manylinux1 is not supported anymore, as of about 16 months ago: pypa/manylinux#994 You have options:
|
I see, is it possible to have wheels which are more permissive though ? Earlier pysqlite3-binary supported glibc 2.5+ Supporting manylinux2010 aka manylinux_2_12 aka glibc 2.12+ Legacy formats: https://peps.python.org/pep-0600/#legacy-manylinux-tags |
If you'd like to set up a pypi project that tracks You can easily modify the wheel-building scripts in the To build wheels for 3.10+ I believe was what necessitated the switch to manylinux 2_24. pypa are a bunch of clowns who don't care much about compatibility, so I am stuck following their dubious path. |
I am trying to install latest pysqlite3-binary 0.4.7 but failed to do. I am using centos 7.9.2009 as the VM and python 3.7.12.
[root@vm] # pip install pysqlite3-binary==0.4.7.post6
ERROR: Could not find a version that satisfies the requirement pysqlite3-binary==0.4.7.post6 (from versions: 0.4.1.post1, 0.4.2, 0.4.3, 0.4.4, 0.4.5, 0.4.6)
ERROR: No matching distribution found for pysqlite3-binary==0.4.7.post6
Please let me know if we need more info at my end.
The text was updated successfully, but these errors were encountered: