#2920: Putting _() into builtins causes trouble with doctests
---------------------------+------------------------------------------------
Reporter: mtredinnick | Owner: mtredinnick
Status: new | Component: Unit test system
Version: | Resolution:
Keywords: | Stage: Design decision needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------+------------------------------------------------
Comment (by mtredinnick):
Replying to [comment:4 mtredinnick]:
> (In [4486]) Revert [4485] in order to fix accidental mod_python
breakage. Refs #2920.
For reference, the problems we were seeing are in
[http://groups.google.com/group/django-
users/browse_frm/thread/efcd6737b098c164/da5e1cc2bd2eff2d?lnk=gst&q=&rnum=46#da5e1cc2bd2eff2d
this django-users thread]. They should be fixed after [4905], so we can
move onto part II of this ticket, which is removing _() from builtins.
--
Ticket URL: <http://code.djangoproject.com/ticket/2920#comment:6>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
