-
Notifications
You must be signed in to change notification settings - Fork 145
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
ncurses 5 -> 6 transition means we probably need to drop some libraries from the manylinux whitelist #286
Comments
Confirmation: (Thanks to @squeaky-pl for pointing this out) |
This might cause some "fun" for people, but so it goes...:
I guess anaconda must have noticed this already given that they're now shipping ncurses: https://anaconda.org/anaconda/ncurses |
Is there an easy way to check which projects on pypi rely on ncurses 5 being part of the PEP513 whitelist to be able to notify the maintainers? |
I manually walked top 20 results for curses and ncurses on pypi and didn't find any manylinux wheels. But of course that doesn't mean they are not there. |
I don't know of an easy way. I suppose it wouldn't be hard to get a list of all manylinux wheels (via the API or the bigquery download logs – assuming all wheels are downloaded at least once – or asking Donald) and then writing some script to grovel over them to see what libraries they link to. But it would be annoying :-) Is it a high priority? I guess the default if we do nothing is that projects will be notified by a combination of (a) complaints from Fedora users, and (b) complaints from auditwheel when they try to release a new version. |
+1 |
Apparently Sabayon Linux is also using ncurses6. See conda-forge/ncurses-feedstock#29 (comment) |
|
The PEP 513 whitelist includes
libpanelw.so.5
andlibncursesw.so.5
, both of which are part of ncurses version 5.But apparently the new hostness is ncurses 6, which breaks ABI with ncurses 5. I'm told that Fedora 24 and successors have already switched to ncurses 6, with the ncurses 5 libraries being available in a compatibility package, but not installed by default. So... I guess these have to be dropped from the whitelist.
The text was updated successfully, but these errors were encountered: