←back to thread

196 points bovem | 9 comments | | HN request time: 0.804s | source | bottom
1. Zamiel_Snawley ◴[] No.41143932[source]
I don’t see it on the main read me, what are the limitations/incompatibilities with CPython at this point in time? How “drop in ready” is it?
replies(4): >>41143994 #>>41144011 #>>41146031 #>>41146507 #
2. fastball ◴[] No.41143994[source]
They have a "What's Left?"[1] and the results of running RustPython against the CPython test suite[2] up on the website.

[1] https://rustpython.github.io/pages/whats-left

[2] https://rustpython.github.io/pages/regression-tests-results....

replies(1): >>41145439 #
3. ◴[] No.41144011[source]
4. snthpy ◴[] No.41145439[source]
sqlite3 is the main one on that list that jumps out at me.
5. rty32 ◴[] No.41146031[source]
This seems very weird to me. Anyone who is just slightly interested in the project would want to know if specs are fully implemented and this has parity with the "official implementation". Can't believe it's not in README.
6. lemurien ◴[] No.41146547[source]
Do you mean they would work like that to prevent an alternative implementation? This seems a bit far fetched.
7. dejw ◴[] No.41146654[source]
that's a bit harsh. c++ has specification and programs still break easily by just moving to a different compiler.
8. VagabundoP ◴[] No.41146691[source]
>The modus operandi of the shrinking set of people who took over CPython is to add new garbage so other implementations cannot keep up.

Ridiculous accusation bordering on paranoid.

9. HelloNurse ◴[] No.41147056[source]
I suppose you consider new Python features are "garbage" because you don't care about them?