On Wed, 2007-05-30 at 09:48 +0800, Russell Keith-Magee wrote: > On 5/30/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > > > There are some backwards-incompat > > changes between the Python 2.4 doctest.py (which is what is included in > > Django) and the Python 2.5 version. > > The version in Django isn't an _exact_ copy of Python 2.4; it has been > slightly modified to give some flexibility that is present in > unittest, but not in doctest - specifically, the nomination of the > runner and test base class to use when constructing a doctest suite.
Urgh. Okay... so I guess we should add a big comment at the top of our doctest.py to mention that. I might not be the only one in future who wonders about what is needed to make it forwards compatible with python 2.5's doctest and when I looked at the file in the past, it started out exactly the same way as the Python version (I didn't think to go back and check the old history that was accidentally lost when it was moved to it's current location, so I missed the changes that had been made). I'll add something suitably informative when I get a chance. Do you think it's worth calling our version something other than doctest.py to avoid problems? That's what we've done with _threading and _decimal -- so "import decimal" is in no way ambiguous, even if you don't remember the import order for relative imports. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
