RetroSearch Browse

Mon Jun 4 00:50:15 CEST 2012 · https://mail.python.org/pipermail/python-dev/2012-June/119842.html

On 04.06.12 00:28, Nick Coghlan wrote:
> ...
> Backwards compatibility constraints mean we simply can't do that.
> However, as noted above, it may make sense to provide more ways for
> embedding applications to selectively access the behaviour through the
> C API.

Why that???
I don't see this.
If you have a new python version with a new file that has-to-be-there,
what is then the problem? The new version carries the new file, so I
don't see a compatibility issue, because this version does not want
to be backward-compatible. It just introduces the new file constraint,
and it produces what it needs.

Am I somehow blinded, maybe?

(yes, you all know that I am, so please be patient with me) -- Chris

-- 
Christian Tismer             :^)<mailto:tismer at stackless.com>
tismerysoft GmbH             :     Have a break! Take a ride on Python's
Karl-Liebknecht-Str. 121     :    *Starship* http://starship.python.net/
14482 Potsdam                :     PGP key ->  http://pgp.uni-mainz.de
work +49 173 24 18 776  mobile +49 173 24 18 776  fax n.a.
PGP 0x57F3BF04       9064 F4E1 D754 C2FF 1619  305B C09C 5A3B 57F3 BF04
       whom do you want to sponsor today?   http://www.stackless.com/

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

Showing content from https://mail.python.org/pipermail/python-dev/2012-June/119842.html below:

[Python-Dev] PEP 405 (built-in virtualenv) status