Mastodon

SnackOverflowI confess: I wanted to try out <a href="https://darmstadt.social/tags/PyO3" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyO3</a> and started writing a <a href="https://darmstadt.social/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a> wrapper for the <a href="https://darmstadt.social/tags/Reticulum" class="mention hashtag" rel="nofollow noopener" target="_blank">#Reticulum</a> reference implementation, which happens to be in <a href="https://darmstadt.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a>. There's no easy way for me to say this, but it could actually be done! It boggles the mind, but given enough time and energy, I could actually wrap the RNS package in a Rust crate.Don't worry: Nobody is going there … but what a time to be alive!For those looking for a Reticulum crate: - <a href="https://github.com/BeechatNetworkSystemsLtd/Reticulum-rs" rel="nofollow noopener" translate="no" target="_blank">https://github.com/BeechatNetworkSystemsLtd/Reticulum-rs</a> - <a href="https://lib.rs/crates/reticulum" rel="nofollow noopener" translate="no" target="_blank">https://lib.rs/crates/reticulum</a> (alpha)

Cheuk Ting HoAs a final preparation for the <a href="https://fosstodon.org/tags/PyO3" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyO3</a> workshop tomorrow at <a href="https://fosstodon.org/tags/EuroPython" class="mention hashtag" rel="nofollow noopener" target="_blank">#EuroPython</a>, I have updated some exercises to ensure thread-safety. We are ready for <a href="https://fosstodon.org/tags/FreeThreaded" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeThreaded</a> <a href="https://fosstodon.org/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a>! Make sure you have the setup ready: <a href="https://github.com/Cheukting/py03_101" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Cheukting/py03_101</a>

oylenshpeegulHey, you can use <a href="https://mastodon.social/tags/PyO3" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyO3</a> to call <a href="https://mastodon.social/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a> from <a href="https://mastodon.social/tags/Hy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Hy</a>!<a href="https://oylenshpeegul.gitlab.io/blog/posts/20250603/" rel="nofollow noopener" translate="no" target="_blank">https://oylenshpeegul.gitlab.io/blog/posts/20250603/</a>

gigapixelHad a lot of fun presenting at rust Basel yesterday <a href="https://rust-basel.ch/" rel="nofollow noopener" translate="no" target="_blank">https://rust-basel.ch/</a> about diplomat <a href="https://github.com/rust-diplomat/diplomat" rel="nofollow noopener" translate="no" target="_blank">https://github.com/rust-diplomat/diplomat</a> . Here’re the slides (repo) <a href="https://github.com/jcrist1/diplomat-talk" rel="nofollow noopener" translate="no" target="_blank">https://github.com/jcrist1/diplomat-talk</a> Also we’ll have an introductory workshop to CLI tools in early July <a href="https://www.meetup.com/rust-basel/events/307567391/?eventOrigin=group_upcoming_events" rel="nofollow noopener" translate="no" target="_blank">https://www.meetup.com/rust-basel/events/307567391/?eventOrigin=group_upcoming_events</a>I’ll also be presenting at the Basel data science Meetup on how you can use PyO3 <a href="https://www.meetup.com/basel-data-scientists/events/308069592/?eventOrigin=group_upcoming_events" rel="nofollow noopener" translate="no" target="_blank">https://www.meetup.com/basel-data-scientists/events/308069592/?eventOrigin=group_upcoming_events</a><a href="https://mathstodon.xyz/tags/basel" class="mention hashtag" rel="nofollow noopener" target="_blank">#basel</a> <a href="https://mathstodon.xyz/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a> <a href="https://mathstodon.xyz/tags/rustBasel" class="mention hashtag" rel="nofollow noopener" target="_blank">#rustBasel</a> <a href="https://mathstodon.xyz/tags/diplomat" class="mention hashtag" rel="nofollow noopener" target="_blank">#diplomat</a> <a href="https://mathstodon.xyz/tags/dataScience" class="mention hashtag" rel="nofollow noopener" target="_blank">#dataScience</a> <a href="https://mathstodon.xyz/tags/PyO3" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyO3</a>

JacketAfter working a bit on a project mixing <a href="https://tech.lgbt/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> and <a href="https://tech.lgbt/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a> using <a href="https://tech.lgbt/tags/pyo3" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyo3</a> I can say that while this setup is really useful it is not great in exception handling. If it's in Python you get a python style and if it's in rust you get a rust style exception that doesn't have a traceback... By default? I saw that there might be a way to compile it with a traceback but I'm not sure. What I would like at least it to add the traceback from python automatically to the rust exception. I think it's something that pyo3 could improve.

Cheuk Ting HoAre you interested in how <a href="https://fosstodon.org/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a> changes the ecosystem in <a href="https://fosstodon.org/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a>? Are you creating Python libraries using Rust code via <a href="https://fosstodon.org/tags/PyO3" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyO3</a>? Show your interest in participating in Rust <a href="https://fosstodon.org/tags/Summit" class="mention hashtag" rel="nofollow noopener" target="_blank">#Summit</a> in <a href="https://fosstodon.org/tags/EuroPython" class="mention hashtag" rel="nofollow noopener" target="_blank">#EuroPython</a> 2025 now! (details in the comment)

WolfAt last night’s <a href="https://hachyderm.io/@mug" class="u-url mention" rel="nofollow noopener" target="_blank">@mug</a> meeting we looked at a lot of different solutions to <a href="https://hachyderm.io/tags/adventofcode" class="mention hashtag" rel="nofollow noopener" target="_blank">#adventofcode</a> day 1 in many different languages. Two that were very interesting to me were <a href="https://hachyderm.io/tags/Zig" class="mention hashtag" rel="nofollow noopener" target="_blank">#Zig</a> and <a href="https://hachyderm.io/tags/haskell" class="mention hashtag" rel="nofollow noopener" target="_blank">#haskell</a>. 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 <a href="https://hachyderm.io/tags/SQL" class="mention hashtag" rel="nofollow noopener" target="_blank">#SQL</a>. Another in <a href="https://hachyderm.io/tags/vim9script" class="mention hashtag" rel="nofollow noopener" target="_blank">#vim9script</a>. Another in <a href="https://hachyderm.io/tags/swiftlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#swiftlang</a> <a href="https://hachyderm.io/tags/swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#swift</a> (I don’t think that one’s in the repo yet). I wrote several implementations myself. The one I felt most proud of is <a href="https://hachyderm.io/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> with the core written in <a href="https://hachyderm.io/tags/rustlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#rustlang</a> <a href="https://hachyderm.io/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a> tied together with <a href="https://hachyderm.io/tags/PyO3" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyO3</a>. The one I felt was maybe the best tool for the job was entirely based on <a href="https://hachyderm.io/tags/pandas" class="mention hashtag" rel="nofollow noopener" target="_blank">#pandas</a>. As I said in a previous post, I tried to solve it in <a href="https://hachyderm.io/tags/polars" class="mention hashtag" rel="nofollow noopener" target="_blank">#polars</a>, 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: <a href="https://github.com/MichiganUnixUserGroup/MUG-2025-03-11-Advent-of-Code" rel="nofollow noopener" translate="no" target="_blank">https://github.com/MichiganUnixUserGroup/MUG-2025-03-11-Advent-of-Code</a>.

rustmeetWant to combine the power of Rust with the flexibility of Python? 🦀🐍 Kajetan Rachwał - ML Engineer from Robotec.ai will show you how! Join his talk, "Magic of Bindings: Introduction to Rust-Python bindings" to learn practical techniques for leveraging libraries like Polars and Orjson, using tools like PyO3 and Maturin and building high-performance applications through seamless integration.For more information about our speaker and his talk, visit: <a href="https://rustmeet.eu/en/magic-of-bindings-introduction-to-rust-python-bindings/" rel="nofollow noopener" translate="no" target="_blank">https://rustmeet.eu/en/magic-of-bindings-introduction-to-rust-python-bindings/</a><a href="https://c.im/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://c.im/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a> <a href="https://c.im/tags/rustlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#rustlang</a> <a href="https://c.im/tags/pyO3" class="mention hashtag" rel="nofollow noopener" target="_blank">#pyO3</a>

Rasmus LindegaardBeen spending the week so far paying with <a href="https://fosstodon.org/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a> and <a href="https://fosstodon.org/tags/Pyo3" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pyo3</a>.Rust is friggin amazing.And so is Pyo3.I've been working in python for the last 2-3 years, and learned that its a really... Let's be diplomatic and say it's not for me. The idea of being able to just code modules in Rust and then let people use that in their python code sits well with me.

WolfI did, during my previously mentioned workshop, do one thing to offend <a href="https://hachyderm.io/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a>’s <a href="https://hachyderm.io/tags/borrowchecker" class="mention hashtag" rel="nofollow noopener" target="_blank">#borrowchecker</a>. I was implementing an Account struct that had a current balance and a Vec containing a history of balances. This was using <a href="https://hachyderm.io/tags/PyO3" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyO3</a> 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);<a href="https://hachyderm.io/@algo_luca" class="u-url mention" rel="nofollow noopener" target="_blank">@algo_luca</a> 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.

WolfToday I successfully wrote a <a href="https://hachyderm.io/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a> implementation using <a href="https://hachyderm.io/tags/PyO3" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyO3</a> that served as a package in my <a href="https://hachyderm.io/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> program. Part of a presentation I’m doing for <a href="https://hachyderm.io/@mug" class="u-url mention" rel="nofollow noopener" target="_blank">@mug</a>. 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](<a href="https://github.com/MichiganUnixUserGroup/MUG-2025-03-11-Advent-of-Code" rel="nofollow noopener" translate="no" target="_blank">https://github.com/MichiganUnixUserGroup/MUG-2025-03-11-Advent-of-Code</a>). Lots of people in this repo demoing lots of languages. My stuff lives at `code\Python\wolf`

WolfI’ve been writing a lot of <a href="https://hachyderm.io/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> and <a href="https://hachyderm.io/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a> 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 RustI 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. <a href="https://hachyderm.io/tags/PyO3" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyO3</a> has proven to be incredible, though I still have so much to learn. What an amazing way to combine the two tools. Thanks. <a href="https://hachyderm.io/tags/mainmatter" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainmatter</a> for leading me to this path.

WolfI just attended a two-day workshop on <a href="https://hachyderm.io/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#rust</a>-<a href="https://hachyderm.io/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> interoperability (the main glue between the two was <a href="https://hachyderm.io/tags/PyO3" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyO3</a>). Run by <a href="https://bird.makeup/users/mattermost" class="u-url mention" rel="nofollow noopener" target="_blank">@mattermost</a>. The instructor was <a href="https://hachyderm.io/@algo_luca" class="u-url mention" rel="nofollow noopener" target="_blank">@algo_luca</a> 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.

mgorny-nyan (on) :autism:🙀🚂🐧A cóż ja mogę teraz robić, w piątkowy wieczór?Oczywiście, że wysyłam zgłoszenia do przypadkowych projektów <a href="https://pol.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> / <a href="https://pol.social/tags/RustLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustLang</a>, prosząc o aktualizację wersji <a href="https://pol.social/tags/PyO3" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyO3</a> i nowe wydanie, po to, by móc wprowadzić wsparcie <a href="https://pol.social/tags/PyPy" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyPy</a> 3.11 w <a href="https://pol.social/tags/Gentoo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gentoo</a>. 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.

mgorny-nyan (he) :autism:🙀🚂🐧What could I be doing right now, on a Friday evening?Of course filing bugs on random <a href="https://social.treehouse.systems/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> / <a href="https://social.treehouse.systems/tags/RustLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustLang</a> packages requesting a <a href="https://social.treehouse.systems/tags/PyO3" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyO3</a> version update and a new release, to support <a href="https://social.treehouse.systems/tags/PyPy" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyPy</a> 3.11 in <a href="https://social.treehouse.systems/tags/Gentoo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gentoo</a>. 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.

mgorny-nyan (on) :autism:🙀🚂🐧Dobra wiadomość: jest łatka dla <a href="https://pol.social/tags/PyO3" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyO3</a> dla wsparcia <a href="https://pol.social/tags/PyPy" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyPy</a> 3.11, więc ruszamy z aktualizacjami w <a href="https://pol.social/tags/Gentoo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gentoo</a> do przodu.Złe wiadomości:1. Mówimy o <a href="https://pol.social/tags/RustLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustLang</a>, 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.<a href="https://pol.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a>

mgorny-nyan (he) :autism:🙀🚂🐧Good news is, there's an upstream patch for <a href="https://social.treehouse.systems/tags/PyO3" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyO3</a> to support <a href="https://social.treehouse.systems/tags/PyPy" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyPy</a> 3.11, so the <a href="https://social.treehouse.systems/tags/Gentoo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gentoo</a> updates are progressing.Bad news:1. Since it's <a href="https://social.treehouse.systems/tags/RustLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustLang</a>, we need to patch every single package separately. 2. To avoid keeping a dozen copies of the same patch, we'd like to fetch it. Unfortunately, we can't use upstream pull request directly since it edits a bunch of files that aren't in the crate. 3. Ok, so we host a modified patch and we're good here. Unfortunately, the patch doesn't apply cleanly to the previous minor release (0.23.3), so we need to manually update PyO3 in a lot of <a href="https://social.treehouse.systems/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> packages. Good news is, that's usually updating our `CRATES` list and removing `Cargo.lock`. 4. …except for these packages that pin exactly to 0.23.3, or are still on 0.22.x or earlier. Then we also need to patch `Cargo.toml`.But yeah, things are going forward. And then of course Python packages are becoming an increasingly convoluted mess of cyclic dependencies, but that's another story.

mgorny-nyan (on) :autism:🙀🚂🐧Mi się wydaje, czy błędy testów w Maturinie są cosik straszne?(tak, oczywiście, że <a href="https://pol.social/tags/PyO3" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyO3</a> blokuje teraz portowanie do <a href="https://pol.social/tags/PyPy" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyPy</a> 3.11, i będziemy mieli z tym od jasnej cholery roboty, bo przecież każda zasrana paczka będzie wymagać starej wersji)<a href="https://pol.social/tags/Gentoo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gentoo</a> <a href="https://pol.social/tags/Maturin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Maturin</a> <a href="https://pol.social/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> <a href="https://pol.social/tags/RustLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustLang</a>

mgorny-nyan (he) :autism:🙀🚂🐧Is it just me or are <a href="https://social.treehouse.systems/tags/Maturin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Maturin</a> test failures just creepy?(yes, of course <a href="https://social.treehouse.systems/tags/PyO3" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyO3</a> is now a major blocker for <a href="https://social.treehouse.systems/tags/PyPy" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyPy</a> 3.11, and will require tons of work because of all the dependency pinning)<a href="https://social.treehouse.systems/tags/Gentoo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gentoo</a> <a href="https://social.treehouse.systems/tags/Python" class="mention hashtag" rel="nofollow noopener" target="_blank">#Python</a> <a href="https://social.treehouse.systems/tags/RustLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#RustLang</a>

MainmatterSpeed up your Python with Rust! Join our hands-on online workshop to learn all about Rust-Python Interoperability with <a href="https://hachyderm.io/@algo_luca" class="u-url mention" rel="nofollow noopener" target="_blank">@algo_luca</a> and <a href="https://mastodon.nl/@hdoordt" class="u-url mention" rel="nofollow noopener" target="_blank">@hdoordt</a> . Dive deep into PyO3, Rust-powered Python extensions, concurrency, and more!🦀 Details & registration ➡️ <a href="https://ti.to/mainmatter/rust-python-feb-2025" rel="nofollow noopener" translate="no" target="_blank">https://ti.to/mainmatter/rust-python-feb-2025</a> <a href="https://fosstodon.org/tags/rustlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#rustlang</a> <a href="https://fosstodon.org/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://fosstodon.org/tags/rustpython" class="mention hashtag" rel="nofollow noopener" target="_blank">#rustpython</a> <a href="https://fosstodon.org/tags/PyO3" class="mention hashtag" rel="nofollow noopener" target="_blank">#PyO3</a> <a href="https://fosstodon.org/tags/mainmatter" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainmatter</a>

Recent searches

Search options

Administered by:

Server stats:

#PyO3