RFC: Changes for version 2.0

[sirosen]

We're working on moving most of the implementation into packaging.dependency_groups, and pip install --group is now available.

I think I'd like to wait until packaging.dependency_groups has been out for a while, and then make the following changes:

• depend on packaging instead of the implementation here
  • slim down the tests
• update the main entry point (which prints groups) and the lint entry point to use the new implementation
• remove the pip wrapper -- people can use newer pip versions
• release the resulting, smaller, package as 2.0

---

I think that's all; it looks pretty straightforward to me.
I'm curious if anyone has feedback about this plan.

[sirosen]

Oh, and an idea:

Maybe the CLIs should merge, and it becomes

$ dependency-groups lint
$ dependency-groups print

Will think on that more.

[henryiii]

Keep in mind, requiring minimum versions of things systems tend to provide when building is painful with pip when inside a package build, since pip can leak system packages into the so-called "isolated" environment (which is not a real virtual environment in pip, which causes various problems). I don't think this is a big problem here, as I assume build backends don't normally need dependency groups, but worth noting that requiring a minimum version of packaging is not always safe. I think it's safe here.