I'm sorry you've seized the opportunity to use my effort to put a little joy and humor in my message to push me on the slope, sorry that it's been misinterpreted and that I just don't understand at all your technical explanation. I guess there is always that risk. Best James
Le 7 avr. 2017 10:43 PM, "James Bennett" <ubernost...@gmail.com> a écrit : > On Thu, Apr 6, 2017 at 5:22 PM, James Pic <j...@yourlabs.org> wrote: > >> Do I need this to deploy my projects ? No of course, because I use the >> prettiest way hhihihi ;) I'm more than happy to win a debate >> > > Please don't do this. This does not make you look like someone who I could > constructively engage with to try to figure out what problem is being > reported and what a good solution would be. > > >> And this is >> how the drama begins, I can imagine them in front of Tobias. >> > > Please also don't do this. You are perfectly well aware that people will > give one type of explanation to a new user they're helping, and quite > another to a mailing list of experienced developers discussing the merits > of different approaches. And regardless of the context-insensitivity of > what you're doing here, putting words in someone's mouth to try to make > them look bad just makes you look bad. > > Meanwhile, Django has a way to avoid all the turmoil you've proposed in > your reply -- run 'startproject', get package with settings file inside, > run 'manage.py <command>'. Several tools for deploying Django into > production even make use of this, providing custom management commands > which can be invoked to run/deploy/etc., and doing so requires no deep > dives into Python imports, Python packages, or environment variables. Of > course, a third-party package which develops its own independent > configuration mechanism will need to teach all of its users how to make use > of and deploy that configuration mechanism, but that's the responsibility a > third-party project takes on when it invents its own method. > > -- > 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/CAL13Cg_JBcc6mYhH7un3LKgGFR22pZz%3D_ > kQyc0sB5dh4uq8g-g%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAL13Cg_JBcc6mYhH7un3LKgGFR22pZz%3D_kQyc0sB5dh4uq8g-g%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/CAC6Op18F%2B3TM-P2NHb-qv4tXC0X9s1YJ045q5iK50HA45VULZA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
