On Sun, Jan 3, 2010 at 23:24, Chris Withers wrote:
> Why? What does sphinx's doctest parser do that Manuel's doctest parser
> doesn't?
The most important one is that it can match output to code blocks. The
details of what I need have been described in previous mails.
I've now added a sphinx pars
Lennart Regebro wrote:
> already wrote. For Manuel I have to make it use sphinx doctest
> parsers,
Why? What does sphinx's doctest parser do that Manuel's doctest parser
doesn't?
Chris
--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.
On Fri, Jan 1, 2010 at 22:05, Chris Withers wrote:
> I'd warrant you'll find it easier and simpler to write a customer Manuel
> plugin to do what you want, especially as most of the hard work is done
> for you already...
Nah, all I needed, at least at the moment, is to fix a bug in Sphinx
(i'll m
Lennart Regebro wrote:
> I also realized I need another option, namely to say under which
> version a particular doctest should be run. So I had a brainwave, and
> the solution to my problems is obvious: I'll write a custom doctest
> extension for Sphinx.
I'd warrant you'll find it easier and simp
I also realized I need another option, namely to say under which
version a particular doctest should be run. So I had a brainwave, and
the solution to my problems is obvious: I'll write a custom doctest
extension for Sphinx.
On Thu, Dec 31, 2009 at 13:03, Lennart Regebro wrote:
> On Thu, Dec 31,
On Thu, Dec 31, 2009 at 12:38, Chris Withers wrote:
> Not with Sphinx's hidden code blocks...
Sure, but I don't get Manuel to pick those up.
I want this to work:
.. testcode::
from setuptools import setup, find_packages
readme = open('docs/README.txt', 'rt').read()
changes = open('
Chris Withers wrote:
> Lennart Regebro wrote:
>> On Wed, Dec 30, 2009 at 16:00, Chris Withers wrote:
Scratch that, I got it to work now. Anyway, the code in question
*does* raise an exception, but I don't want that exception to be
rendered in the output, which still means Manuel doe
Lennart Regebro wrote:
> On Wed, Dec 30, 2009 at 16:00, Chris Withers wrote:
>>> Scratch that, I got it to work now. Anyway, the code in question
>>> *does* raise an exception, but I don't want that exception to be
>>> rendered in the output, which still means Manuel doesn't help me solve
>>> the
On Wed, Dec 30, 2009 at 16:00, Chris Withers wrote:
>> Scratch that, I got it to work now. Anyway, the code in question
>> *does* raise an exception, but I don't want that exception to be
>> rendered in the output, which still means Manuel doesn't help me solve
>> the problem.
>
> try except?
No,
Lennart Regebro wrote:
> On Wed, Dec 30, 2009 at 14:38, Chris Withers wrote:
>>> However, it still completely refuses to execute any codeblock stuff
>>> (or at least reports no error, even though the code is invalid). It's
>>> also not clear to me how the output of a codeblock would be tested.
>
On Wed, Dec 30, 2009 at 14:38, Chris Withers wrote:
>> However, it still completely refuses to execute any codeblock stuff
>> (or at least reports no error, even though the code is invalid). It's
>> also not clear to me how the output of a codeblock would be tested.
Scratch that, I got it to work
On Wed, Dec 30, 2009 at 14:38, Chris Withers wrote:
> What "it" are you referring to?
Well, the tests, using manuel. Although only the >>> tests.
>> However, it still completely refuses to execute any codeblock stuff
>> (or at least reports no error, even though the code is invalid). It's
>> als
Lennart Regebro wrote:
> On Wed, Dec 30, 2009 at 11:51, Chris Withers wrote:
>> Lennart Regebro wrote:
>>> So. I want either to get a normal unittest.TextTestRunner().run(suite)
>>> to include the testcode blocks, *or* I need to override the testparser
>>> for sphinx. Any recommendations for how t
On Wed, Dec 30, 2009 at 11:51, Chris Withers wrote:
> Lennart Regebro wrote:
>> So. I want either to get a normal unittest.TextTestRunner().run(suite)
>> to include the testcode blocks, *or* I need to override the testparser
>> for sphinx. Any recommendations for how to do this? Looking into how
>
Lennart Regebro wrote:
> So. I want either to get a normal unittest.TextTestRunner().run(suite)
> to include the testcode blocks, *or* I need to override the testparser
> for sphinx. Any recommendations for how to do this? Looking into how
> sphinx.ext.doctest works, I believe the first option is
>
I want a doctest like this:
>>> from __future__ import division
>>> 5/2
2.5
This doesn't work, because in doctests each line is executed
separately, so when it comes to 5/2, the __future__ import is
forgotten, and 5/2 returns 2. I could use testcode blocks, but in
testcode blocks,
16 matches
Mail list logo
