4 ms·
Okay, so what's the catch? I see no Windows support and no ABI compatibility, but other than that it's just... a drop in replacement and I get a 30% speedup? I'
by yjftsjthsd-h 5y ago
Okay, so what's the catch? I see no Windows support and no ABI compatibility, but other than that it's just... a drop in replacement and I get a 30% speedup? I'm aware that "too good to be true" is only a heuristic, but it generally holds; am I missing some great caveat?
- O5vYtytb 5y agoNo abi compat is a big one. But if your writing pure python go for it.
- yjftsjthsd-h 5y agoHonestly, even that seems trivial? By my reading of https://github.com/pyston/pyston#installing-packages https://github.com/pyston/pyston#installing-packages , the only impact is that when you install (compiled) libraries they need to be recompiled, just like if you use Alpine (which is also ABI-incompatible because it uses musl libc), which is a little bit of pain at build/packaging time but doesn't actually break anything (i.e. there are no libraries that you can't use, just libraries with an extra compile step) and doesn't affect runtime behavior at all. EDIT: I should caveat "doesn't actually break anything" with "although it does require you to install build dependencies because you have to compile the package from source instead of using a prebuilt wheel". I don't think this changes the substance of my comment but best to be precise.
- kanaffa12345 5y ago