Hi, On Tuesday, May 12, 2015 at 4:43:41 AM UTC+2, Steven Berry wrote: > > On Monday, May 11, 2015 at 6:30:39 PM UTC-4, Florian Apolloner wrote: > >> >> On Monday, May 11, 2015 at 10:13:03 PM UTC+2, Steven Berry wrote: >>> >>> With all that said I'm in favor of what you suggest -- rely on gunicorn >>> where possible. However I don't think what I'm suggesting (and have already >>> implemented) fundamentally interferes with #21978. As far as I can tell the >>> django.core.servers.basehttp module exists solely for the runserver >>> command. >>> And the contents therein aren't so much of a homegrown webserver as they >>> are convenient subclasses to Python's inherent wsgiref.simple_server. >>> The onus of maintenance lies largely in the Python codebase. >>> >> >> It might not interfere, but there are already perfectly fine >> alternatives like stunnel which provide you with TLS support. So unless >> there is a really compelling argument to TLS support to runserver itself >> (which I yet fail to see in this thread), I am -0 to -1. Keeping the code >> as simple as possible also makes migrations to a 3rd party server easier >> later on. >> > > > Florian, by that logic what's the point of having runserver in the first > place? There are already perfectly fine alternatives that serve web > content. What I was suggesting was moving something that is half-baked to > something that's at least 60% baked while still taking advantage of what > runserver does well. The trick, which I touched on in my second post, and > which I think Tim addressed, is identifying what your intended scope is > here. If the goal is to deprecate runserver entirely then I agree with > you. But that intention hasn't been made clear, and what we're left with is > a crippled webserver with a bit of an identity crisis. >
At the time Django started there where not many perfectly fine alternatives (if at all) to easily run a python webapp during development. And just because something is already there, does not mean it should be used as an argument for adding more stuff to it. And I am not really sure about the identity crisis, it does what it is supposed to easy and well during dev. 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-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/91426269-26fe-4490-8236-9852c5254247%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
