Starting with Python 3 and Django 1.x?

[Ari Davidow]

I am new to Django, and relatively new to (well, re-learning) python.

I am working on a website that requires a lot of bidirectional type. Sanity suggests that starting this off with Python 3 and all the built in Unicode sanity makes sense. 

The online tutorials assume Python 2. Are there equivalent tutorials for Python 3, and/or some explanation of where to pay attention to things that will be different in the context of what I'll encounter learning Django?

Normally, I would use the existing production version of something--Django 1.6 in this case. Is there any reason to include the release candidate of 1.7 as part of my juggling learning and creating this site?

Thanks,

ari

[Ari Davidow]

Belay the part of the post that asks about Python 2 vs Python 3 tutorial. Had not yet found https://docs.djangoproject.com/en/1.7/intro/tutorial01/ which is the same tutorial, but written for Python 2.

Still curious about learning 1.6 and transferring to 1.7, or jumping into the water now and saving some migration in six months or a year.

ari

[Collin Anderson]

I'd start with 1.7 as it should be more friendly to newcomers. There will be another release candidate soon and the final version should be out in about a month.

[ngangsia akumbo]

stick to python 2.7

collins anderson can i meet u on skype? mine is

skype:  ngangsi.richard

[Ari Davidow]

If I stick to Python 2.7, I start off with a host of Unicode issues--not a promising way to start a site that relies on Unicode, Middle Eastern character sets, and bidi functionality. I hate the last-century, Python 2 ways of dealing with those. That makes no sense, barring something more compelling than the statement, "stick to python 2.7".

ari

--
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...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/d2864620-4d13-4d41-9d6d-cad5b31dc589%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[François Schiettecatte]

I would go with Python 3, string handling is much better and the library layout is a little more rational. I am stuck with 2.7 for the websites I develop but I have been using 3 for the attending scripts with no issues. If you do decide to go with 2.7 I would add the following to each file to make sure that a future migration to 3 is as painless as possible.

from __future__ import print_function
from __future__ import unicode_literals
from __future__ import absolute_import
from __future__ import division


François

> To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAF%2BxBDVVTBSo39oVJ9eAPC9h_VwOdwo9JsSq1Y%2BTK2Jenu7Ecw%40mail.gmail.com.

[Andreas Kuhne]

You will get issues with some of the third-party plugins. For example getting mysql to work, requires that you use the oracle plugin and not the commonly used mysqldb plugin. Also south and django-storages require patching for them to work.

We are rewriting our webpage and upgrading all dependencies including upgrading to python 3. I'm not sure that it is worth the effort yet. You do have to do alot of extra work just det get all dependencies working.

Regards,

Andréas

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/E570EE98-0691-404B-A1D8-DBA7112AF42B%40gmail.com.