Re: __unicode__() addition not working in basic poll application.

On Wed, Nov 14, 2012 at 5:13 PM, Daniel Roseman <daniel@roseman.org.uk> wrote:

On Tuesday, 13 November 2012 20:10:38 UTC, Colin Keenan wrote:

By the way, I just checked django.VERSION and it's (1, 6, 0, 'alpha', 0)

So, since version 1.6 is supposed to fully support python 3, I should be fine. Obviously, being 'alpha' means I'll run into trouble, but I'll keep checking out new versions as I learn so by the time 1.6 is really out, I'll be all set.

Django 1.5 isn't even released yet. I've no idea how you've got onto "1.6 alpha", but I doubt it will be released any time soon - it's probably at least 9 months away. You should stick to the released versions rather than running from trunk, and that means Python 2 for now.

Filling in the blanks here -- If you download Django's trunk branch, it currently reports as 1.6 alpha. When we cut the 1.5 alpha, we created a separate branch for 1.5 development, so that trunk can remain in a live "commit anything" state, rather than our historical "trunk feature freeze" state. 

So, in theory, trunk can currently contain features that won't be included in 1.5; however, in practice, the core team is focussing primarily on the 1.5 release branch, in preparation for the 1.5 beta and final releases.

Yours,

Russ Magee %-)

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.