#pyo3 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #pyo3, aggregated by home.social.
-
You can now use Ratatui in Python! 🐀🥳
🐍 **PyRatatui** — Python bindings for @ratatui_rs
💯 Build high-performance TUIs in Python with 35+ widgets, async & effects
🦀 Backed by Rust via PyO3
⭐ GitHub: https://github.com/pyratatui/pyratatui
#rustlang #ratatui #tui #python #library #bindings #pyo3 #terminal
-
ZODB has served the Zope and Plone community for over two decades. But its storage model — opaque pickle blobs and BTree-based catalog indexes — hasn't aged well. You can't query your data with SQL. You can't inspect object state without unpickling. And the catalog is a black box that lives inside the very database it indexes.
Time to change that. Four modules, one mission — get ZODB out of the pickle jar.
https://community.plone.org/t/zodb-out-of-the-pickle-jar/22832
-
RE: https://hachyderm.io/@itworldcup/115960578331633434
I'm tempted to do something with #PyO3 in celebration of the ongoing #ITWorldCup finals, no matter the outcome.
-
Как я Rust в Python встраивал
Rust все популярней, а вместе c этим создается много библиотек для Python на Rust. В данной статье узнаем, как создать простенькую библиотеку для Python на Rust на примере кодирования данных в Base 64.
-
-
Ah yes, the classic tale of #Python needing a lifeline, now through #Tauri and #Pyo3. 🤖 Because what could possibly go wrong when you mix #AI, #security, and a desperate attempt to stay relevant in the tech world? 🤦♂️ Just another day in the endless #GitHub maze of #innovation. 🌀
https://github.com/pytauri/pytauri #HackerNews #ngated -
Tauri binding for Python through Pyo3
https://github.com/pytauri/pytauri
#HackerNews #Tauri #Pyo3 #Python #bindings #open-source #development
-
Sharing a mutable reference between Rust and Python
https://blog.lilyf.org/posts/python-mutable-reference/
#ycombinator #django #templates #rust #python #pyo3 -
As a final preparation for the #PyO3 workshop tomorrow at #EuroPython, I have updated some exercises to ensure thread-safety. We are ready for #FreeThreaded #Python! Make sure you have the setup ready: https://github.com/Cheukting/py03_101
-
Are you interested in how #Rust changes the ecosystem in #Python? Are you creating Python libraries using Rust code via #PyO3? Show your interest in participating in Rust #Summit in #EuroPython 2025 now! (details in the comment)
-
At last night’s @mug meeting we looked at a lot of different solutions to #adventofcode day 1 in many different languages. Two that were very interesting to me were #Zig and #haskell. The way these two languages worked was really quite fascinating. After seeing real code in these two languages, I can tell they are not for me; but they were interesting and illuminating nonetheless.
There was a solution entirely in #SQL. Another in #vim9script. Another in #swiftlang #swift (I don’t think that one’s in the repo yet). I wrote several implementations myself. The one I felt most proud of is #Python with the core written in #rustlang #rust tied together with #PyO3. The one I felt was maybe the best tool for the job was entirely based on #pandas. As I said in a previous post, I tried to solve it in #polars, but the API exposed by Polars at least as far as I could tell, made it no better than simple lists in Python. I need to get deeper knowledge here.
The repo lives here: https://github.com/MichiganUnixUserGroup/MUG-2025-03-11-Advent-of-Code.
-
I did, during my previously mentioned workshop, do one thing to offend #Rust’s #borrowchecker. I was implementing an Account struct that had a current balance and a Vec containing a history of balances. This was using #PyO3 so there are some special types. Because of inheritance, I have self_ instead of self. Here’s the bad thing I said:
self_.history.push(self_.as_super().balance);
@algo_luca had to explain it to me. He didn’t even need to think about it. He instantly knew what was wrong. Now I am enlightened. I won’t make this particular kind of mistake again.
Of course the mistake is that I was trying to use a mutable reference (so I could push to history) and anything else at the same time.
-
Today I successfully wrote a #Rust implementation using #PyO3 that served as a package in my #Python program. Part of a presentation I’m doing for @mug. It’s day 1 of Advent of Code. I wrote four Python versions progressing from the simplest thing you would reasonably write up to packages and Rust. Here’s [the repo](https://github.com/MichiganUnixUserGroup/MUG-2025-03-11-Advent-of-Code). Lots of people in this repo demoing lots of languages. My stuff lives at `code\Python\wolf`
-
I’ve been writing a lot of #Python and #rust together over the last week or so, and I have things to say about that.
* even though I’ve been using Python for decades; when working in two languages at the same time I have to keep double-checking the syntax on _both_
* wow! Python can be a lot more succinct than Rust
I really like them both very much. Neither one is a replacement for the other. I’m a huge fan of types. The bigger your plans, the more important types are. They’re required in Rust, but I always use the in Python, too.
#PyO3 has proven to be incredible, though I still have so much to learn. What an amazing way to combine the two tools. Thanks. #mainmatter for leading me to this path.
-
I just attended a two-day workshop on #rust-#Python interoperability (the main glue between the two was #PyO3). Run by @mainmatter. The instructor was @algo_luca Two days, four hours each. Speeding up big Python programs with little bits of Rust. I enjoyed every second of it. Luca either knew the answer to your question off the top of his head or he was willing to dig right then to find it. The exercises were good as well as deep; the instruction was effective, smart, and respectful; the results were exciting. I learned a lot. I would happily attend another event of the same caliber.
Edit: originally I mistakenly said Mattermost. I meant to say Mainmatter. Thanks for pointing that out.
-
A cóż ja mogę teraz robić, w piątkowy wieczór?
Oczywiście, że wysyłam zgłoszenia do przypadkowych projektów #Python / #RustLang, prosząc o aktualizację wersji #PyO3 i nowe wydanie, po to, by móc wprowadzić wsparcie #PyPy 3.11 w #Gentoo. Bo, rzecz jasna, prawidłowy sposób rozwoju współczesnych paczek Pythona to przypadkowo przepisywanie ich fragmentów w Ruście, a potem ignorowanie konieczności aktualizowania zależności przez pół roku albo dłużej.
Tak, mówię o tych wszystkich paczkach, które w ogóle jeszcze nie wspierają PyO3 0.23.x.
A potem jeszcze przyjdą i powiedzą, że powinniśmy zostawić temat zależności i bezpieczeństwa autorom projektów.
-
What could I be doing right now, on a Friday evening?
Of course filing bugs on random #Python / #RustLang packages requesting a #PyO3 version update and a new release, to support #PyPy 3.11 in #Gentoo. Because obviously the right way to maintain modern Python packages is to rewrite random parts of them in Rust, then neglect updating their dependencies for half a year or more.
Yes, I'm talking about all the packages that don't even support PyO3 0.23.x yet.
And then they'll come and say that we should leave dependency management and security to upstreams.
-
Dobra wiadomość: jest łatka dla #PyO3 dla wsparcia #PyPy 3.11, więc ruszamy z aktualizacjami w #Gentoo do przodu.
Złe wiadomości:
1. Mówimy o #RustLang, więc każdą paczkę trzeba łatać z osobna.
2. Nie chcemy trzymać dziesiątek kopii tej samej łatki, więc chcemy ją ciągnąć z sieci. Niestety, nie możemy użyć oryginalnej kopii, bo modyfikuje pliki, których nie znajdziemy w archiwum crate.
3. No więc trzymamy własną kopię tej łatki, ograniczoną do dostępnych plików. Niestety, pasuje tylko do wersji 0.23.4, a że mnóstwo paczek Pythona używa 0.23.3, to mamy sporo aktualizowania. Ale przynajmniej w większości przypadków wystarczy podmienić cyferki na liście `CRATES`, i wykasować `Cargo.lock`.
4. …no chyba że dana paczka akurat wymusza dokładnie 0.23.3, albo używa 0.22.x bądź starszej wersji. Wtedy bez łatania `Cargo.toml` się nie obędzie.No ale idziemy do przodu. Tyle że warto jeszcze wspomnieć, że z paczek Pythona robi się coraz większy bajzel cyklicznych zależności, ale to już inna bajka.
-
uvとPyO3でPythonからRustを呼ぶ①（プロジェクト作成・Hello World実行まで）
https://qiita.com/nukipei/items/f096a1df6c8074b16150?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
uvとPyO3でPythonからRustを呼ぶ①（プロジェクト作成・Hello World実行まで）
https://qiita.com/nukipei/items/f096a1df6c8074b16150?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
uvとPyO3でPythonからRustを呼ぶ①（プロジェクト作成・Hello World実行まで）
https://qiita.com/nukipei/items/f096a1df6c8074b16150?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
uvとPyO3でPythonからRustを呼ぶ①（プロジェクト作成・Hello World実行まで）
https://qiita.com/nukipei/items/f096a1df6c8074b16150?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
My recent work on #CBOR diagnostic tools has culminated in the release v0.0.7 of the cbor-edn #RustLang crate, and the cbor-diag v1.1.0 #Python package (which is powered by the former, #maturin and #PyO3).
It is now easy to receive CBOR data structure with internal tags, and have them display like this:
{1: IP'2001:db8::1', 3: DT'2025-01-14T13:27:49Z'}
https://cbor-diag.readthedocs.io/en/latest/
https://docs.rs/cbor-edn/latest/cbor_edn/ -
My recent work on #CBOR diagnostic tools has culminated in the release v0.0.7 of the cbor-edn #RustLang crate, and the cbor-diag v1.1.0 #Python package (which is powered by the former, #maturin and #PyO3).
It is now easy to receive CBOR data structure with internal tags, and have them display like this:
{1: IP'2001:db8::1', 3: DT'2025-01-14T13:27:49Z'}
https://cbor-diag.readthedocs.io/en/latest/
https://docs.rs/cbor-edn/latest/cbor_edn/ -
My recent work on #CBOR diagnostic tools has culminated in the release v0.0.7 of the cbor-edn #RustLang crate, and the cbor-diag v1.1.0 #Python package (which is powered by the former, #maturin and #PyO3).
It is now easy to receive CBOR data structure with internal tags, and have them display like this:
{1: IP'2001:db8::1', 3: DT'2025-01-14T13:27:49Z'}
https://cbor-diag.readthedocs.io/en/latest/
https://docs.rs/cbor-edn/latest/cbor_edn/ -
My recent work on #CBOR diagnostic tools has culminated in the release v0.0.7 of the cbor-edn #RustLang crate, and the cbor-diag v1.1.0 #Python package (which is powered by the former, #maturin and #PyO3).
It is now easy to receive CBOR data structure with internal tags, and have them display like this:
{1: IP'2001:db8::1', 3: DT'2025-01-14T13:27:49Z'}
https://cbor-diag.readthedocs.io/en/latest/
https://docs.rs/cbor-edn/latest/cbor_edn/ -
My recent work on #CBOR diagnostic tools has culminated in the release v0.0.7 of the cbor-edn #RustLang crate, and the cbor-diag v1.1.0 #Python package (which is powered by the former, #maturin and #PyO3).
It is now easy to receive CBOR data structure with internal tags, and have them display like this:
{1: IP'2001:db8::1', 3: DT'2025-01-14T13:27:49Z'}
https://cbor-diag.readthedocs.io/en/latest/
https://docs.rs/cbor-edn/latest/cbor_edn/
