Source: pyparsing
Version: 2.1.10+dfsg1-1
Severity: important
Dear Maintainer,
Since the update of pyparsing to 2.1.10, the sphinxcontrib-doxylink
package now FTBFS and is affected by an RC bug [1].
The failure occurs in the testsuite. The latter used to pass fine with
2.1.9 [2] but now fails with 2.1.10 [3]. The errors are all of the form:
```
Traceback (most recent call last):
> File "/<<PKGBUILDDIR>>/tests/test_parser.py", line 98, in
> test_numbers_for_defaults
> self.assertEqual(parsing.normalise(arglist[0]), arglist[1])
> File "/<<PKGBUILDDIR>>/sphinxcontrib/doxylink/parsing.py", line
> 116, in normalise
> argument_string_list.append(''.join((arg.qualifier,' ')))
> TypeError: sequence item 0: expected string, ParseResults found
```
Since I am no pyparsing expert, I was wondering whether you guys were
familiar with the specific features introduced with 2.1.10 which could
have caused this. I also filed a bug upstream [4] but I am not holding
my breath.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841582
[2]
https://ci.debian.net/data/packages/unstable/amd64/s/sphinxcontrib-doxylink/20161014_051640.autopkgtest.log.gz
[3]
https://ci.debian.net/data/packages/unstable/amd64/s/sphinxcontrib-doxylink/20161019_142357.autopkgtest.log.gz
[4]
https://bitbucket.org/birkenfeld/sphinx-contrib/issues/172/doxylink-typeerror-sequence-item-0
Cheers,
Ghis
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (900, 'testing'), (300, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
