[Python-Dev] readd u'' literal support in 3.3?

[Michael Foord]

On 13/12/2011 14:24, Nick Coghlan wrote:
>
> Input = normal 2.x code; Output = code that runs on both 2.x and 3.x.
>
> That is, tinkering with what 2to3 produces, not what it accepts.
>

How is that different from what 2to3 currently does? Are you agreeing 
with Laurence, suggesting an alternative, or something else?

Michael

> --
> Nick Coghlan (via Gmail on Android, so likely to be more terse than usual)
>
> On Dec 13, 2011 11:46 PM, "Michael Foord" <fuzzyman at voidspace.org.uk 
> <mailto:fuzzyman at voidspace.org.uk>> wrote:
>
>     On 13/12/2011 13:33, Laurence Rowe wrote:
>
>         On Mon, 12 Dec 2011 22:18:40 +0100, Chris McDonough
>         <chrism at plope.com <mailto:chrism at plope.com>> wrote:
>
>             On Mon, 2011-12-12 at 09:50 -0500, PJ Eby wrote:
>
>
>                        As someone who ported WebOb and other stuff
>                 built on top of it
>                        to Python
>                        3 without using "from __future__ import
>                 unicode_literals", I'm
>                        kinda sad
>                        that to be using best practice I'll have to go
>                 back and flip
>                        the
>                        polarity on everything.
>
>
>                 Eh?  If you don't need unicode_literals, what's the
>                 problem?
>
>
>             Porting the WebOb code sucked.  It's only about 5K lines
>             of code but the
>             porting effort took me about 80 hours.  Some of the
>             problem is certainly
>             my own idiocy, but some of it is just because straddling
>             code across
>             Python 2 and Python 3 currently requires that you change
>             lots and lots
>             of code for suspect benefit.
>
>
>         Could this manual work be cut down if there was a version of
>         2to3 that targeted the subset of the language that is
>         compatible with both 2 and 3? That would seem to avoid most of
>         the drawbacks to the current 2to3 approach.
>
>     I'm not sure what you mean, but it *reads* as if you mean "a
>     version of 2to3 that only converts code that doesn't need
>     converting". Could you clarify?
>
>     Thanks,
>
>     Michael
>
>         Laurence
>
>         _______________________________________________
>         Python-Dev mailing list
>         Python-Dev at python.org <mailto:Python-Dev at python.org>
>         http://mail.python.org/mailman/listinfo/python-dev
>         Unsubscribe:
>         http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk
>
>
>
>     -- 
>     http://www.voidspace.org.uk/
>
>     May you do good and not evil
>     May you find forgiveness for yourself and forgive others
>     May you share freely, never taking more than you give.
>     -- the sqlite blessing http://www.sqlite.org/different.html
>
>     _______________________________________________
>     Python-Dev mailing list
>     Python-Dev at python.org <mailto:Python-Dev at python.org>
>     http://mail.python.org/mailman/listinfo/python-dev
>     Unsubscribe:
>     http://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com
>


-- 
http://www.voidspace.org.uk/

May you do good and not evil
May you find forgiveness for yourself and forgive others
May you share freely, never taking more than you give.
-- the sqlite blessing http://www.sqlite.org/different.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20111213/49f24785/attachment.html>