Re: Compiled bytecode installed, because test suite was run

Piotr Ożarowski writes: > [Ben Finney, 2016-04-12] > > * Pybuild runs the upstream test suite > > * which imports the Python packages > > * which creates the compiled bytecode files > > * which remain in the package directories > > * which are scooped up by Pybuild for installation > > * which sh

Re: python-mkdocs new dependancy

[Brian May, 2016-04-12] > When building python-mkdocs from git source I get this error: > > LANG=C.UTF-8 PYTHONPATH=. ./debian/scripts/mkdocs build > Traceback (most recent call last): > File "./debian/scripts/mkdocs", line 7, in > from mkdocs.__main__ import cli > File "/<>/mkdocs/__main

Re: Compiled bytecode installed, because test suite was run

[Ben Finney, 2016-04-12] > Piotr Ożarowski writes: > > > does your package name start with python3- or do you have > > ${python3:Depends} in Depends? > > Both, yes. The “Depends” field contains “${python3:Depends}”. > > Is there anything I can do to diagnose this more precisely? Some part of >

Re: Compiled bytecode installed, because test suite was run

Piotr Ożarowski writes: > does your package name start with python3- or do you have > ${python3:Depends} in Depends? Both, yes. The “Depends” field contains “${python3:Depends}”. Is there anything I can do to diagnose this more precisely? Some part of the ‘sbuild’ output? -- \ “[I]t is