Re: Re: Python Egg Guidelines across distros
Hi,
The reason why I get rid of setuptools as a install and runtime
requirement is that they introduce a huge over head on the import, using
namespace packages. I searched my mailbox all across to find the
discussion about that, but it seems it was done orally rather than on
mail. Anyway, Fernando Perez spent some time profiling to get some hard
numbers on this, and they are not pretty.
> However, I don't agree that setuptools is only a build requirement.
> setuptools makes writing plugins for a package much easier than starting
> from scratch.
That's a good point. That's what they where design to do, in the
beginning.
> Also, eggs (as in the egg metadata that comes with the packages; not the
> optional pseudo-jar copying zip format) may be duplication but it is not
> needless duplication. Elf shared libraries and packages contain
> duplicate information but we don't call for removal of versioning
> information from either of those because it's provided by the other.
> Package versioning is useful at install time. Shared library versioning
> and egg versioning are useful at runtime.
Yes. To be fair, setuptools are coming in to address a fundamental limit
of Python's import mechanism, and they are a very important project. I
feel pretty bad about bashing them. It is true that if nobody actually
works with Philip Elby (I mean send good patches) to improve them, they
will never work as we need them to work. Sigh ! I just don't have time
for that, I already wonder why I am spending my nights in front of a
computer.
Anyway, it a good project for a talented Python packager and the
community badly needs it to happen.
Gaël
Reply to: