We had several discussions about combining scipy-doctest and pytest-doctestplus. While the strategy is still TBD, previous work and discussions are scattered all over.
So the first order of business is to collect them together. A minimal, potentially incomplete list:
Cross-ref gh-59 for a discussion about the third option in the "better doctesting" space, xdoctest.
At least in the medium term, while the grand strategy is TBD, we are using the scipy-doctest pluggable and configurable architecture to bring it to feature parity with other tools (and pytest itself). Ongoing work:
Let's use this issue to (i) work out the long-term path forward, and (ii) flag missing features or quirks.
We had several discussions about combining
scipy-doctestandpytest-doctestplus. While the strategy is still TBD, previous work and discussions are scattered all over.So the first order of business is to collect them together. A minimal, potentially incomplete list:
--doctestsoption toruntests.pydoesn't do anything numpy/numpy#21070 (comment)scipy-doctest:scikit-learn's adoption: DOC Investigate scipy-doctest for more convenient doctests scikit-learn/scikit-learn#29027Cross-ref gh-59 for a discussion about the third option in the "better doctesting" space,
xdoctest.At least in the medium term, while the grand strategy is TBD, we are using the
scipy-doctestpluggable and configurable architecture to bring it to feature parity with other tools (and pytest itself). Ongoing work:xdoctest's Parser;pytest-doctestplus's Checker;pytest_extra_requiresto conditionally ignore paths / skip functions unless requirements are met #204 implementspytest_extra_requires, requested in DoctestPlus and optional dependencies #197Let's use this issue to (i) work out the long-term path forward, and (ii) flag missing features or quirks.