6 ms·
Django 1.5 beta release notes
- elithrar 14y ago> Configurable User model This pleases me greatly. No longer do I need to rely on plug-ins (and therefore, them being updated) to minimally extend the existing User model for small projects.
- rheide 14y agoYou could already extend the user model with a OneToOne relation plus setting in settings.py that was supported in the official Django distribution. But the way that was handled was a bit hacky so I'm glad they changed it too.
- wahnfrieden 14y agoYea and incur an extra DB lookup every time. This is very welcome.
- the_cat_kittles 14y agonot to mention tastypie headaches when trying to update nested resources (user->userprofile->something else)
- zalew 14y agoBut you still were forced to use obligatory auth.User fields like username/email, etc., while there are quite a few use cases when you curse it and the only choices were either making some really weird workarounds or dropping User altogether. Russel's solution is meant to solve this problem.
- quaunaut 14y agoThe two big headline features, the configurable User model and Python 3 support, are both huge. The first, because as is right now, simply extending the User model feels janky and possibly broken, and the second, because Django is probably one of the biggest reasons people have not moved onto Python 3.
- pawroman 14y agoI hope that Django 1.5 (or 1.6) will be a major milestone in the process of Py3 adoption, hopefully other libraries (and people) will follow!
- fatbird 14y agoDjango is the lagging project, actually. Most smaller projects have already bitten the bullet. At my last Django meetup, we did a show of hands of who was waiting for Django to move before personally switching over to Python 3, and it was basically everyone.
- wahnfrieden 14y agoWe'll see, there are surely dependencies that people simply haven't looked into because of Django's prominent lack of support.
- StavrosK 14y agoYep, now people will be waiting for "that Django library that doesn't work with Python 3". Hopefully those are much fewer. I'll start experimenting with 3 when 1.5 us released, I hear it's the default on ubuntu 12.10, but I might be wrong (I should check).
- takluyver 14y agoIt's installed by default in 12.10, alongside Python 2.7. Eventually, only Python 3 will be in a default installation, but it will still use the command 'python3'.
- ehutch79 14y agoalso, PIL, and mysql bindings.
- dangoldin 14y ago
- scommab 14y agoMajor Highlights: - Python3 support! (supports python2.6.5+ and python3.2+ in the same code base) - {% verbatim %} (no collision problems with mustache) - Built-in Partial model saving
- jfb 14y agoCan someone point me to a compare/contrast sort of doc between modern Django and Rails? I don't do a lot of web app programming, but I'm curious as to whether there's much of a difference between the two.
- jarcoal 14y agoRails is written in Ruby, and Django in Python. That's by far the biggest (and maybe only) difference.
- bryanh 14y agoThat certainly is a big distinction, but is not the only difference. An older overview is available here: http://www.vaporbase.com/rails-django http://www.vaporbase.com/rails-django
- jfb 14y agoSure. But, for instance, is Django as tied to the active record pattern as is Rails? And yes, I know you can swap out persistence layers in modern Rails, which is good (because active record is utter bilge), but who does that? &c.
- ncavig 14y agoNo, it's not. But since Rails 3 neither is rails really. Rails is more about the ActiveModel pattern, which has it's own API. Active Record inherits from ActiveModel. You can pick and choose what you want in your persistence classes, or even better, make models/classes that have no persistence layer tie. For instance, if you want to use a class like it was a MySQL table, you could include a few ActiveModel classes which will make things for ActiveSupport helpers work with them. http://api.rubyonrails.org/classes/ActiveModel.html http://api.rubyonrails.org/classes/ActiveModel.html - pick and choose what you want in your classes. This was one of the major changes in Rails 3 EDIT: just to clear it up, by ActiveModel I mean Model. Rails is convention over configuration and adheres to the MVC pattern and philosophy
- jarcoal 14y ago
- hayksaakian 14y ago> python3 support Go on
- ceol 14y agoWe’re labeling this support “experimental” because we don’t yet consider it production-ready, but everything’s in place for you to start porting your apps to Python 3. Our next release, Django 1.6, will support Python 3 without reservations.
- josephlord 14y agoI haven't tested it and I might be being unfair but I have a feeling that Django's experimental non-production-ready release may be comparable to other web framework's normal production releases in terms of stability. Although obviously plug ins and other components would also need to be compatible too.
- hayksaakian 14y agoExcellent, now all I need is a railscasts equivalent and I'm ready to test the waters.
- josephlord 14y agoDon't take my word for it, I'm guessing based on my impression of Django. You know some projects you want to avoid the .0 release and others are pretty safe at the beta release. I just have the feeling that Django is at the safe end. I don't have any data to back it up at this point though.
- Alex3917 14y agoIf I want to create my own database and write my own SQL queries instead of using Django's object models and ORM, does it still make sense to use Django's user model in my project?
- deleted 14y ago[deleted]