meejah <mee...@meejah.ca> writes: > I believe this was "just" fallout from following Python upstream changes -- > that is, switching to "hatch" / hatchling (one of the choices of the wider > Python switch to PEP0517) instead of 500+ lines of custom Python, setup.py > etc. > > I have filed https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4173 to track this. > > That made it into the release notes as "switched to hatch" but maybe didn't > capture nuance like this :( > https://github.com/tahoe-lafs/tahoe-lafs/blob/master/NEWS.rst#dependencyinstallation-changes
Thanks. Well, changing the distfile name because of a tool change is still a bug :-) It is conventional for packaging systems to name things based on distfile names, or rather for pkgname == distfile-name == repo-name == human-used-name. But maybe python culture is just becoming problematic. _______________________________________________ tahoe-dev mailing list tahoe-dev@lists.tahoe-lafs.org https://lists.tahoe-lafs.org/mailman/listinfo/tahoe-dev