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/2005-December/058578.html below:

[Python-Dev] ElementTree - Why not part of the core? (fwd)

[Python-Dev] ElementTree - Why not part of the core? (fwd) [Python-Dev] ElementTree - Why not part of the core? (fwd)Fredrik Lundh fredrik at pythonware.com
Mon Dec 12 08:51:27 CET 2005
Martin v. Löwis wrote

> > And maybe PEP 291 could be updated to cover both compatibility with older
> > Python versions and other compatibility issues.
>
> So what would be the minimum Python version you keep compatibility with?

as Brett pointed out, the procedure to use for externally developed and
bundled components should be described in PEP 2.  but we need to list
them somewhere too; PEP 291 is as good as any other place.

> > Just say "go", and I'll start working on this.
>
> Not sure if it is me who should say that; as nobody else
> has spoken against it: go.

just one question: where do you want the "vendor" checkins ?  I'm using
a flat "kits" namespace in my own repositories, e.g.

    http://svn.python.org/kits/elementtree-1.2.6-20050316
    http://svn.python.org/kits/jpeg-6b
    http://svn.python.org/kits/zlib-1.2.1

or, as commands for this specific case:

    $ wget http://effbot.org/downloads/elementtree-1.2.6-20050316.tar.gz
    $ tar xvfz elementtree-1.2.6-20050316.tar.gz
    $ svn import elementtree-1.2.6-20050316
        svn+ssh://pythondev@svn.python.org/kits/elementtree-1.2.6-20050316

anyone has a better name?

</F>



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