I admit I can't find a lot of use cases for this out there. It is just something I think django could benefit from. Please feel free to close this issue.
On Sunday, December 20, 2020 at 12:26:45 AM UTC+5:30 Adam Johnson wrote: > The use case I mentioned applies to lot of packages (and new projects >> could benefit from this change too). >> > > Please bring more evidence than just blind assertion. > > Also I think it's a net negative, as it complicates the notion of what a > management command is. It's against the Zen of Python ( > https://www.python.org/dev/peps/pep-0020/) to provide more than one way > of doing things, when only one would suffice. > > On Sat, 19 Dec 2020 at 17:58, Diptesh Choudhuri <diptesh....@gmail.com> > wrote: > >> There are no remaining use cases here. The use case I mentioned applies >> to lot of packages (and new projects could benefit from this change too). >> >> On Saturday, December 19, 2020 at 11:05:55 PM UTC+5:30 Ahmad A. Hussein >> wrote: >> >>> What are the remaining use cases here? Is the proposed change absolutely >>> necessary for these use cases? >>> >>> >>> >>> On Sat, Dec 19, 2020 at 6:19 PM Diptesh Choudhuri <diptesh....@gmail.com> >>> wrote: >>> >>>> Though its just one file and two directories, the use case is common >>>> enough to be used by a lot of packages and I think django should do >>>> something to support it officially. >>>> >>>> On Saturday, December 19, 2020 at 8:19:28 PM UTC+5:30 >>>> f.apo...@gmail.com wrote: >>>> >>>>> On Saturday, December 19, 2020 at 3:16:51 PM UTC+1 >>>>> diptesh....@gmail.com wrote: >>>>> >>>>>> and having to add a bunch of unnecessary files to the source code >>>>> >>>>> >>>>> A bunch? You can literally get away with one file: >>>>> >>>>> ➜ testing git:(dc_message_signing) ✗ tree testabc >>>>> testabc >>>>> └── management >>>>> └── commands >>>>> └── my_cmd.py >>>>> >>>>> This is a complete (!) django app. While I agree that in theory it >>>>> would be nice to support some other mechanisms, I do not think it is >>>>> worth >>>>> the effort given how easy it is to add a command (one file & two >>>>> directories) >>>>> >>>> -- >>>> >>> 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-develop...@googlegroups.com. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/django-developers/d1f62c54-8f9c-46a1-ba57-e5506bca3436n%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/django-developers/d1f62c54-8f9c-46a1-ba57-e5506bca3436n%40googlegroups.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 django-develop...@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/df7a5f44-2f6b-4a42-bcca-767f32b56c43n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-developers/df7a5f44-2f6b-4a42-bcca-767f32b56c43n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > Adam > -- 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/793ce8f4-71e9-408d-b6c9-f83a08fa7c60n%40googlegroups.com.
