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


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

Re: Help fixing #959558 (case: FTBFS: AttributeError: 'tuple' object has no attribute 'lstrip' with sphinx 2.4)

Started byScott Talbert <swt@techie.net>
First post2020-05-26 23:10 +0200
Last post2020-05-27 11:30 +0200
Articles 3 — 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

  Re: Help fixing #959558 (case: FTBFS: AttributeError: 'tuple' object  has no attribute 'lstrip' with sphinx 2.4) Scott Talbert <swt@techie.net> - 2020-05-26 23:10 +0200
    Re: Help fixing #959558 (case: FTBFS: AttributeError: 'tuple' object  has no attribute 'lstrip' with sphinx 2.4) "Diego M. Rodriguez" <diego@moreda.io> - 2020-05-27 10:20 +0200
    Re: Help fixing #959558 (case: FTBFS: AttributeError: 'tuple' object  has no attribute 'lstrip' with sphinx 2.4) Dmitry Shachnev <mitya57@debian.org> - 2020-05-27 11:30 +0200

#12617 — Re: Help fixing #959558 (case: FTBFS: AttributeError: 'tuple' object has no attribute 'lstrip' with sphinx 2.4)

FromScott Talbert <swt@techie.net>
Date2020-05-26 23:10 +0200
SubjectRe: Help fixing #959558 (case: FTBFS: AttributeError: 'tuple' object has no attribute 'lstrip' with sphinx 2.4)
Message-ID<AaOZH-6YH-3@gated-at.bofh.it>
On Tue, 26 May 2020, Thomas Goirand wrote:

> Hi there!
>
> Does any of you knows how to fix this bug?
> https://bugs.debian.org/959558
>
> Almost all of OpenStack can removed from Bullseye if not fixed in time,
> so I tried to fix, but couldn't.

It looks like it's a bug in sphinx.  I tried sphinx 3.0.4 and it seems to 
work fine.  2.4.4 still has the problem, however.

Dmitry, do you plan to update to sphinx 3.0.x soon?

Scott

[toc] | [next] | [standalone]


#12619

From"Diego M. Rodriguez" <diego@moreda.io>
Date2020-05-27 10:20 +0200
Message-ID<AaZs5-4Wh-1@gated-at.bofh.it>
In reply to#12617

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

On 5/26/20 11:06 PM, Scott Talbert wrote:
> It looks like it's a bug in sphinx.

I'm suspecting the same - and I was also not able to reproduce it in
a local installation (pip-installed sphinx trying to match the
dependencies and versions). However, it seems the culprit is at
"case/mock.py":51:

call = mock.call

In case a new upload of sphinx does not land in time, perhaps a
workaround along the lines of:

diff --git a/docs/reference/case.mock.rst b/docs/reference/case.mock.rst
index 1a28a5c..2b6562c 100644
--- a/docs/reference/case.mock.rst
+++ b/docs/reference/case.mock.rst
@@ -9,3 +9,4 @@
 .. automodule:: case.mock
     :members:
     :undoc-members:
+    :exclude-members: call

might be acceptable? While not the ideal solution, the upstream
generated docs [1] end up including the docstring from
"unittest.mock._Call" [2] for that member, which might not provide too
much relevant info for end users anyway (and the inheritance from
"tuple" might be related to the original error).

[1] https://case.readthedocs.io/en/latest/reference/case.mock.html#case.mock.call
[2] https://github.com/python/cpython/blob/3.8/Lib/unittest/mock.py#L2352

-- 
Diego M. Rodriguez

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


#12620

FromDmitry Shachnev <mitya57@debian.org>
Date2020-05-27 11:30 +0200
Message-ID<Ab0xP-5y6-3@gated-at.bofh.it>
In reply to#12617

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

Hi all!

On Tue, May 26, 2020 at 05:06:16PM -0400, Scott Talbert wrote:
> On Tue, 26 May 2020, Thomas Goirand wrote:
> > Hi there!
> >
> > Does any of you knows how to fix this bug?
> > https://bugs.debian.org/959558
> >
> > Almost all of OpenStack can removed from Bullseye if not fixed in time,
> > so I tried to fix, but couldn't.
>
> It looks like it's a bug in sphinx.  I tried sphinx 3.0.4 and it seems to
> work fine.  2.4.4 still has the problem, however.
>
> Dmitry, do you plan to update to sphinx 3.0.x soon?

3.x won't happen soon, but I will fix this bug in the next Sphinx 2.4 upload.

--
Dmitry Shachnev

[toc] | [prev] | [standalone]


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


csiph-web