-
Unicode <== Coding of the characters (all schemes) <== math.
For those who are interested in that field, I recommand to
try to understand why we (the world) have to live with
all these coding schemes.
jmf
--
https://mail.python.org/mailman/listinfo/python-list
Le dimanche 13 avril 2014 22:13:36 UTC+2, Terry Reedy a écrit :
> Everyone, please ignore Jim's unicode/fsr trolling, which started in
>
> July 2012. Don't quote it, don't try to answer it.
>
>
>
> --
>
> Terry Jan Reedy
---
FYI:
I was waiting for the final 3.4 release.
I'm only now ma
Everyone, please ignore Jim's unicode/fsr trolling, which started in
July 2012. Don't quote it, don't try to answer it.
--
Terry Jan Reedy
--
https://mail.python.org/mailman/listinfo/python-list
On Saturday, April 12, 2014 5:55:22 PM UTC+5:30, wxjm...@gmail.com wrote:
> --
>
> Regarding the Flexible String Representation, I have always
> been very coherent in the examples I gave (usually with and/or
> from an interactive intepreter - not relevant).
> I never seen once somebody pointin
Le samedi 12 avril 2014 14:53:15 UTC+2, Ned Batchelder a écrit :
> On 4/12/14 8:25 AM, wxjmfa...@gmail.com wrote:
>
> > --
>
> >
>
> > Regarding the Flexible String Representation, I have always
>
> > been very coherent in the examples I gave (usually with and/or
>
> > from an interactive
On 4/12/14 8:25 AM, wxjmfa...@gmail.com wrote:
--
Regarding the Flexible String Representation, I have always
been very coherent in the examples I gave (usually with and/or
from an interactive intepreter - not relevant).
I never seen once somebody pointing or beeing able to point
what is wro
--
Regarding the Flexible String Representation, I have always
been very coherent in the examples I gave (usually with and/or
from an interactive intepreter - not relevant).
I never seen once somebody pointing or beeing able to point
what is wrong in those examples.
jmf
--
https://mail.pyth
On 11/04/2014 17:02, Chris Angelico wrote:
On Sat, Apr 12, 2014 at 1:57 AM, Mark Lawrence wrote:
If you wish to interpret my words as baiting that's fine by me. From my
perspective I'm simply making a statement of fact.
It's almost now debatable whether you were metabaiting Steven into
telli
On 4/11/14 11:02 AM, Chris Angelico wrote:
It's almost now debatable whether you were metabaiting Steven into
telling you off for trolling the resident troll...
QOTW
--
https://mail.python.org/mailman/listinfo/python-list
On Sat, Apr 12, 2014 at 1:57 AM, Mark Lawrence wrote:
> If you wish to interpret my words as baiting that's fine by me. From my
> perspective I'm simply making a statement of fact.
It's almost now debatable whether you were metabaiting Steven into
telling you off for trolling the resident troll.
On 11/04/2014 16:49, Steven D'Aprano wrote:
On Fri, 11 Apr 2014 13:48:50 +0100, Mark Lawrence wrote:
On 11/04/2014 10:25, wxjmfa...@gmail.com wrote:
Unicode!
Works perfectly in Python 3.3+ thanks to the excellent work done as a
result of http://legacy.python.org/dev/peps/pep-0393/, the Fle
On Fri, 11 Apr 2014 13:48:50 +0100, Mark Lawrence wrote:
> On 11/04/2014 10:25, wxjmfa...@gmail.com wrote:
>>
>> Unicode!
>>
>>
> Works perfectly in Python 3.3+ thanks to the excellent work done as a
> result of http://legacy.python.org/dev/peps/pep-0393/, the Flexible
> String Representation, as
On 11/04/2014 10:25, wxjmfa...@gmail.com wrote:
Unicode!
Works perfectly in Python 3.3+ thanks to the excellent work done as a
result of http://legacy.python.org/dev/peps/pep-0393/, the Flexible
String Representation, as we, with one noticable exception, are
perfectly well aware of.
--
M
Unicode!
--
https://mail.python.org/mailman/listinfo/python-list
Steven D'Aprano writes:
> Today in Montreal Canada, there was a Language Summit to discuss the
> future of Python. Some highlights: […]
> More in this email thread here:
> https://mail.python.org/pipermail/python-dev/2014-April/133873.html
Thanks very much for this! Core development is importa
Today in Montreal Canada, there was a Language Summit to discuss the
future of Python. Some highlights:
PyPy is only three bug fixes away from shipping support for Python 3.2!
Guido confirms that easing the transition from 2.x to 3.x code is a major
priority. Version 2.7 is alive and in good he
16 matches
Mail list logo
