RetroSearch Browse

Fri Sep 12 10:37:26 CEST 2014 · https://mail.python.org/pipermail/python-dev/2014-September/136316.html

On Fri, 12 Sep 2014 07:54:56 +0100
Jeff Allen <ja.py at farowl.co.uk> wrote:
> Simply having a block "for private use" seems to create an unmanaged 
> space for conflict, reminiscent of the "other 128 characters" in 
> bilingual programming. I wondered if the way to respect use by 
> applications might be to make it private to a particular sub-class of 
> str, idly however.

It's not private from Python's point of view, it's actually specified
in a PEP. So all Python 3 code has to follow the rule, and there's no
conflict internally.

The characters shouldn't leak out to other applications, unless the
user's code does its I/O very badly :-)

Regards

Antoine.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2014-September/136316.html below:

[Python-Dev] Multilingual programming article on the Red Hat Developer blog