A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2009-April/089245.html below:

[Python-Dev] a suggestion ... Re: PEP 383 (again)

[Python-Dev] a suggestion ... Re: PEP 383 (again) [Python-Dev] a suggestion ... Re: PEP 383 (again)"Martin v. Löwis" martin at v.loewis.de
Thu Apr 30 08:42:21 CEST 2009
Thomas Breuel wrote:
> On Thu, Apr 30, 2009 at 05:40, Curt Hagenlocher <curt at hagenlocher.org
> <mailto:curt at hagenlocher.org>> wrote:
> 
>     IronPython will inherit whatever behavior Mono has implemented. The
>     Microsoft CLR defines the native string type as UTF-16 and all of the
>     managed APIs for things like file names and environmental variables
>     operate on UTF-16 strings -- there simply are no byte string APIs.
> 
> 
> Yes.  Now think about the implications.  This means that adopting PEP
> 383 will make IronPython and Jython running on UNIX intrinsically
> incompatible with CPython running on UNIX, and there's no way to fix that. 

*Not* adapting the PEP will also make CPython and IronPython
incompatible, and there's no way to fix that.

Regards,
Martin
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4