Hi Barry, On Tue, Nov 05, 2013 at 06:55:33PM -0500, Barry Warsaw wrote: > Today I migrated the enum34 package to use pybuild. Win! > Based on that, I've done a pass through the library style guide, which I was > able to greatly simplify. > https://wiki.debian.org/Python/LibraryStyleGuide > Please take a look, edit as necessary or follow up here for more discussion. > There's one little white lie currently: debian/*.pyremove files aren't yet > supported for Python 3 package, but Piotr is going to enable that with the > next upload of dh-python. A few questions: (On PYBUILD_NAME) Here, we're telling it that the name is foo. This should match the source package name, so for example, in enum34, you'd see: [...] If it's supposed to match the source package name, why does it need to be specified at all? Shouldn't the debhelper-based build system figure that out on its own? (Ignoring for the moment pybuilder's rather non-dh use of environment variables generally) dh $@ --with python2,python3 --buildsystem=pybuild Why does the build system need to be specified explicitly? Debhelper build systems are meant to use the check_auto_buildable method to declare whether they should or should not be used. Why can pybuild not autodetect? Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slangasek@ubuntu.com vorlon@debian.org
Attachment:
signature.asc
Description: Digital signature