Re: Compiled bytecode installed, because test suite was run
[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 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 should be removed by dh_python3
> * which leads to Lintian correctly complaining
> “package-installs-python-pycache-dir”.
>
> How do I convince Pybuild to run the tests as part of the package build
> (as normal), but clean up the compiled files *after* the tests and
> *before* gathering the installed files?
does your package name start with python3- or do you have
${python3:Depends} in Depends?
(yeah, something dh_python* should be more verbose about, will be fixed
soon)
--
Piotr Ożarowski Debian GNU/Linux Developer
www.ozarowski.pl www.griffith.cc www.debian.org
GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
Compiled bytecode installed, because test suite was run
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 the Python packages * which creates the compiled bytecode files * which remain in the package directories * which are scooped up by Pybuild for installation * which leads to Lintian correctly complaining “package-installs-python-pycache-dir”. How do I convince Pybuild to run the tests as part of the package build (as normal), but clean up the compiled files *after* the tests and *before* gathering the installed files? -- \ “The great thing about science is we can test our ideas.… But | `\ until we do, until we have data, it is just one more proposal.” | _o__) —Darren Saunders, 2015-12-02 | Ben Finney
Re: CPython hash randomization makes some Python packages unreproducible
On Apr 09, 2016, at 08:11 PM, Julien Cristau wrote: >FWIW I think that's a bad idea. A number of packages run their test >suite at build time, and running the tests with hash randomization >enabled seems to me like something we shouldn't give up. Completely agreed. Although we're in the long tail now, during the bulk of the Python 3 transition, we found real bugs when hash randomization was enabled. >Couldn't packages where the binary packages contents depend on the hash seed >just set one themselves? +1 -Barry
