hatch?

[Schamschula]

For a downstream port maintainer, in my case for MacPorts, this means adding another build system, incompatible with all the others currently in use.

[facelessuser]

Yes?

[facelessuser]

Let me mention, that it is becoming discouraged to use setup.py. I do some dynamic things in my setup, so I opted to use a build system that I find flexible. It is compatible with the recent related PEPs.

[Schamschula]

That is well known. However, if you look at the MacPorts python build system (PortGroup) you'll see why I don't want to hack in another backend.

See: https://github.com/macports/macports-ports/blob/master/_resources/port1.0/group/python-1.0.tcl

[facelessuser]

I understand, with that said, people are naturally going to gravitate toward a system that works well for their project. If it isn't SoupSieve now, it will be some other project in the future. Is the plan to campaign against a new useful build backend? I don't think that serves anyone but macports.

[facelessuser]

Just to clarify, the new tox rewrite looks to be using Hatch as well: https://github.com/tox-dev/tox/blob/rewrite/pyproject.toml#L2.