Control: tags 751908 + wontfix
thanks
When applications (e.g. tox) are Python 3 scripts but are contained in
binary packages named python-foo instead of python3-foo, pybuild won't
dh_python3, not pybuild.
* pybuild is for building/installing/testing
* dh_python3 is for messing with already
Sorry about the bug mis-identification (I knew better).
On Jun 18, 2014, at 11:58 AM, Piotr Ożarowski wrote:
However, in almost all such cases, the binary package will Depend:
${python3:Depends} so that should be a good enough indication that
the binary package should get those
I think this is fine, however we do need to be more explicit about cases where
a package is either split into bilingual libraries + executable, or just an
application with ancillary libraries (some might say private library).
python-foo packages have to provide public libraries, you can ship
On Jun 18, 2014, at 04:39 PM, Piotr Ożarowski wrote:
policy mentions that Python 2.X and Python 3.X are separate languages
for us and that's why we have python-foo and python3-foo packages.
I don't want APT to install python3 when I install python-foo and I
don't want APT to install python when I
Package: dh-python
Version: 1.20140511-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear Maintainer,
When applications (e.g. tox) are Python 3 scripts but are contained in
binary packages named python-foo instead of python3-foo, pybuild won't
apply Python 3 transformations
5 matches
Mail list logo
