[issue15939] make *.rst files in Doc/ parseable by doctest

Changes by Ezio Melotti : -- type: -> enhancement versions: -Python 3.2 Added file: http://bugs.python.org/file31339/issue15939-ctypes-2.diff ___ Python tracker ___ ___

[issue15939] make *.rst files in Doc/ parseable by doctest

Chris Jerdonek added the comment: > FTR there were a few actual errors that I fixed (mostly about bytes vs > string). Great! Note that for the others, I was just trying to make the files parseable rather than passing. Currently, doctest aborts out on the files I fixed without even attemptin

[issue15939] make *.rst files in Doc/ parseable by doctest

Ezio Melotti added the comment: > A way to do it could be to register new doctest directives that skip > the marked test based on the value of sys.platform. That can be done for 3.4+ only though. > If we remove the directives, we lose that information and won't > be able to do it anymore. It a

[issue15939] make *.rst files in Doc/ parseable by doctest

Chris Jerdonek added the comment: > Either there's another way to run those tests on selected platforms that can > be used instead A way to do it could be to register new doctest directives that skip the marked test based on the value of sys.platform. If we remove the directives, we lose tha

[issue15939] make *.rst files in Doc/ parseable by doctest

Ezio Melotti added the comment: The attached patch fixes the doctests in Doc/library/ctypes.rst. -- stage: -> patch review versions: +Python 3.4 Added file: http://bugs.python.org/file27529/issue15939-ctypes.diff ___ Python tracker

[issue15939] make *.rst files in Doc/ parseable by doctest

Ezio Melotti added the comment: If they don't work I see no reasons to leave them there. Either there's another way to run those tests on selected platforms that can be used instead, of if there's no way the tests should just be skipped. -- ___ Pytho

[issue15939] make *.rst files in Doc/ parseable by doctest

Chris Jerdonek added the comment: My opinion on the "+LINUX" and "+WINDOWS" doctest directives in Doc/library/ctypes.rst is simply to leave them alone for now. We can make those errors go away in code when running doctest by adding no-op calls to doctest.register_optionflag() as below: +doct

[issue15939] make *.rst files in Doc/ parseable by doctest

Changes by Chris Jerdonek : -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue15939] make *.rst files in Doc/ parseable by doctest

Changes by Chris Jerdonek : Added file: http://bugs.python.org/file27186/issue-15939-1.patch ___ Python tracker ___ ___ Python-bugs-list maili

[issue15939] make *.rst files in Doc/ parseable by doctest

Changes by Chris Jerdonek : Removed file: http://bugs.python.org/file27185/issue-15935-1.patch ___ Python tracker ___ ___ Python-bugs-list mai

[issue15939] make *.rst files in Doc/ parseable by doctest

Chris Jerdonek added the comment: The attached patch addresses all but Doc/library/ctypes.rst. See the following python-dev e-mail for a question about how best to handle that case: http://mail.python.org/pipermail/python-dev/2012-September/121721.html -- keywords: +patch Added file:

[issue15939] make *.rst files in Doc/ parseable by doctest

New submission from Chris Jerdonek: Currently, when trying to parse the *.rst files in the Doc/ folder (i.e. not actually running them but simply generating unittest.TestCase instances from them by passing them to doctest.DocFileSuite()), five files yield errors. This issue is to make it so th