Earlier quoted context omitted.
What are they violating, out of curiosity?
They list the repository as MIT licensed, but the python modules are distributed under the Python Software License which says: 2. Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python alone or in any derivative…
RustPython: A Python Interpreter Written in Rust
11–20 of 75 posts
Re: RustPython: A Python Interpreter Written in Rust
#12Earlier quoted context omitted.
idk but Jython didn't. So I don't think there's anything inherent in the language outside of CPython that calls for it.
Iirc, it mostly impact C modules in terms of the guarantees that are offered / not offered with GIL / NOGIL.
Yeah, but the ecosystem of C modules is what makes Python so great.
Re: RustPython: A Python Interpreter Written in Rust
#13Earlier quoted context omitted.
They list the repository as MIT licensed, but the python modules are distributed under the Python Software License which says: 2. Subject to the terms and conditions of this License Agreement, PSF hereby grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce, analyze, test, perform and/or display publicly, prepare derivative works, distribute, and otherwise use Python alone or in any derivative…
https://github.com/RustPython/RustPython/blob/main/Lib/PSF-L...
Thanks. I definitely missed it.
Re: RustPython: A Python Interpreter Written in Rust
#14This project doesn't seem to be adhering to the terms of the license of the original CPython modules that have been copied into its source repository.
[deleted]
Re: RustPython: A Python Interpreter Written in Rust
#15does it have a GIL
[deleted]
Re: RustPython: A Python Interpreter Written in Rust
#16I 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?
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....
sqlite3 is the main one on that list that jumps out at me.
Re: RustPython: A Python Interpreter Written in Rust
#17We waiting for Ruby ;)
Re: RustPython: A Python Interpreter Written in Rust
#18We waiting for Ruby ;)
Lookup Artichokeruby
Re: RustPython: A Python Interpreter Written in Rust
#19does it have a GIL
idk but Jython didn't. So I don't think there's anything inherent in the language outside of CPython that calls for it.
The complete semantics of Python object lifetime are expensive to implement in a compatible manner without a GIL. Jython got around this by not doing it, making it not fully compatible (yes, people do depend on objects being eagerly freed), just using the JVM GC instead. If you do want full compatibility, the choice is between single-threaded performance and parallelism.
Re: RustPython: A Python Interpreter Written in Rust
#20I 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?
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.