Re: Python packaging, dependencies, upstream facilities
[Barry Warsaw, 2010-09-21]
> On Sep 21, 2010, at 10:30 AM, Piotr Ożarowski wrote:
> >I see only one sane way to fix the problem - changing Python
> >interpreter to recognize API from filenames, like foo.1.py foo.2.py
> >foo.2.3.py (with `import foo <= 2` as valid syntax) and let upstream
> >authors decide when to bump it, just like C guys do, but that's a
> >topic for python-devel mailing list...
>
> It would be, but I'm skeptical. In general, libraries tend to come in
> (Python) packages these days and you're generally not going to mix APIs in
> files within the same package, unless the package is itself managing multiple
> APIs. It might be something that distutils2 can attack, either through its
> metadata files or by encoding the API in package directory names.
foo.1/ foo.2/ foo.2.3/ i.e. versioned (Python) packages (and not
modules) sounds fine to me.
Changes in distutils2 will not help us much, as we still have to store
files somewhere (unless we'll automatically rename top level directories
to match .dist-info's API)
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
Reply to: