4 ms·

i'm still waiting for a 100% compatible pypy implementation. People will not switch if "python" can't run on it. Like it or not, but CPython is the standard pyt

i'm still waiting for a 100% compatible pypy implementation. People will not switch if "python" can't run on it. Like it or not, but CPython is the standard python. Anyone know where unladen swallow ended up? I feel like the improved python interpreter is a pipe dream, but this is coming from someone who has long moved on from python to go due to pythons scaling troubles ( in my unique environment)

wyldfire 9y ago
> People will not switch if "python" can't run on it. For my use, it's been remarkably close to CPython. Where does it fall short for you? I think it's a design goal to match CPython behavior, so I think it would be rare if they were to NOFIX a doesnt-match-CPython bug. If you're writing anything other than I/O bound code in pure python, you're probably doing it wrong. Write an extension in C or rust for the inner loops and their critical data structures, and keep everything else in python.
- bastawhiz 9y ago
  In my experience, as someone who runs a fairly hefty Python application, the biggest source of incompatibility is the C extensions. One that's a thorn in my side is psycopg2. There's a version that works with cffi, but then you're crossing your fingers hoping that it matches the main psycopg2 package in terms of functionality and security updates. I would gladly throw money at someone to figure out how to take the juicy compat bits from Pyston and bring them into Pypy.
bastawhiz 9y ago
> i'm still waiting for a 100% compatible pypy implementation. Then please donate! https://pypy.org/py3donate.html https://pypy.org/py3donate.html Building something compatible with modern Python (especially as new features and syntax seem to be piling up every month) is hard work. > Anyone know where unladen swallow ended up? Google killed it. Turns out it wasn't worth the effort. Dropbox came to the same conclusion when they abandoned Pyston.

wyldfire 9y ago

> People will not switch if "python" can't run on it. For my use, it's been remarkably close to CPython. Where does it fall short for you? I think it's a design goal to match CPython behavior, so I think it would be rare if they were to NOFIX a doesnt-match-CPython bug. If you're writing anything other than I/O bound code in pure python, you're probably doing it wrong. Write an extension in C or rust for the inner loops and their critical data structures, and keep everything else in python.

bastawhiz 9y ago
In my experience, as someone who runs a fairly hefty Python application, the biggest source of incompatibility is the C extensions. One that's a thorn in my side is psycopg2. There's a version that works with cffi, but then you're crossing your fingers hoping that it matches the main psycopg2 package in terms of functionality and security updates. I would gladly throw money at someone to figure out how to take the juicy compat bits from Pyston and bring them into Pypy.

bastawhiz 9y ago

> i'm still waiting for a 100% compatible pypy implementation. Then please donate! https://pypy.org/py3donate.html https://pypy.org/py3donate.html Building something compatible with modern Python (especially as new features and syntax seem to be piling up every month) is hard work. > Anyone know where unladen swallow ended up? Google killed it. Turns out it wasn't worth the effort. Dropbox came to the same conclusion when they abandoned Pyston.