3 ms·
Only because they were compiled against cpython and not pypy right? If pypy had taken off/over, wouldn't it have been the other way around, where you need to do
by lucb1e 2y ago
Only because they were compiled against cpython and not pypy right? If pypy had taken off/over, wouldn't it have been the other way around, where you need to do a special compile any time you want to use a C project with cpython rather than using the prebuilt pypy-compatible version?
Edit: things seem to have changed since I last looked into compiling a dependency for pypy. https://doc.pypy.org/en/latest/faq.html#do-c-extension-modules-work-with-pypy https://doc.pypy.org/en/latest/faq.html#do-c-extension-modul... now says they support c-extension modules without modifications
The package you mentioned, some postgres thing apparently, mentions they support pypy 3.9 and 3.10: https://www.psycopg.org/psycopg3/docs/basic/install.html https://www.psycopg.org/psycopg3/docs/basic/install.html
- vasco 2y ago"Only": https://github.com/psycopg/psycopg/issues/154 https://github.com/psycopg/psycopg/issues/154
- cqqxo4zV46cp 2y agoBy “some postgres thing”, you mean…pretty much the only way that one would connect to Postgres in Python!
- lucb1e 2y agoRight, I just wasn't familiar with it (never heard this name before) and the only association I could think of for this abbreviated name was psyops and cops. Turns out it's actually for postgres which, of course, is a name I very well know. Didn't realize it was a well-known library!
- leadingthenet 2y agoThere's also https://github.com/MagicStack/asyncpg https://github.com/MagicStack/asyncpg