You know you’re wrong at database administrating, when…
My presentation about GraphQL from MoscowPython Meetup #47 @ Mail.Ru HQ.
Python3 is a great pain in python community. It was released on Dec 3, 2008 and brings major breaking changes and also new interpreter was slower, than python2 realization. After long way and five releases, in 2016, it’s obvious to start on python 3.5: type hinting, asyncio, same perfomance and gets better in coming python 3.6.
In python world, many solutions for trivial problems could be found in standart library: from statistical functions to localization for your package. But somehow some things just don’t connect to each other, and you just stuck at combining this constructor in right way.
There is some standart stack to run django in production. For python 2, it is nginx + gunicorn or uwsgi + monkey patching libs, such as gevent or eventlet. Generally, I prefer gunicorn + eventlet, but when you switch (or start) django project on latest python 3.5, eventlet can do some bad magic. And you can switch to a new built-in mechanism, called aiohttp. Based on gunicorn docs, you need simply switch worker to gaiohttp and that’s all.