Re: Compiled bytecode installed, because test suite was run

2016-04-13 Thread Piotr Ożarowski
[Ben Finney, 2016-04-13] > package_share_dir = /usr/share/${PACKAGE_NAME} > export PYBUILD_INSTALL_ARGS ?= \ >--install-lib=${package_share_dir}/ \ >--install-scripts=${package_share_dir}/ > > So with Pybuild configured correctly, that should mean I don't need to >

Re: Compiled bytecode installed, because test suite was run

2016-04-13 Thread Ben Finney
Piotr Ożarowski writes: > [Ben Finney, 2016-04-13] > > One complication may have been that the directory name to which the > > library was installed (with the “--install-lib” option) does not > > contain the Debian package name. > > […] By changing --install-lib you modified

Re: Compiled bytecode installed, because test suite was run

2016-04-13 Thread Piotr Ożarowski
> PYBUILD_NAME and PYBUILD_DESTDIR are pybuild related, dh_python3 doesn't > use them. By changing --install-lib you modified destination directory > anyway (and you should point dh_python3 to the same dir - it doesn't > know about pybuild's existence) FTR: PYBUILD_DESTDIR is like DESTDIR but

Re: Compiled bytecode installed, because test suite was run

2016-04-13 Thread Piotr Ożarowski
[Ben Finney, 2016-04-13] > 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 > > > *

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

Compiled bytecode installed, because test suite was run

2016-04-11 Thread Ben Finney
Howdy all, 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 test suite * which imports