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%:
On 28 September 2012 03:57, Arnaud Fontaine ar...@debian.org wrote:
This is just a cosmetic change, as it does not bring anything,
especially considering that 'set -e' is used to make sure that the build
process fails if one of the command fails.
I hope Barry will chime in here - I'm
Hi,
Thomas Kluyver tho...@kluyver.me.uk writes:
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:
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
4 matches
Mail list logo
