9 ms·
Django 1.6 beta 1 released
- fotcorn 13y agoIntegrated connection pooling makes this release a no-brainer upgrade on release day.
- acjohnson55 13y agoAgreed! The changes to transaction management seem pretty solid too. I've found transactions to be pretty somewhat unpredictable at times in the past, so I'm encouraged by these changes.
- gtaylor 13y agoWe're really looking forward to this. We'll still use pgbouncer, but we think we may see a slight boost.
- ubernostrum 13y agoIt's not connection pooling.
- rattray 13y agoCare to explain what it is?
- ubernostrum 13y agoCurrently, Django closes the database connection at the end of each request/response cycle. In 1.6, Django will optionally not do this; instead, a setting can specify the maximum amount of time to hold open and keep reusing an existing connection. This is not connection pooling; that would imply some functionality to actively maintain and allocate connections. This is simply "your process will hold its connection open from one request/response cycle to the next".
- mixmastamyk 13y agoIt is "Persistent database connections" just like it says it is.
- dmishe 13y agoLooks like a no-go for unicorn deploy https://groups.google.com/forum/#!msg/django-developers/rH0QQP7tI6w/I_R0JV8suSkJ https://groups.google.com/forum/#!msg/django-developers/rH0Q...
- bhauer 13y agoThank goodness. Not being a user of the framework, the lack of database connectivity persistence in Django was among the most surprising elements of setting up the initial test cases in our framework benchmarks project. We've since then added a Postgres test with a connection pool, but I still have the memory of that surprise from the first round. (Incidentally, I hope to get this new version into Round 7 of our project.)
- acjohnson55 13y agoI really enjoy working with Django, but in many ways, it seems to be staying pretty vanilla while other technologies head in more experimental directions. Does Django have a bright future in a world that's moving heavily client side, or will it be relegated to a relatively bland corner of the web world?
- gtaylor 13y agoWe've got a more complex application (Pathwright) running Django, and we're currently going much more heavy client side. Nothing about Django keeps you from doing this, and there are some excellent third party apps that actually make it very easy (django-rest-framework is awesome). > Django have a bright future in a world that's moving heavily client side, or will it be relegated to a relatively bland corner of the web world? This is one of those questions seeking controversy where there is none. Django seems to get out of the way even more when you shift to a heavier client.
- zalew 13y agohe's probably referring to the ever-recurring topic of django not integrating front-end libs out of the box (which I in particular support).
- jonknee 13y agoI support that too, but I think Django should provide some default API endpoint support (like Django Rest Framework).
- gtaylor 13y agoI'd be pretty miffed if they did this. You need only look at the comments contrib to see an example of something that was OK'ish when it was incorporated, but has languished since then. Now I question the need to even have it in contrib. We don't have to bake components in for them to be excellent. rest-framework in particular moves ridiculously fast, and being separate from Django lets them do that. Also, if in the future something even better comes out, I can easily switch to it.
- caioariede 13y agoPillow is now the preferred image manipulation library to use with Django. Nice!
- fvox13 13y agoIs there an easy way to tell which bugs have been fixed as a part of this release?
- famousactress 13y agoI'm thrilled about this particular release, because it includes a significant overhaul of the way joins are built (or rather, trimmed) in the ORM and almost certainly makes your project faster if you do even relatively complex queries: The original bug: https://code.djangoproject.com/ticket/10790 https://code.djangoproject.com/ticket/10790 Got even worse in 1.4 https://code.djangoproject.com/ticket/18785 https://code.djangoproject.com/ticket/18785 Thanks Anssi!
- pvnick 13y agoI'm currently working with Django for a client's project I'm developing. Coming off a LAMP stack binge, the technology itself has been an absolute delight. I've been given the directive to use South to manage the data model, but for future projects I was hoping somebody with more experience can give some insights as to what you've found works and what doesn't work. I'm not the biggest fan of South, but maybe it's just a lack of experience/patience.
- adamauckland 13y agoI would always use South, but you need to read the migrations and _understand_ what it's doing. When it gets a conflict (and it will), you need to be able to fix up the migrations.
- danielsamuels 13y agoUnfortunately that's the best we have right now. However, the guy who wrote South (and is a core Django developer) ran a Kickstarter last month to raise funds to write South-like functionality directly into the Django core.
- maspwr 13y agoHe (Andrew Godwin) also recently gave a talk on the subject, (http://lanyrd.com/2013/djangocon-europe/schgcz/ http://lanyrd.com/2013/djangocon-europe/schgcz/).
- adamauckland 13y ago> Does Django have a bright future in a world that's moving heavily client side Where are you getting the data for the client from? Django-Rest-Framework is a very convenient way to get data down into the browser layer from a DB.
- euroclydon 13y agoI think this is an area where ASP.NET MVC excels because, while REST is nice, you also have to consider web sockets, and I have not seen good web socket support in Django, where ASP.NET has SignalR which is loads easier to configure than a custom solution with Django and Nginx/Apache. Not to mention that SignalR has very nice degradation support on both ends when web sockets are not available.
- rattray 13y agoThere is a socket.io server for Python that claims to work with Django: https://github.com/abourget/gevent-socketio https://github.com/abourget/gevent-socketio I haven't used it personally, and would be very interested to hear others' thoughts. EDIT: Looking through the example code ( https://github.com/abourget/gevent-socketio/tree/master/examples/django_chat https://github.com/abourget/gevent-socketio/tree/master/exam... ), it doesn't seem as straightforward as one might hope, especially compared to the channels API. FWIW, I'm using the AppEngine Channels API from my Django app, and have yet to be disappointed with it.
- bad_user 13y agoWell, if you're talking about alternatives that do asynchronism, Comet and Web Sockets well, the most convenient framework I ever used is Play 2.1 The framework is said to be reactive, meaning that you can build components that react to events asynchronously. The architecture is completely awesome, as Akka actors are baked in and the protocols are modelled with Futures and Iteratees, an FP concept for sane I/O. Things like serving unending streams of data and responding to client events using async I/O are in the very foundations of the framework, instead of being taked on later. People using Node.js or Tornado or whatever, don't know what they are missing. See their docs on the subject: - for Scala: http://www.playframework.com/documentation/2.1.1/ScalaAsync http://www.playframework.com/documentation/2.1.1/ScalaAsync - for Java: http://www.playframework.com/documentation/2.1.1/JavaAsync http://www.playframework.com/documentation/2.1.1/JavaAsync
- wiremine 13y agoThis can't be right: 1.5 was just released in February. It takes at least 1 year between Django releases, right? Right!? (He said, sarcastically.) Seriously, it is GREAT to see the framework continue to roll forward.
- mixmastamyk 13y agoThere's probably a lot of stuff that didn't make the 1.5 cut.
- zalew 13y ago1.5 was the first release after moving to git - they freeze the release branch and let the rest of development continue on master, so now releases will tend to be quicker (we all hope) hence the surprise with 'early' 1.6. now, since we have an alpha, 1.6 is bugfixed on branch, and 1.7 features can be developped on master like now during the 1.6 release schedule.
- aerolite 13y agoChrist, Django is changing too fast. I recently upgraded from 1.2 to 1.3 and it's still way obsolete.
- powersurge360 13y agoDjango 1.3 was released back in March of 2011. That's more than two years ago! Were you waiting on some sort of third party package or something?
- tomovo 13y agoI recently updated an older project from 1.2 to 1.5 and it was quite a bit of work.
- zalew 13y ago1.3 -> 1.4 was trivial AFAIR. 1.4 -> 1.5 may need some more work if you depended a lot on function-based generic views.
- mixmastamyk 13y agoPersistent database connections :). Glad to see the objections finally fall by the wayside. Still no update for the homely admin app? Would love to have it use bootstrap (or similar) to offload look and feel to those focused on it. One extra thing to do in every Django app is to change the ugly yellow on cyan title bar. I know it is already possible with apps, but then it means one more thing to fix on upgrade.
- Nagyman 13y agoFWIW, admin2 is under active development and moving forward. I don't know if the intention is to replace the existing admin, but as it's not backwards compatible there will be some effort to upgrade if you've completed any serious customization. https://github.com/twoscoops/django-admin2 https://github.com/twoscoops/django-admin2
- Spiritus 13y agoGiven its dependencies I find it highly unlikely it will find its way into the Django core anytime soon.
- gtaylor 13y agoI wish the admin started as an external project and stayed that way (for the sake of getting some love and attention). But of course, then we wouldn't be able to show shiny tutorial videos and people wouldn't get it automagically. Watching this with interest.
- StavrosK 13y agoI saw this earlier and am absolutely ecstatic over the new template functionality. I can't tell you how many times I've cloned old projects to start new ones, a process which isn't very fun (due to the amount of stuff one needs to change). I started this right away: http://www.stavros.io/posts/django-template-projects/ http://www.stavros.io/posts/django-template-projects/ I'll post various templates there, for example a default one containing all the "best practices" that I use (and structured that way), one that includes Persona by default (so you can just click the "Log in with Persona button" and log in), etc. I love this feature.
- ninetenel 13y agoI'm so excited about this .. my team just started using django on our current project after our flask experiments fall on their face
- SPSteinbeck 13y agoFor fuck's sakes, go away you insipid faggot. Edit: please don't downvote me, he's a worthless troll and needs to be put in his place; look at his past comments.