[sldev] Python libs in source tree

[Ryan Williams (Which)]

Tao Takashi wrote:
> Hey, it would be cool if you package those libraries up as eggs and put them
> somewhere for separate download so I can require them in my egg/buildout and
> they install automatically :-)

Yeah, it's sorta weird because it's such a grab bag of semi-independent
tools, it's hard to imagine anyone using all of them except for us (and
even we don't use all of them, hah).  I'd rather not have some
equivalent of py.lib, where you get a whole bunch of stuff that you're
not sure you really want just to get greenlet.  This might be just a
personal prejudice of mine, though, so feel free to set me straight if
the py.lib model actually rocks.

> some namespace packages would probably also be quite handy for this, so you
> can have different packages for each library but still can group them under
> one name.

Could we make an egg for each file, or something like that?  Seems like
it'd be the most fine-grained way to do it.

-RYaN