On Sun, Oct 25, 2009 at 4:30 PM, aharrisreid <[email protected]> wrote: > > I am very much new to Python, and one of my first projects is a simple > data-based website. However, looking to the future, I am > starting with Python 3.1 (I can hear many of you shouting "don't - > start with 2.6"), so I need to know - is Pylons compatible with 3.1 > yet. If not, are plans in the pipeline?
There have been some snags porting WSGI to Python 3, so all WSGI frameworks are stuck on Python 2. The biggest problem is the changing nature of strings. WSGI assumes strings are bytestring but in Python 3 they're Unicode. This gets into which layer should decode the HTTP headers, and what to do if the headers have no encoding specified. There are also proposals to simplify the protocol and make it friendly to asynchronous servers (if that's possible). People disagree on how to approach these, and there has been no consensus. Most people are content to use Python 2, and there has been no groundswell pushing for Python 3 yet. There's supposedly some action on this on the Web-Sig, but I haven't read it recently. -- Mike Orr <[email protected]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
