Just a small spinoff idea from Adam's suggestion on django-stubs. There is another package, django-types that started as a fork of django-stubs and was originally intended to be merged back into it. It removes the need to use any mypy plugins, making it possible to use type checkers other than mypy, such as Pyrite, Pyre, etc. However, django-types isn't nearly as actively maintained and having competing type stubs libraries is quite annoying as they each get fixes for different issues, leaving neither in especially good shape, IMO. Although the work has previously been done I think there is enough work there detangling it and getting a PR to a mergeable state for a short project.
Tom On Sat, 26 Nov 2022 at 17:02, Shai Berger <s...@platonix.com> wrote: > Hi, > > Adding to the above, I have two migration-related ideas. > > The first is quite down-to-earth: Support for moving models between > apps. This is a long-standing problem, esp. in enterprise-y or just > long-running projects. I have expressed my dissatisfaction with the > current state of things a couple of years ago[1], and maybe it's time > to change that. > > The second is a bit of a pie-in-the-sky: Allow auto-detection of custom > migration operations. The auto-detector has its change-detection mostly > hard-coded into it[2], and it doesn't seem easy or even possible to > allow third-party code to intervene. But I dream... > > Note: These two are quite independent. Auto-detection of the fact that > a model has moved between apps is not required, supporting such moves > with flags to makemigrations or even a dedicated management-command > would be completely satisfactory as far as I'm concerned. > > Thanks, > Shai. > > > [1] https://forum.djangoproject.com/t/why-do-we-need-apps/827/20 > [2] > https://github.com/django/django/blob/main/django/db/migrations/autodetector.py#L104 > > -- > 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 django-developers+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/20221126180231.372b01a2.shai%40platonix.com > . > -- 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 django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAHoz%3DMbM1M26%2BtrKwX7CoAK_VmORNQGLMLCn_WC5vhAP4PuU4g%40mail.gmail.com.