[Python-Dev] a suggestion ... Re: PEP 383 (again) (original) (raw)
Thomas Breuel tmbdev at gmail.com
Thu Apr 30 09:26:10 CEST 2009
- Previous message: [Python-Dev] a suggestion ... Re: PEP 383 (again)
- Next message: [Python-Dev] a suggestion ... Re: PEP 383 (again)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> 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.
CPython and IronPython are incompatible. And they will stay incompatible if the PEP is adopted.
They would become compatible if CPython adopted Mono and/or Java semantics.
Since both have had to deal with this, have you looked at what they actually do before proposing PEP 383? What did you find? Why did you choose an incompatible approach for PEP 383?
Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20090430/7120f22c/attachment.htm>
- Previous message: [Python-Dev] a suggestion ... Re: PEP 383 (again)
- Next message: [Python-Dev] a suggestion ... Re: PEP 383 (again)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]