On Tue, Oct 8, 2013 at 3:48 AM, Ben Finney <ben+deb...@benfinney.id.au> wrote: > On 21-Sep-2013, Dmitry Shachnev wrote: >> Script /usr/bin/python3-coverage has a versioned shebang. Then why >> /usr/bin/python3.3-coverage is needed? > > This is merely a modification of what the upstream code does (creates > programs ‘coverage’, ‘coverage3’, ‘coverage-3.3’). I don't want to deviate > too far from upstream behaviour without good reason.
Then please make sure that shebang of "coverage3" is "#!/usr/bin/python3". Also, I think the consensus is that if the script can be invoked as "pythonX.Y -m MODULE", then the entry point can be dropped. For example, this change was made in nose and python-pip. >> Directories /usr/share/python-coverage and /usr/share/python3-coverage >> have identical contents. Maybe it'll make sense to use a single directory >> (i.e. /usr/share/coverage) and split it to a separate binary package >> (i.e. coverage-data)? > > That's a good idea, and I'm hoping to get to that soon. For now, my focus > is on getting a current Coverage into Debian. It's better to make that change early to avoid adding Breaks/Replaces in the future. -- Dmitry Shachnev -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
