Le mercredi 07 décembre 2016, Aymeric Augustin a écrit : > In my experience: > > - many Django-related packages use a django- prefix in the name of the package > on PyPI
And the mismatch between package name and module name means that we have many packages which are not co-installable because they use the same python module name. At least using a matching package/module name means that those conflicts are detected when you try to submit your package. Here's a concrete example found in a few seconds: https://pypi.python.org/pypi/cep/0.1.1 https://pypi.python.org/pypi/django-cep/1.1.2 > - very few use a django_ prefix in the name of the Python module, because this > module can only be used in the context of Django and the longer name makes > imports less readable It's hard to know the reason. Maybe they do because they follow the documentation to the letter? I agree with your assessment of the current situation. A majority of packages do not follow this recommendation, but a non-trivial part of the packages do follow it correctly. I have seen many examples in Debian and it's easy to find many more on PyPi. > Considering the backwards-compatibility issues — if you change a package name > all imports needs updating — I don’t think it’s realistic to go against the > established practice of the ecosystem at this point, and for this reason I'm > not in favor of making that recommandation. I'm not asking to rename existing modules, I'm just asking to update the recommendation in the documentation so that new Django applications do follow the best practice that avoid namespace conflicts and namespace pollution. While the mismatch affects the majority of Django packages, and it's an established practice for some Django developers, I don't see how making this recommendation goes against anything. It's not like we will break anything by making this recommendation. > To sum up, I’m afraid that your suggestion priorizes the needs of packagers > over those of developers and, unfortunately for you, developers are the > heavier users there. I don't think that developers have much to loose here and as you know, developers and packagers work hand in hand pretty well. Cheers, -- Raphaël Hertzog ◈ Writer/Consultant ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- 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/20161207115211.vzjefmdxpn4db2k4%40home.ouaza.com. For more options, visit https://groups.google.com/d/optout.
