FWIW, I have several small, public-facing Django projects, all of which are 
on Django 1.5.1/Python 3.3. I've had no trouble with them at all. 

I've wanted to switch to Python 3 for a while, but it's only been in the 
past year (thanks in large part to Django's move) that it's become 
practical. 

All my work now is in 3.3; I'm not trying to stay compatible with 2.7+. If 
a package doesn't work with 3.3, then I'm not using it (or maybe, I would 
assist with porting it.) But I realize that's not practical for everybody.

All this is to say you should have no worries about using Django with 3.3

--Mark

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


Reply via email to