4 ms·
The money for migrations was to employ the guy who wrote south to work on those migrations fulltime. It wasn't as much of a "community" thing as one guy who did
by SEJeff 13y ago
The money for migrations was to employ the guy who wrote south to work on those migrations fulltime. It wasn't as much of a "community" thing as one guy who did it all. That wasn't the django "community" but a single django contributor. I think you've got things a bit mixed up here. Overall, the core of django sholud be small. The real good stuff is in the reusable apps.
Besides, runserver isn't supposed to be for production. If you want things to run faster run it under a real wsgi server such as circus/chaussette, uwsgi, or gunicorn. That being said, I highly suggest looking into runserver_plus from: https://github.com/django-extensions/django-extensions https://github.com/django-extensions/django-extensions, it is really nice stuff.
- antelopesalad 13y agoThis has nothing to do with production mode. The development experience is unacceptable with runserver in development mode. I have a trivial app with half a dozen apps and it takes 5 seconds to reload runserver when I touch a view file. On the same hardware a ~6k SLOCs rails project with 40 gems reloads pretty much instantly because the rails dev server is smart enough to do code swapping. Edit: runserver_plus does nothing to make runserver reload faster, it is an improved stack trace with a built in debugger. Since I am already using django-extensions I tried runserver_plus and it added 2 full seconds to each reload. So now it takes 7 seconds just for runserver_plus to reload after touching a view.
- rbanffy 13y agoIf you consider the development experience to be unacceptable, then use something else.
- hexsprite 13y agoWhy don't you try using Python's profiling tools and file a bug report with what you find? That might get you a better response than asking on IRC.
- antelopesalad 13y agoI don't have the time to audit and analyze the entire django framework and every third party app I touch. I am only using a few apps too that are popular in the community. Realistically I'm a web app developer who wants to be productive. It's insane that I need to even consider doing that just to not have to wait 5 seconds for runserver to reload in development mode on a trivial app. It should be on the shoulders of the django core team to make sure their platform makes developers happy. P.S., if you want to give me $100,000 I will quit my job and spend the next half a decade learning advanced python, audit the entire django code. You would probably laugh and call me insane right, but this seems like what the django core devs are forcing us to do because they don't want to address the problems with the framework.
- joshlegs 13y agoidk what you're working on, but i'm currently working on a ~100mb app. It's pretty big, and i've never had anything like what you're talking about. are you sure it's not hardware related?