RetroSearch Browse

Mon Jul 19 05:52:42 CEST 2010 · https://mail.python.org/pipermail/python-dev/2010-July/102056.html

On Sun, Jul 18, 2010 at 11:46 PM, Eli Bendersky <eliben at gmail.com> wrote:
..
> However, I wonder what this means for backwards compatibility. Is it valid
> to switch trace.py to use the newer command-line argument parsing module
> that's only available in the newest versions of Python? I guess it could be
> since trace.py is stdlib which always arrives with its relevant version of
> Python. This *would* mean, however, that trace.py would be incompatible
> between 2.7 (argparse) and 2.6 (which doesn't have argparse), but I'm not
> sure how much of a problem this is.

As long as 3.x trace supports all command line options and switches
that 2.x does, I don't see any compatibility problems.   Adding more
options or using new language or library features in implementation
should be fine.

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

Showing content from https://mail.python.org/pipermail/python-dev/2010-July/102056.html below:

[Python-Dev] Markup of command-line options in Python's .rst documentation