Re: .egg-info for entry points during dh_auto_test

2021-10-21 Thread Stefano Rivera
Hi Michael (2021.10.21_18:55:51_+) > pytest-lazy-fixtures is a pytest plugin and registers itself through the > Python entrypoints mechanism. In its unitests, it assumes that this > registration has already happened but during dh_auto_test there is no > .egg-info directory available. I could us

.egg-info for entry points during dh_auto_test

2021-10-21 Thread Michael Fladischer
Hi, I'm working on src:pytest-lazy-fixtures and was trying to get the unittests to run but it seems that I have run into a problem that I'm not sure on how to fix it in a clean way. pytest-lazy-fixtures is a pytest plugin and registers itself through the Python entrypoints mechanism. In its

Re: Sphinx theme package naming conventions

2021-10-21 Thread Andrius Merkys
Hi Dmitry, On 2021-10-21 14:38, Dmitry Shachnev wrote: > On Thu, Oct 21, 2021 at 10:26:53AM +0300, Andrius Merkys wrote: >> Is it OK to follow [1] and stay faithful to upstream name, or should I >> rename both source and binary packages to match already existing sphinx >> theme package names? > I

Re: Sphinx theme package naming conventions

2021-10-21 Thread Dmitry Shachnev
Hi Andrius! On Thu, Oct 21, 2021 at 10:26:53AM +0300, Andrius Merkys wrote: > Hello, > > I am working to package sphinx_press_theme (ITP bug #996543). According > to Python package naming conventions [1] proper binary package name for > it would be python3-sphinx-press-theme. However, most of sphi

Sphinx theme package naming conventions

2021-10-21 Thread Andrius Merkys
Hello, I am working to package sphinx_press_theme (ITP bug #996543). According to Python package naming conventions [1] proper binary package name for it would be python3-sphinx-press-theme. However, most of sphinx theme packages seem to be named $THEME_NAME-sphinx-theme (source package), resultin