On Feb 03, 2010, at 09:55 AM, Guido van Rossum wrote:
On Wed, Feb 3, 2010 at 9:09 AM, Barry Warsaw ba...@python.org wrote:
-snip snip-
from __future__ import unicode_literals
def func(foo, bar):
print foo, bar
kw = {'foo': 7, 'bar': 9}
func(**kw)
-snip snip-
That
Nick Coghlan wrote:
Barry Warsaw wrote:
On Jan 31, 2010, at 01:44 PM, Nick Coghlan wrote:
We deliberate don't document -U because its typical effect is break the
world - it makes all strings unicode in 2.x.
It only affects string literals, not all strings.
As an aside, I think this should
On 02:52 pm, m...@egenix.com wrote:
Note that in Python 2.7 you can use
from __future__ import unicode_literals
on a per module basis to achieve much the same effect.
In Python 2.6 as well.
Jean-Paul
___
Python-Dev mailing list
exar...@twistedmatrix.com wrote:
On 02:52 pm, m...@egenix.com wrote:
Note that in Python 2.7 you can use
from __future__ import unicode_literals
on a per module basis to achieve much the same effect.
In Python 2.6 as well.
Right, but there are a few issues in 2.6 that will be
On 03:21 pm, m...@egenix.com wrote:
exar...@twistedmatrix.com wrote:
On 02:52 pm, m...@egenix.com wrote:
Note that in Python 2.7 you can use
from __future__ import unicode_literals
on a per module basis to achieve much the same effect.
In Python 2.6 as well.
Right, but there are
exar...@twistedmatrix.com wrote:
On 03:21 pm, m...@egenix.com wrote:
exar...@twistedmatrix.com wrote:
On 02:52 pm, m...@egenix.com wrote:
Note that in Python 2.7 you can use
from __future__ import unicode_literals
on a per module basis to achieve much the same effect.
In Python
On Feb 03, 2010, at 11:10 PM, Nick Coghlan wrote:
Ripping it out is probably a reasonable idea given that there is a much
better approach available now (i.e. trying to run under Py3k) that
actually has a vague hope of working.
Then again, if 2.7 really is the last non-maintenance 2.x release,
On Feb 03, 2010, at 04:21 PM, M.-A. Lemburg wrote:
exar...@twistedmatrix.com wrote:
On 02:52 pm, m...@egenix.com wrote:
Note that in Python 2.7 you can use
from __future__ import unicode_literals
on a per module basis to achieve much the same effect.
In Python 2.6 as well.
On Wed, Feb 3, 2010 at 9:09 AM, Barry Warsaw ba...@python.org wrote:
On Feb 03, 2010, at 04:21 PM, M.-A. Lemburg wrote:
exar...@twistedmatrix.com wrote:
On 02:52 pm, m...@egenix.com wrote:
Note that in Python 2.7 you can use
from __future__ import unicode_literals
on a per module
That will raise a TypeError in 2.6 but works in 2.7. Is it appropriate and
feasible to back port that to Python 2.6? I remember talking about this a
while back but I don't remember what we decided and I can't find a bug on the
issue.
I don't know about feasible but I think it's
On Wed, Feb 3, 2010 at 12:00 PM, Martin v. Löwis mar...@v.loewis.de wrote:
That will raise a TypeError in 2.6 but works in 2.7. Is it appropriate and
feasible to back port that to Python 2.6? I remember talking about this a
while back but I don't remember what we decided and I can't find a
11 matches
Mail list logo
