Eric Smith schrieb:
> The only problem I see is that the __future__ import of unicode_literals
> doesn't work in 3.0 yet. I'll look into fixing that.
The __future__ import of unicode_literals was added to py3k 26 hours
earlier:
Author: christian.heimes
Date: Wed Mar 26 23:34:47 2008
New Revisio
On Fri, Mar 28, 2008 at 5:33 AM, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> For now, it's best to put this on the wiki. That will allow many
> people to contribute.
Yeah, but the code would be more practical in an svn. But some docs in
the wiki would be a good idea. I'll see what I can do next w
On Thu, Mar 27, 2008 at 3:52 AM, Lennart Regebro <[EMAIL PROTECTED]> wrote:
> On Thu, Mar 27, 2008 at 5:33 AM, Talin <[EMAIL PROTECTED]> wrote:
> > -- A document describing the "common subset", and how to write programs
> > in it. This doesn't have to be a complete standalone manual, just an
>
Eric Smith wrote:
> Greg Ewing wrote:
>> Charles Merriam wrote:
>>> How can I write the greatest common denominator of this code:
>>>
>>> print "Hello World!" # yes, that needs to be Unicode.
>> Something like
>>
>>from __future__ import unicode_literals
>>from py3k_compat import Print
>>
Greg Ewing wrote:
> Charles Merriam wrote:
>> How can I write the greatest common denominator of this code:
>>
>> print "Hello World!" # yes, that needs to be Unicode.
>
> Something like
>
>from __future__ import unicode_literals
>from py3k_compat import Print
>
>Print("Hello World!
Charles Merriam wrote:
> How can I write the greatest common denominator of this code:
>
> print "Hello World!" # yes, that needs to be Unicode.
Something like
from __future__ import unicode_literals
from py3k_compat import Print
Print("Hello World!") # yes, that indeed is Unicode.
g
On Thu, Mar 27, 2008 at 5:33 AM, Talin <[EMAIL PROTECTED]> wrote:
> -- A document describing the "common subset", and how to write programs
> in it. This doesn't have to be a complete standalone manual, just an
> addendum to the regular Python docs explaining what things to avoid and
> how to g
Charles Merriam schrieb:
> On Wed, Mar 26, 2008 at 9:33 PM, Talin <[EMAIL PROTECTED]> wrote:
>
>> For new code, however, there is an alternative strategy that doesn't
>> involve 2to3 at all, which is to write code in the "greatest common
>> subset" of 2.6 and 3.0.
>>
>> As Lennart Regbro p
Charles Merriam wrote:
> On Wed, Mar 26, 2008 at 9:33 PM, Talin <[EMAIL PROTECTED]> wrote:
> ...
>> For new code, however, there is an alternative strategy that doesn't
>> involve 2to3 at all, which is to write code in the "greatest common
>> subset" of 2.6 and 3.0.
>>
>> As Lennart Regbro poin
On Wed, Mar 26, 2008 at 9:33 PM, Talin <[EMAIL PROTECTED]> wrote:
...
> For new code, however, there is an alternative strategy that doesn't
> involve 2to3 at all, which is to write code in the "greatest common
> subset" of 2.6 and 3.0.
>
> As Lennart Regbro pointed out earlier, this common sub
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 27, 2008, at 2:09 AM, Martin v. Löwis wrote:
>> For new code, however, there is an alternative strategy that doesn't
>> involve 2to3 at all, which is to write code in the "greatest common
>> subset" of 2.6 and 3.0.
>>
>> As Lennart Regbro pointe
Martin v. Löwis wrote:
>> For new code, however, there is an alternative strategy that doesn't
>> involve 2to3 at all, which is to write code in the "greatest common
>> subset" of 2.6 and 3.0.
>>
>> As Lennart Regbro pointed out earlier, this common subset is actually
>> quite large (larger than
> For new code, however, there is an alternative strategy that doesn't
> involve 2to3 at all, which is to write code in the "greatest common
> subset" of 2.6 and 3.0.
>
> As Lennart Regbro pointed out earlier, this common subset is actually
> quite large (larger than Guido originally intended,
We had a short discussion about Python 3.0 porting during our bi-weekly
Python meeting at Google, and it was suggested that I write up what was
discussed.
From reading the Python 3000 mailing list over the last several months,
it is apparent that there are many different approaches to making t
14 matches
Mail list logo
