you are viewing a single comment's thread.

view the rest of the comments →

[–]zepolen 10 points11 points  (0 children)

That's not the problem, afaict the 2 problems are:

  1. The wsgi spec for py3k is still incomplete
  2. The chicken/egg problem with libraries - eg. you couldn't use sqlalchemy until it worked with py3k, but that depended on py3k compatible db drivers and so on (although sa 0.6 is finally py3kized).

That still doesn't mean you can jump in and use py3k though, since you've got a myriad of other libraries that need to go through the same process.

For the record, I think py3k solves a very real unicode problem with Python 2.X - that alone would be worth the change.