Okay then! Just 2 questions before I go: > 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.
Can we please quantify such heuristics? I want something concrete to write in my OSS to-do list :) > 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. I can't find any such events; do you happen to have links? I'd like to improve Python's packaging experience, in this case by learning from the past. On Monday, July 25, 2022 at 9:39:26 AM UTC-4 Mariusz Felisiak wrote: > I agree with James and Carlton, -1 from me. > > Best, > Mariusz > -- 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/2fd8a563-ba87-4064-ab19-2fab6458d8aen%40googlegroups.com.
