[Jakub Wilk, 2012-02-13] > * Barry Warsaw <ba...@python.org>, 2012-02-07, 20:53: > >http://wiki.debian.org/Python/LibraryStyleGuide > > * “The package […] should have a working setup.py or setup.cfg file” > — err, surely setup.cfg without setup.py is not enough.
it will be enough soon (or was "packaging" released already?) > * “there appears to be no way to prevent distribute explicitly from > downloading the package” — some ideas how to do it: [...] > 3) Fool setuptools into using a non-functional HTTP proxy, e.g. by > setting this in your debian/rules: > > export http_proxy = http://127.0.0.1:9/ I will use this trick in pymultibuild, thanks (and since I mentioned it in public, now I have to get back into working on it, right? ;) > * “debian/*.pyremove […] Again, this does not need a Python 3 > version.” - why it's not needed for Python 3? since all Python 3 versions use the same directory¹ (and PEP402 is not implemented yet), you can use rm command in debian/rules without too many efforts [¹] /usr/lib/python3/dist-packages/ -- 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/20120213125853.gg28...@piotro.eu
