Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #15398 > unrolled thread

sphinx-build module not found in sbuild

Started byJérémy Lal <kapouer@melix.org>
First post2024-01-08 13:30 +0100
Last post2024-01-08 14:00 +0100
Articles 3 — 2 participants

Back to article view | Back to linux.debian.maint.python


Contents

  sphinx-build module not found in sbuild Jérémy Lal <kapouer@melix.org> - 2024-01-08 13:30 +0100
    Re: sphinx-build module not found in sbuild Julian Gilbey <julian@d-and-j.net> - 2024-01-08 13:50 +0100
      Re: sphinx-build module not found in sbuild Jérémy Lal <kapouer@melix.org> - 2024-01-08 14:00 +0100

#15398 — sphinx-build module not found in sbuild

FromJérémy Lal <kapouer@melix.org>
Date2024-01-08 13:30 +0100
Subjectsphinx-build module not found in sbuild
Message-ID<HTWVr-1FFc-3@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

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 ?

[toc] | [next] | [standalone]


#15399

FromJulian Gilbey <julian@d-and-j.net>
Date2024-01-08 13:50 +0100
Message-ID<HTXeN-1FLn-9@gated-at.bofh.it>
In reply to#15398
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

[toc] | [prev] | [next] | [standalone]


#15400

FromJérémy Lal <kapouer@melix.org>
Date2024-01-08 14:00 +0100
Message-ID<HTXot-1FOI-1@gated-at.bofh.it>
In reply to#15399

[Multipart message — attachments visible in raw view] — view raw

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 。•́︿•̀。

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.maint.python


csiph-web