21–30 of 45 posts
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.
Are you looking for material that helps you understand the process open source developers use to create and maintain their projects?
I've been using rye for all of my python projects and it has generally been great. There's a slightly annoying piece at the beginning when you first set up a project because "rye init" doesn'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've used.
How does Rye compare to Poetry?
Poetry and Rye mostly do the same things, but Rye additionally does Python version management. I was personally recently reminded* that not only should one use dedicated environments for their projects, but also lock their specific Python versions.
I've used Rye so far for Python/package/env management, and it does the job just fine.
* (I upgraded from Fedora 38 to Fedora 39, which also bumped the system Python version from 3.11 to 3.12. And all of my virtual environments said boom.) :')
This is an impressive effort, no doubt. And Python packaging is in a woeful state. But I'm sorry, the last thing the ecosystem needs it another alternative! https://chriswarrick.com/blog/2023/01/15/how-to-improve-pyth... https://xkcd.com/927/
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 have been considering doing that but I wasn’t sure if there was appetite.
For those lacking time/skill to contribute, how can we support?
Rye is a one stop shop for everything that I need.
I've been using rye for all of my python projects and it has generally been great. There's a slightly annoying piece at the beginning when you first set up a project because "rye init" doesn'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've used.
How does Rye compare to Poetry?
Otoh it’s definitely newer and there are still rough edges from time to time.
Earlier quoted context omitted.
I have been considering doing that but I wasn’t sure if there was appetite.
The sooner python packaging has a sane story, the sooner people will wonder why it took so jolly long. For those lacking time/skill to contribute, how can we support?
Improving documentation, spreading the word, giving feedback. Honestly anything helps.
This is an impressive effort, no doubt. And Python packaging is in a woeful state. But I'm sorry, the last thing the ecosystem needs it another alternative! https://chriswarrick.com/blog/2023/01/15/how-to-improve-pyth... https://xkcd.com/927/
Ask me how I know you didn't read the article.
"I did not feel well throwing yet another Python packaging tool into the ring.
Yet it exists now and has user. (sic)"
TL;DR: I knew it was a bad idea, but I did it anyway.
But I wouldn't have had to, anyway. Because I know how names work: "Rye" is not in the set of current named tools. Doesn't matter that it wraps them. It becomes one by doing so, and now we have 15.
Earlier quoted context omitted.
Ask me how I know you didn't read the article.
LOL I surely did, it even explicitly says: "I did not feel well throwing yet another Python packaging tool into the ring. Yet it exists now and has user. (sic)" TL;DR: I knew it was a bad idea, but I did it anyway. But I wouldn't have had to, anyway. Because I know how names work: "Rye" is not in the set of current named tools. Doesn't matter that it wraps them. It becomes one by doing so, and now we have 15.
If you click into their link "Should Rye Exist" [1] you'll see that XKCD 927 is literally the first sentence and full width image.
