I think we need to be very cautious. Anecdotally, I've seen folks hitting issues trying to adopt the new methods, and I don't see any upside to Django being an earlier adopter here.
We were slow adopting PEP 517 and still had regressions reported: https://github.com/django/django/pull/12013 https://github.com/django/django/pull/13994 I'd much rather let the bulk of smaller projects adopt, and iron out the details, and then update when it's a better beaten track. On the particulars, I'm sure Hatchling is great, but it's not at all clear (from here — to me) that it's mature enough to trust Django with. It seems the packaging options are emerging very quickly (which is great) but I'd like the current (evolutionarily) explosive period to settle some, so we can see the long-term survivors going forward before we jump. With setup.py, I think for a project like Django, there's a certain value in being second-to-last off the boat. Kind regards, Carlton On Sun, 24 Jul 2022 at 22:39, James Bennett <[email protected]> wrote: > On Sun, Jul 24, 2022 at 1:34 PM Ofek Lev <[email protected]> wrote: > >> > My initial reaction is "no", and that this request kind of rubs me the >> wrong way. In the pull request you say [...] But the blog post you quote is >> just saying to run "python -m build" instead of "python setup.py" >> >> This issue is that the `python -m build`/PEP 517 way does not support the >> deprecated RPM logic. I tried to articulate that as best as I could; I'm >> sorry if it wasn't clear! > > > We can run `python -m build` pretty much as-is using setuptools as the > build backend, though, and that suffices for Django's packaging needs. > > I'm not familiar with what happened with black but I think you might be >> referencing how the recommended style was in flux for a time. >> > > I am referring to the multiple occasions on which black's approach to > packaging caused installation of the package, via pip, to fail in often > mysterious ways. > > This is something that's documented in the history of their issue tracker, > and that the maintainers have since apologized for and adopted policies to > try to prevent in the future. > >> -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAL13Cg_F1JxY5ANKw53LvEYc8_JjJGb_%2BSs-dZ2YxWr_tRw1Vw%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAL13Cg_F1JxY5ANKw53LvEYc8_JjJGb_%2BSs-dZ2YxWr_tRw1Vw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJwKpyTvKDGEnO2RQM3yhB9UJ_YLhaZJYmwdLmjBhd5MFPDW-w%40mail.gmail.com.
