Apologies for not responding sooner, this one got buried in my inbox. On Sep 19, 2012, at 05:41 PM, Thomas Kluyver wrote:
>I think Barry's key suggestion was to avoid using for loops to handle >multiple versions of Python 3. The example in LibraryStyleGuide uses >rules like this: > >build-python%: > python$* setup.py build > >override_dh_auto_build: $(PYTHON3:%=build-python%) > dh_auto_build > >CCed Barry in case he wants to offer other suggestions about >modernising d/rules. >For reference, the current d/rules file in Debian is here: >http://anonscm.debian.org/viewvc/pkg-zope/python-tz/trunk/debian/rules?view=markup I happen to like this style over the explicit for-loop because it's more succinct, and lets make do the hard lifting. It's easier to describe to folks, and easier to cargo cult, so I think in general it makes for less problematic d/rules files. Functionally, the two styles achieve the same results, so it's hard to argue on that point. Several of us debian-python folks settled on the current recommendations after much discussion in various forums, including tracker issues. Of course, the decision about which to use is always up to the maintainer, however I still personally recommend the LibraryStyleGuide version for Debian Python packagers. Cheers, -Barry And yep, I can't wait for python-multibuild ;). Maybe we need to get dh support for Python 3 in the meantime?
signature.asc
Description: PGP signature
