Rye: A Vision Continued

I think it’s interesting that rye uses ruff (<a href="https:&#x2F;&#x2F;github.com&#x2F;astral-sh&#x2F;ruff">https:&#x2F;&#x2F;github.com&#x2F;astral-sh&#x2F;ruff</a>) for linting and formatting. That’s the right call, and it’s also correct to bundle that in for an integrated dev experience.<p>I had to guess, that’s the path that the Astral team would take as well - expand ruff’s capabilities so it can do everything a Python developer needs. So the vision that Armin is describing here might be achieved by ruff eventually. They’d have an advantage that they’re not a single person maintenance team, but the disadvantage of needing to show a return to their investors.

I&#x27;ve been using rye for all of my python projects and it has generally been great. There&#x27;s a slightly annoying piece at the beginning when you first set up a project because &quot;rye init&quot; doesn&#x27;t actually produce a valid empty project - you have to add a few lines to pyproject.toml, but it certainly beats a lot of the other things I&#x27;ve used.

I&#x27;m usually using conda (mamba) nowadays as it also has binary support so I can use cuda etc. easily for deep learning purposes. Is this something Rye can also do?

I really like Rye and have used it a lot. Lately I&#x27;ve been using pixi more and more because of its cross-platform locking support, since I develop on Mac and deploy mostly to Linux. It also supports all cobda packages, which can be a big advantage.

I welcome anything that brings sanity to Python packaging. I have had several projects that I have been working with and have tried Poetry, Hatch, PDM and just plain old `requirements.txt` and I have been longing for something that Just Works like Rubygems and Bundler or Mix (Elixir) or Cargo, or even something that Sort of Works like npm or yarn.<p>I haven&#x27;t tried Rye yet, mostly because <i>from my (outsider&#x27;s) perspective</i>, Python version management is better handled externally like rvm, rbenv, or chruby for Ruby or rustup for Rust; I have recently shifted to using mise (formerly rtx) because unlike asdf it does not use shims by default.<p>Is there a good case for Rye over PDM if you leave out Python version management?

Regarding one man project. I always think of contributing back to the community. But things are not at all simple. I wish developers of projects would do weekly knowledge sharing videos. Or at least record themselves going through the code.

I&#x27;m about to do a full rewrite&#x2F;refactor of my flask app and will be starting fresh with Rye. I was using a cobbled together pyenv+virtualenv+bunch of other tools to manage it all, but was spending too much time on environment setup&#x2F;upkeep when I was not on my main laptop.<p>Rye is a one stop shop for everything that I need.

This is an impressive effort, no doubt. And Python packaging is in a woeful state. But I&#x27;m sorry, the <i>last</i> thing the ecosystem needs it <i>another</i> alternative!<p><a href="https:&#x2F;&#x2F;chriswarrick.com&#x2F;blog&#x2F;2023&#x2F;01&#x2F;15&#x2F;how-to-improve-python-packaging&#x2F;" rel="nofollow">https:&#x2F;&#x2F;chriswarrick.com&#x2F;blog&#x2F;2023&#x2F;01&#x2F;15&#x2F;how-to-improve-pyth...</a> <a href="https:&#x2F;&#x2F;xkcd.com&#x2F;927&#x2F;" rel="nofollow">https:&#x2F;&#x2F;xkcd.com&#x2F;927&#x2F;</a>

Going for pip-tools, twine, virtualenv and build makes sense. But I wished he went for black instead. Ruff is not there yet.

Not to dig on this project, but I find it constantly befuddling how awful the Python dev ecosystem is. And has barely improved after a decade of being so popular. The ergonomics of coding with Java or C# in 2010 are still so far beyond anything in Python in 2024, I constantly question why it&#x27;s so popular.