Hi,

I'm stuck at this odd behavior:

when I build a package in my current environment (debian/testing),
sphinx-build ... works correctly.

when building in sbuild, sphinx-build doesn't find current module: ModuleNotFoundError: No module named 'xxx'
in docs/conf.py at
from xxx import __version__

I don't understand which other debian package is modifying that outcome.

Any idea ?

<div dir="ltr">Hi,<div><br></div><div>I&#39;m stuck at this odd behavior:</div><div><br></div><div>when I build a package in my current environment (debian/testing),</div><div>sphinx-build ... works correctly.</div><div><br></div><div>when building in
sbuild, sphinx-build doesn&#39;t find current module:</div><div>ModuleNotFoundError: No module named &#39;xxx&#39;<br></div><div>in docs/conf.py at</div><div>from xxx import __version__<br></div><div><br></div><div>I don&#39;t understand which other
debian package is modifying that outcome.</div><div><br></div><div>Any idea ?</div><div><br></div><div><br></div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, Jan 08, 2024 at 01:22:54PM +0100, J�r�my Lal wrote:

Hi,
I'm stuck at this odd behavior:
when I build a�package in my current environment (debian/testing), sphinx-build ... works correctly.
when building in sbuild, sphinx-build doesn't find current module: ModuleNotFoundError: No module named 'xxx'
in�docs/conf.py at
from xxx import __version__
I don't understand which other debian package is modifying that outcome.
Any idea ?

Perhaps your local build is importing from a globally-installed
version of the package? (For example, you're building version 1.3 of python3-foo, but you already have version 1.2 of python3-foo
installed.)

Best wishes,

Julian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Le lun. 8 janv. 2024 à 13:46, Julian Gilbey <julian@d-and-j.net> a écrit :

On Mon, Jan 08, 2024 at 01:22:54PM +0100, Jérémy Lal wrote:

Hi,
I'm stuck at this odd behavior:
when I build a package in my current environment (debian/testing), sphinx-build ... works correctly.
when building in sbuild, sphinx-build doesn't find current module: ModuleNotFoundError: No module named 'xxx'
in docs/conf.py at
from xxx import __version__
I don't understand which other debian package is modifying that outcome. Any idea ?

Perhaps your local build is importing from a globally-installed
version of the package? (For example, you're building version 1.3 of python3-foo, but you already have version 1.2 of python3-foo
installed.)

Damn, that new package I'm working on already exists ｡•́︿•̀｡

<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le lun. 8 janv. 2024 à 13:46, Julian Gilbey &lt;<a href="mailto:julian@d-and-j.net">julian@d-and-j.net</a>&gt; a écrit :<br></div><blockquote
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, Jan 08, 2024 at 01:22:54PM +0100, Jérémy Lal wrote:<br>
&gt; Hi,<br>
&gt; I&#39;m stuck at this odd behavior:<br>
&gt; when I build a package in my current environment (debian/testing),<br> &gt; sphinx-build ... works correctly.<br>
&gt; when building in sbuild, sphinx-build doesn&#39;t find current module:<br> &gt; ModuleNotFoundError: No module named &#39;xxx&#39;<br>
&gt; in docs/conf.py at<br>
&gt; from xxx import __version__<br>
&gt; I don&#39;t understand which other debian package is modifying that outcome.<br>
&gt; Any idea ?<br>

Perhaps your local build is importing from a globally-installed<br>
version of the package?  (For example, you&#39;re building version 1.3 of<br> python3-foo, but you already have version 1.2 of python3-foo<br> installed.)<br></blockquote><div><br></div><div>Damn, that new package I&#39;m working on already exists ｡•́︿•̀｡</div></div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)