If I understand correctly the input, would the following proposal be an acceptable middle ground?
Replace: > It’s often useful to prepend django- to your module name when creating a > package to distribute. This helps others > looking for Django apps identify your app as Django specific With: > It's often useful to use the "Framework :: Django" setup.py classifiers when > creating a package to distribute. > This helps others looking for Django apps identify your app as Django > specific. > > On a related note, using a different name between your PyPI package and the > actual module to import increases the risk > of namespace collisions: if your package is called "django_foo" but imported > as "foo", it might conflict with a > package named "foo". If possible, use the same name for the "module to > import" and the "packaged application". I also think that the current tutorial is slightly confusing for newcomers: it suggests to use different names for the package and the module — a distinction which might not be quite beginner-friendly. -- Raphaël On Thu, 08 Dec 2016 16:29:42 +0000 Michael Manfre <mman...@gmail.com> wrote: > As some one who maintains django packages, I wouldn't use "django_" and > don't think it should be an official recommendation. I do support > documenting the potential collisions to let package maintainers make a more > informed decision. > > On Thu, Dec 8, 2016 at 7:17 AM Adam Johnson <m...@adamj.eu> wrote: > > > +1 (to what Aymeric and Florian said) > > > > On 7 December 2016 at 19:54, Robert Roskam <raiderrob...@gmail.com> wrote: > > > > +1 > > > > On Wednesday, December 7, 2016 at 11:25:05 AM UTC-5, Marc Tamlyn wrote: > > > > What Aymeric and Florian sayid. > > > > On 7 December 2016 at 15:58, Florian Apolloner <f.apo...@gmail.com> wrote: > > > > On Wednesday, December 7, 2016 at 1:10:48 PM UTC+1, Aymeric Augustin wrote: > > > > I still think I wouldn't use a django_ prefix when I create new apps > > because > > it adds a small but pervasive overhead to prevent conflicts that aren't > > common > > in practice. > > > > > > Same here, I am certainly against making that a recommendation from/in > > Django itself. > > > > Cheers, > > Florian > > > > -- > > 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 post to this group, send email to django-d...@googlegroups.com. > > Visit this group at https://groups.google.com/group/django-developers. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/django-developers/ba0114d9-0baa-4662-8fff-f7c9b03b90d3%40googlegroups.com > > <https://groups.google.com/d/msgid/django-developers/ba0114d9-0baa-4662-8fff-f7c9b03b90d3%40googlegroups.com?utm_medium=email&utm_source=footer> > > . > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > -- > > 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 post to this group, send email to django-developers@googlegroups.com. > > Visit this group at https://groups.google.com/group/django-developers. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/django-developers/b6258a98-2f7e-4617-bb44-e7bc14952327%40googlegroups.com > > <https://groups.google.com/d/msgid/django-developers/b6258a98-2f7e-4617-bb44-e7bc14952327%40googlegroups.com?utm_medium=email&utm_source=footer> > > . > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > > > -- > > 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 post to this group, send email to django-developers@googlegroups.com. > > Visit this group at https://groups.google.com/group/django-developers. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/django-developers/CAMyDDM1jBb50Rw74sEP8Ot7ykTDop7pn8Xr6kZw4uqgJmzot3Q%40mail.gmail.com > > <https://groups.google.com/d/msgid/django-developers/CAMyDDM1jBb50Rw74sEP8Ot7ykTDop7pn8Xr6kZw4uqgJmzot3Q%40mail.gmail.com?utm_medium=email&utm_source=footer> > > . > > For more options, visit https://groups.google.com/d/optout. > > > -- 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 post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20161208184005.3e346d6e%40ithor.polyconseil.fr. For more options, visit https://groups.google.com/d/optout.
