Thanks for all the replies everyone! It definitely seems like it'd be worthwhile just going through and learning 2.7 then and using related libraries to create

Thanks for all the replies everyone! It definitely seems like it'd be worthwhile just going through and learning 2.7 then and using related libraries to create what I want (once I've learned and am able to do so). However, this has me thinking. It seems like Ruby (and related frameworks, like Rails) don't have the backwards-compatibility issue that is seemingly plaguing Python? The newest version of Ruby was easily adopted (compared to Python 3) as it remained backwards-compatible. Even upon researching the next evolution of Ruby (2), it seems that it won't be huge leap and, again, will remain backwards-compatible. My question is... if I'm looking to start building a website now and use Python 2.7 (and likely Django), what would I do when the time comes and Python 3 is really the go-to version? Would I need to rewrite the code entirely? Will the older code ever become compatible or easily transitioned? It seems like Ruby would be the better choice to avoid possible fragmentation issues? I could be entirely wrong here though. So, please, if someone could help me with this, that would be great. I went through some of Learn Ruby the Hard Way. And I'm willing to switch over to Ruby. I like them both in different ways in terms of syntax/readability. But I don't know enough to really make a decision beyond that. But this Python fragmentation between 2 and 3 makes me worried. I'd feel safer choosing to learn Ruby. I don't know though.