This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ned.deily
Recipients Arthur-Milchior, docs@python, ned.deily
Date 2021-12-02.18:20:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1638469231.66.0.707811398777.issue45920@roundup.psfhosted.org>
In-reply-to
Content
> So I guess the only way to actually get make doctest to work is if the virtual env uses the version of python in main. Is there anyway to do that?

By default, the Doc/Makefile "venv" target uses the first "python3" it finds on your shell PATH to build the venv and sphinx. Either arrange for "python3" to point at a Python of the same release family on your PATH or you can use the PYTHON= command line argument to "make venv" to specify the path to the interpreter, for example:

cd cpython
./configure && make
cd Doc
make clean venv doctest PYTHON=../python
  [...]
  Doctest summary
  ===============
   2388 tests
      0 failures in tests
      0 failures in setup code
      0 failures in cleanup code
  build succeeded.
  [...]
History
Date User Action Args
2021-12-02 18:20:31ned.deilysetrecipients: + ned.deily, docs@python, Arthur-Milchior
2021-12-02 18:20:31ned.deilysetmessageid: <1638469231.66.0.707811398777.issue45920@roundup.psfhosted.org>
2021-12-02 18:20:31ned.deilylinkissue45920 messages
2021-12-02 18:20:31ned.deilycreate