Sorry, I broke this by splitting slixmpp in #48545

e08ab90 should be squashed

@lheckemann no worries I will rebase it. I appreciate you letting me know. @FRidh my git fu is not quite good enough and I was being lazy when I made those commits. I will learn how to properly split that commit and merge into the appropriate commit.

Good job.

25 more packages -> python-modules. All tested.

@costrouc Thank you for this work! @FRidh is encouraging me to start updating Python packages semi-automatically with r-ryantm/nixpkgs-update and it cannot update the packages in python-modules.nix (because it won't update things in a file with multiple fetchers), so this work you are doing should help keep Python packages more up to date!

You are welcome! I was aware of your bot and someone told me that it could only work with fetchPypi and being in python-modules. To me it seems like automation is an important step in the growth of nix. Otherwise small package updates will consume too much of our time. I have a bit more free time for the next month and my goal is to really cleanup the python packages in nix.

The good news is that soon (next few years) python projects will start declaring their dependencies in a static file pyproject.toml. This will make life much easier for updating packages.

pyproject.toml will probably still need some time to establish. At the moment I don't see how c-extension can be build using this.

As far as I know, nixpkgs-update doesn't need the derivation to use fetchPypi. In fact, here is one using fetchFromGitHub: https://github.com/NixOS/nixpkgs/pull/49037/files

@ryantm what fetch... does it work with? In some cases packages released through pypi do not contain tests which make upgrades more dangerous (not knowing if something breaks). Makes me want to favor fetchFromGitHub, fetchFromGitLab, etc. What are your thoughts?

@costrouc As long as the fetcher is written in some way that it gets modified by changing the version string somewhere in the file, and the hash for it is somewhere in the file, and nix-prefetch-url works, it should work. So, all the main fetchers work, but sometimes expressions are formatted in a way that doesn't works, for example, the rev might not be based on the version, or fetchgit is using the commit sha.

As for what to do for python things, I want to defer to @FRidh. I'm not familiar with the Python ecosystem.

pyproject.toml will probably still need some time to establish. At the moment I don't see how c-extension can be build using this.

pyproject.toml will specify that setuptools will be used as build system, and from there on everything is the same as it is now. It's a step in the right direction, giving access to dependencies in a easier way. However, we still have to do the hardest part: dependency resolution across the whole package set.