Re: About rust and python

On Mon, Mar 16, 2020 at 10:06 AM vitalije wrote: > You should take a look at [PyOxidizer , PyO3 , neon , and mini_leo ]. Thanks for these links.

Re: About rust and python

> > it loads LeoPyRef.leo along with all at-file nodes in less than 80ms. > > The extension module has also an iterator of nodes which iterates tree of > 9250 nodes in 7ms. Drawing tree with such an iterator shouldn't take too > long. > > Oh, and it doesn't use multi processor cores at all.

Re: About rust and python

You should take a look at the PyOxidizer I haven't used it yet, but it seems promising. The other one you should look at (and I have been using it) is PyO3 , for writing python extensions in rust. There is also neon

Re: About rust and python

On Monday, March 16, 2020 at 6:17:17 AM UTC-5, Edward K. Ream wrote: > [I might study] RustPython ...just to see what real rust code looks like. I have just created #1538

Re: About rust and python

On Mon, Mar 16, 2020 at 9:02 AM Thomas Passin wrote: >> Imo, RustPython is not likely to go anywhere, unless a company like Google or Apple supports it. For Python's core devs, RustPython probably looks like a fork. Having just emerged from the trauma of the Python 3 fork, my guess is that they

Re: About rust and python

On Monday, March 16, 2020 at 7:17:17 AM UTC-4, Edward K. Ream wrote: > > In the "What's Next post > I > said: > > "As far as wasm [WebAssembly] goes, rust has a (temporary?) advantage over > python, because wasm doesn't yet

About rust and python

In the "What's Next post I said: "As far as wasm [WebAssembly] goes, rust has a (temporary?) advantage over python, because wasm doesn't yet support garbage collection." Well, what about writing the python interp in rust?