Re: Compiled bytecode installed, because test suite was run

2016-04-12 Thread Ben Finney
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

Re: Compiled bytecode installed, because test suite was run

2016-04-12 Thread Piotr Ożarowski
[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

Re: Compiled bytecode installed, because test suite was run

2016-04-12 Thread Ben Finney
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? --

Re: Compiled bytecode installed, because test suite was run

2016-04-12 Thread Piotr Ożarowski
[Ben Finney, 2016-04-12] > I am packaging a code base, which has a test suite. The compiled byte > code from the test suite run, is being collected when Pybuild discovers > the resulting Python packages. > > As far as I can determine, these steps are occurring: > > * Pybuild runs the upstream