[Barry Warsaw, 2011-06-10]
> Ah, yeah. Y'know, I am personally not a fan of private modules anyway :).
/me waits till Barry will try to package his 13th package with
Python application that uses "lib" or "tests" module names...
(or will he break after 4th? Bets anyone? ;)
> Note too in a setuptools(?)/distribute/packaging world, you might not actually
> have a `foo` script in the source at all. For example, Mailman 3 has this in
> its setup.py:
>
> template = Template('$script = mailman.bin.$script:main')
> scripts = set(
> template.substitute(script=script)
> for script in ('mailman', 'runner', 'master', 'onebounce')
> )
> setup(
> ...
> entry_points = {
> 'console_scripts' : list(scripts),
> },
> ...)
>
> so in fact /usr/bin/mailman doesn't exist until the system is built out.
> /usr/bin/mailman gets generated and essentially imports the
> `mailman.bin.mailman` module, then runs the main() function.
you realize that setuptools/distribute hardcodes versions and forces you
to depend on python-setuptools/python-pkg-resources, right?
--
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
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110610201342.gt24...@piotro.eu
