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


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

Bug#895849: sphinxcontrib-autoprogram: Incompatible with Sphinx 1.7

Started byAndreas Tille <andreas@an3as.eu>
First post2018-04-17 11:30 +0200
Last post2018-04-18 16:40 +0200
Articles 4 — 3 participants

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

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#895849: sphinxcontrib-autoprogram: Incompatible with Sphinx 1.7 Andreas Tille <andreas@an3as.eu> - 2018-04-17 11:30 +0200
    Bug#895849: sphinxcontrib-autoprogram: Incompatible with Sphinx 1.7 Bas Couwenberg <sebastic@xs4all.nl> - 2018-04-17 11:40 +0200
      Bug#895849: sphinxcontrib-autoprogram: Incompatible with Sphinx 1.7 Andreas Tille <andreas@an3as.eu> - 2018-04-17 12:20 +0200
    Bug#895849: sphinxcontrib-autoprogram: Incompatible with Sphinx 1.7 Dmitry Shachnev <mitya57@debian.org> - 2018-04-18 16:40 +0200

#10418 — Bug#895849: sphinxcontrib-autoprogram: Incompatible with Sphinx 1.7

FromAndreas Tille <andreas@an3as.eu>
Date2018-04-17 11:30 +0200
SubjectBug#895849: sphinxcontrib-autoprogram: Incompatible with Sphinx 1.7
Message-ID<vFv61-2Of-1@gated-at.bofh.it>
Hi,

On Mon, Apr 16, 2018 at 09:48:28PM +0200, Bas Couwenberg wrote:
> Source: sphinxcontrib-autoprogram
> Version: 0.1.2-1

I applied the suggested patch to version 0.1.4 since I wanted to upload
this version anyway.  However, when trying to build the package in Git[1]
I get a test suite failure:

...
test_make_rst (sphinxcontrib.autoprogram.AutoprogramDirectiveTestCase)
Alt least it shouldn't raise errors during making RST string. ... ERROR
test_import_object (sphinxcontrib.autoprogram.UtilTestCase) ... ok

======================================================================
ERROR: test_make_rst (sphinxcontrib.autoprogram.AutoprogramDirectiveTestCase)
Alt least it shouldn't raise errors during making RST string.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/build/sphinxcontrib-autoprogram-0.1.4/sphinxcontrib/autoprogram.py", line 398, in test_make_rst
    list(self.directive.make_rst())
  File "/build/sphinxcontrib-autoprogram-0.1.4/sphinxcontrib/autoprogram.py", line 162, in make_rst
    parser = import_object(import_name or '__undefined__')
  File "/build/sphinxcontrib-autoprogram-0.1.4/sphinxcontrib/autoprogram.py", line 139, in import_object
    raise ImportError("No module named {}".format(module_name))
ImportError: No module named cli

----------------------------------------------------------------------
Ran 6 tests in 0.003s

FAILED (errors=1)
Test failed: <unittest.runner.TextTestResult run=6 errors=1 failures=0>
error: Test failed: <unittest.runner.TextTestResult run=6 errors=1 failures=0>
...


I can confirm that there is no such module cli.  Before I report the
issue upstream I'd like to ask for confirmation that it is not just me
overlooking something.

Thanks for any help

      Andreas.

[1] https://salsa.debian.org/med-team/sphinxcontrib-autoprogram

-- 
http://fam-tille.de

[toc] | [next] | [standalone]


#10419

FromBas Couwenberg <sebastic@xs4all.nl>
Date2018-04-17 11:40 +0200
Message-ID<vFvfI-2R5-3@gated-at.bofh.it>
In reply to#10418
On 2018-04-17 11:25, Andreas Tille wrote:
> On Mon, Apr 16, 2018 at 09:48:28PM +0200, Bas Couwenberg wrote:
>> Source: sphinxcontrib-autoprogram
>> Version: 0.1.2-1
> 
> I applied the suggested patch to version 0.1.4 since I wanted to upload
> this version anyway.  However, when trying to build the package in 
> Git[1]
> I get a test suite failure:

The changes from the PR in question were already included in 0.1.4, and 
subsequently changed in later commits in that release.

  
https://github.com/sphinx-contrib/autoprogram/commit/2debd1489c5a576a8f33b27e847077b860319916

Try building just 0.1.4 without the patch.

Kind Regards,

Bas

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


#10420

FromAndreas Tille <andreas@an3as.eu>
Date2018-04-17 12:20 +0200
Message-ID<vFvSp-3kJ-1@gated-at.bofh.it>
In reply to#10419
> 
> The changes from the PR in question were already included in 0.1.4, and
> subsequently changed in later commits in that release.
> 
> https://github.com/sphinx-contrib/autoprogram/commit/2debd1489c5a576a8f33b27e847077b860319916
> 
> Try building just 0.1.4 without the patch.

This is what I did some days ago.  The patch is not the issue for the
build failure.  I removed the patch from git again - any help is
welcome. 

Kind regards

       Andreas.

-- 
http://fam-tille.de

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


#10423

FromDmitry Shachnev <mitya57@debian.org>
Date2018-04-18 16:40 +0200
Message-ID<vFWpA-435-11@gated-at.bofh.it>
In reply to#10418

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

Hi Andreas,

On Tue, Apr 17, 2018 at 11:25:36AM +0200, Andreas Tille wrote:
> I applied the suggested patch to version 0.1.4 since I wanted to upload
> this version anyway.  However, when trying to build the package in Git[1]
> I get a test suite failure:
>
> [...]
> ImportError: No module named cli
> [...]
>
> I can confirm that there is no such module cli.  Before I report the
> issue upstream I'd like to ask for confirmation that it is not just me
> overlooking something.
>
> Thanks for any help

This test needs the doc/cli.py file. It is present in upstream Git but
not in the released tarball:

https://github.com/sphinx-contrib/autoprogram/blob/master/doc/cli.py

Try either adding this file using a patch, or using a tarball from Github
rather than from PyPI.

--
Dmitry Shachnev

[toc] | [prev] | [standalone]


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


csiph-web