Thanks for responding. This is food for thought and may be encouraging. We "just jumped on Python 3.0 shortly after release" and have been using it without a glitch for four years. I don't doubt your claim about Python 3.0's "readiness for production", though, because workstation number and text crunching "production" and high-volume web "production" are so different, but (in addition to other languages) we've been using Python3 as our only Python for years with no (known) problems.
I'd prefer to start doing webdev in Python3, too, as long as we can just work in Python3 without having our framework's (or our framework's vast, tortured userbase's) endless upgrade problems become our problems. We have no Python2 legacy baggage of our own, and I have no desire to go back and pick up anybody else's.
So when, approximately, will Django 1.6 ship, with "no reservations" about Python3 for production?
And do you have an estimate for when Django will deprecate Python2 entirely, so that Python3 programmers will become the assumed target for all features, docs, tutorials, code snippet examples, add-on modules, etc?
I'd prefer to start doing webdev in Python3, too, as long as we can just work in Python3 without having our framework's (or our framework's vast, tortured userbase's) endless upgrade problems become our problems. We have no Python2 legacy baggage of our own, and I have no desire to go back and pick up anybody else's.
So when, approximately, will Django 1.6 ship, with "no reservations" about Python3 for production?
And do you have an estimate for when Django will deprecate Python2 entirely, so that Python3 programmers will become the assumed target for all features, docs, tutorials, code snippet examples, add-on modules, etc?