Dag Sverre Seljebotn wrote: > I now have code sitting on my drive for a doctesthack directive. What it > does is work around the limitations of the doctest module by > automatically creating a global __test__ dictionary mapping descriptive > names to function and method docstrings. > > 1) Can I push it? > 2) Can I make it the default? It never does anything if a __test__ > already exists, so it should be fully backwards compatible. The only > downside I can see is a little bit of extra memory used. > > Line numbers are embedded into the test names (the keys in __dict__). > > Note: This does not solve the problem of doctest being unable to print > line numbers for class docstrings. Also the test procedure ends up > flowing a little bit different from the Python module (as each function > is a seperate testcase, and not simply part of the module test). As the > name says, it is a hack.
Now that I know what kind of problems this does *not* fix and what new problems it introduces, what about some more detail what kind of problem this actually fixes? Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
