-
At the moment, `sage -coverage file.py` complains if `file.py` has no doctests of the form `s == loads(dumps(s))`. However, it says nothing if there is only one such doctest in `file.py`, independe…
-
Test failures on aarch64, i686 and s390x with gcc compilers and Fedora rawhide (40):
https://koji.fedoraproject.org/koji/taskinfo?taskID=107189797
s390x
```
[doctest] doctest version is "2.4.8"
…
-
Ubuntu 21.10 (X11) compile error on fresh clone when following build instructions.
```
In file included from ../src/wx/tests/tests.hpp:11,
from ../src/wx/tests/strutils.cpp:3:
.…
-
**Steps to reproduce:**
Create a property that spans multiple lines, like this:
```
-- prop> :{
-- \x -> x == x
-- :}
```
**Expected:**
The property will parse and execute correctly…
-
To Do:
- [ ] Properties
- [ ] Invariants
- [ ] Theorems
- [ ] Utilities
Note that inline `#` comments are not the same. We should have important information in doccomments, not doctests.
-
The current test only check that the library is usable and the code from the readme works.
Add tests from the original repository. They seem to require doctest, so maybe package this first.
Klaim updated
2 years ago
-
When invoking a fixture with doctests, output isn't captured, so output from subprocesses can be seen in the output even in subsequent tests. Consider this test:
```
import sys
import subprocess
…
-
I don't think the doctests are actually being run by github workflows and may be failing. this should be investigated.
-
In one of my codes I have a class that looks like:
``` python
import abc
import multiprocessing
class _BaseClass(object):
__metaclass__ = abc.ABCMeta
_manager = multiprocessing.Manager()
…
-
BPO | [42797](https://bugs.python.org/issue42797)
--- | :---
Nosy | @tim-one, @stevendaprano, @costas-basdekis
PRs | python/cpython#24028
*Note: these values reflect the state of the issue at the tim…