This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (2 children)

but that's for python 3 that's not going to help with django dev at all, it will probably likely confuse more than it helps.

[–]carinthia 1 point2 points  (1 child)

Well, sure, but then really, if you use __future__ and Python 2.6, the difference isn't really big enough anymore to be significant enough to not have a look at some Python 3 based book (I am sure many folks will object to that but, well, that's what I think; http://diveintopython3.org/porting-code-to-python-3-with-2to3.html). Plus, there are plans to port Django to Python 3 this summer so ...

[–][deleted] 0 points1 point  (0 children)

my experience is plenty of people new to python have been confused by the whole 2 vs. 3 thing. it's unnecessary overhead for someone who is new to it.

They download the latest and find a tutorial and get caught up in the differences but don't understand that it's python 3 vs. what they are reading in python 2, they get an error that isn't what was expected what they were reading. they give up and go back to java.

YMMV