On Feb 17, 2014, at 05:28 PM, Vincent Cheng wrote: >(My understanding of) the consensus is that modules should provide both >python2 and python3 packages when possible, and individual applications can >depend on either python2 or python3. I'm not entirely sure if there's >consensus on what happens in the case where a package provides both a python >module and is an application at the same time (I'll leave it to others on the >list to chime in), but in any case, that's not a blocker and is something you >can work on for future uploads anyways.
What I tend to do is to create a separate binary package which just contains the /usr/bin/foo script, and have that depend on python3-foo (or less desirably, python-foo). You'll already have two binary packages for python-foo and python3-foo, so a foo-bin binary package can make sense, as that will also contain manpages most likely. It gets a little more complicated if you need a 'foo' script which is Python-version dependent, e.g. nose. But those applications are rare. -Barry -- 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/20140217215659.2730a...@anarchist.wooz.org
