homepage

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 marco.buttu
Recipients JelleZijlstra, berker.peksag, brett.cannon, ezio.melotti, marco.buttu, python-dev, r.david.murray, terry.reedy, zach.ware
Date 2017年01月28日.16:06:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1485619613.46.0.665830489125.issue27200@psf.upfronthosting.co.za>
In-reply-to
Content
In order for the patches to work for every Python version (see #msg284622 ), I added a new feature to the Sphinx doctest extension, called pyversion. Starting from Sphinx 1.6, it will be possible to specify the Python version in order for the example to be tested. For instance, if I run the doctests with Python 3.3, then this test will be skipped:
.. doctest::
 :pyversion: > 3.4
 # Code example
It will be tested only when Sphinx is running on Python > 3.4. My question is: what about using this feature in the patches? I am asking this because Sphinx 1.6 will be released in about 7-10 months, so until then, if we want to use the :pyversion: feature we have to build the documentation using the master version of Sphinx. Please, let me know
History
Date User Action Args
2017年01月28日 16:06:53marco.buttusetrecipients: + marco.buttu, brett.cannon, terry.reedy, ezio.melotti, r.david.murray, python-dev, berker.peksag, zach.ware, JelleZijlstra
2017年01月28日 16:06:53marco.buttusetmessageid: <1485619613.46.0.665830489125.issue27200@psf.upfronthosting.co.za>
2017年01月28日 16:06:53marco.buttulinkissue27200 messages
2017年01月28日 16:06:53marco.buttucreate

AltStyle によって変換されたページ (->オリジナル) /