In February, I reported a doctest bug against 2.3.3 (request id 902628) and attached a patch to fix the problem. 2.4 alpha 1 still shows this behavior: Traceback (most recent call last): File "/tmp/confuse_doctest.py", line 14, in ? import doctest, confuse_doctest File "/tmp/confuse_doctest.py", line 15, in ? doctest.testmod(confuse_doctest) File "/usr/local/lib/python2.4/doctest.py", line 1155, in testmod f, t = tester.rundict(m.__dict__, name, m) File "/usr/local/lib/python2.4/doctest.py", line 915, in rundict f2, t2 = self.__runone(value, name + "." + thisname) File "/usr/local/lib/python2.4/doctest.py", line 1076, in __runone return self.rundoc(target, name) File "/usr/local/lib/python2.4/doctest.py", line 836, in rundoc f2, t2 = self.run__test__(d, name) File "/usr/local/lib/python2.4/doctest.py", line 944, in run__test__ raise TypeError("Tester.run__test__: values in " TypeError: Tester.run__test__: values in dict must be strings, functions, methods, or classes; <super: <class 'A'>, NULL> What can I do to help getting this fixed? -- Christian Tanzer http://www.c-tanzer.at/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4