Make devserver run on Python 3

[bkabrda]

Hi, since Django can run on Python 3 now, I thought it would be nice if devserver could, too. I didn't use six library for compatibility, because I think the modifications are easy enough to keep them as they are...

[scottwoodall]

+1 as I was also needing/wanting this today.

[lithammer]

Should probably just use self.stdout.write() and self.stderr.write() instead of print() as suggest in the docs.

[keimlink]

What the status of this issue? Does django-devserver support Python 3 now?

[gone]

+1 for this one - I've been using coagulant's fork

[ALenfant]

+1, this project seems very interesting and I'd love to use it, but unfortunately I am on Python 3 !

[mikaelengstrom]

+1

[FlipperPA]

Our organization is running on Python 3 exclusively now as well. Shall we start a branch and collaborate if there's enough interest?

[mikaelengstrom]

@FlipperPA I´m interested and could help out.

[rattrayalex]

Is there a fork anyone is using?

[egrubbs]

I know someone that is using this branch for python 3. https://github.com/alexryabtsev/django-devserver/commits/master

[Ismael-VC]

@egrubbs why is Python 3 support not wanted?

[ebertti]

@dcramer Are you there?

[acdha]

@ebertti Unless you're his boss I don't think you should ask questions in that tone. If you want to help develop a project, perhaps test the outstanding pull request(s) and report your results.

[FlipperPA]

I'm guessing the maintainer probably doesn't have much time to give to this project, as he's the founder and CEO of Sentry, which has exploded over the past few years (congrats to you, @dcramer!). If you look at his commit history, it is pretty clear that's where his attention is, and should be. I wonder if he'd be amenable to someone taking this project over as maintainer, especially since Django 2.0 (coming in ~December) will only support Python 3 going forward.

Also worth considering, most of the features of this package can be accomplished in Django or are covered nicely in Django Debug Toolbar, for example:

• Setting up logging to file is possible.
• As of Django 1.8 (IIRC the version correctly), runserver is multithreaded by default (as I found out when running a single-threaded DB driver, hehe). The --no-threading option was introduced.
• Django Debug Toolbar has awesome SQL parsing, explain syntax, and more

• Using IPython's embed() is amazing for interactive debugging with Django's runserver

  Has this project become redundant? If not, can any of the features be pushed upstream to Django's runserver or Django Debug Toolbar?

[acdha]

@FlipperPA The main reason I still use devserver is for speed & AJAX: I often want is the query count/time info for API requests. I've been wondering whether it might be better to basically do a modern Django fork which would add only that information and forgo everything else since it's also much easier: hook the database, cache, etc. calls on startup and then turn control over to the stock WSGI app.