Earlier quoted context omitted.
I can't come up with any cases where cpython would compile that rustc can't target. There are some more niche interpreters that can run on embedded stuff with no rustc support, but they are also subsets of python so it isn't like you can just pull a wheel file and expect it to work
For what it’s worth the GCC backend for rustc is making progress and rustc more generally supports a lot of embedded stuff already
Libraries Run Rust Inside Python (With PyO3)
21–30 of 41 posts
Re: Libraries Run Rust Inside Python (With PyO3)
#22Re: Libraries Run Rust Inside Python (With PyO3)
#23> reach for, a Rust extension does the work ai; dr, sorry
but it's a bit strange
It's too "clunky" for AI, like you stumble too much over the words when reading
If we take the first sentence that could have been from a German person, where such language structures aren't that uncommon.
I myself write a lot like that, and always have written like that, often in way worse ways, like sentences which never, not even after docent of words, end, and have levels of sub-sentence nesting no normal thinking human would want to read. (Through there are indicators of AI usage in pretty much every single sentence.
But at the same time the writing is too bad, for most current AI agents.
Like reading it is hard, in ways AI tends to not mess up. There are missing filler and glue words. Including some cases where I think they are probably grammatically require (through school was too long ago, so idk.). Sometimes it looks like a different language construct was used (like bracket or -- hyphen inlays) which then where search+replaced with commas.
So I really wonder what that is?
- a lower quality LLM Model?
- AI written text modified by hand leading to it having the worst of both worlds?
- or a human who has self learned English as a second language using AI and believes this is how normal English speakers write ...
and the last option is kinda frightening, because sooner or later we will have exactly that: People who write like AI "but worse" and likely do not even realize what they are doing.
---
EDIT/PS: Side note; Rust in Python is a decent match. PyO3 is far from perfect but decently usable. Spreading more awareness about it is nice. This comment is only about the writing structure not the content of the blog post.
Re: Libraries Run Rust Inside Python (With PyO3)
#24But does it work everywhere Python works? My main issue with this Rust move has always been compatibility. Python can be embedded and ran in a heck of a lot of places. What's the story when libraries that I may want to depend on are actually implemented in Rust and my target doesn't/can't handle the toolchain and there's no build target?
It won't work in those cases. Do you have explicit examples? I suspect this won't come up much as Rust has, IME, much broader target support. (Including platforms without a GPOS)
...Since the Gentoo Portage package manager indirectly depends on cryptography, ""we will probably have to entirely drop support for architectures that are not supported by Rust"". He listed five architectures that are not supported by upstream Rust (alpha, hppa, ia64, m68k, and s390) and an additional five that are supported but do not have Gentoo Rust packages (mips, 32-bit ppc, sparc, s390x, and riscv).
[0] https://news.ycombinator.com/item?id=26097153Re: Libraries Run Rust Inside Python (With PyO3)
#25Earlier quoted context omitted.
I can't come up with any cases where cpython would compile that rustc can't target. There are some more niche interpreters that can run on embedded stuff with no rustc support, but they are also subsets of python so it isn't like you can just pull a wheel file and expect it to work
For what it’s worth the GCC backend for rustc is making progress and rustc more generally supports a lot of embedded stuff already
Re: Libraries Run Rust Inside Python (With PyO3)
#26I was a bit nervous about this trend when it started picking up because I care about Pyodide (Python running via WebAssembly) and libraries that use PyO3 might not work in Pyodide. Thankfully that's now been mostly solved - you can compile and publish WASM builds of Rust or C extensions on PyPI now and a Pyodide can then use them. Here's the WASM build of the Rust-including Pydantic-core package for example: https://…
Re: Libraries Run Rust Inside Python (With PyO3)
#27How much of the existing PyPI ecosystem do you think could realistically work this way without package authors doing anything specifically for WASM?
Tokio doesn't work yet but epoll-based support for it is in progress.
Re: Libraries Run Rust Inside Python (With PyO3)
#28Re: Libraries Run Rust Inside Python (With PyO3)
#29Earlier quoted context omitted.
For what it’s worth the GCC backend for rustc is making progress and rustc more generally supports a lot of embedded stuff already
How’s that GCC backend coming along? I could look it up, but I bet others would like to hear about it too.
They’re plugging away at it. A major milestone was getting unwinding to work. I’d say they’re getting quite close and it’s getting better and better. It’s usable for Linux kernel compilation I believe which unlocks Rust to be used for the non-driver components in the kernel.
Re: Libraries Run Rust Inside Python (With PyO3)
#30But does it work everywhere Python works? My main issue with this Rust move has always been compatibility. Python can be embedded and ran in a heck of a lot of places. What's the story when libraries that I may want to depend on are actually implemented in Rust and my target doesn't/can't handle the toolchain and there's no build target?
It's nice that, as long as it's compiled for the correct architecture, I don't have to install the language to run the application.