On Thu, Jan 15, 2009 at 5:40 AM, Eric Holscher <eric.holsc...@gmail.com> wrote: > I think that if there is a plan to ever include fixtures into doctests, then > we should put transaction management into them. We should also decide on a > syntax (__fixtures__ really isn't too bad). This is mostly a bikeshed, where > if it's going to happen, we just need to decide something that works and go > with it. Otherwise we should go ahead and close #5624, and say that doctests > are only for simple cases where you are generating the objects yourself. > This means that we will internally write out doctests that require fixtures > back into unit tests, but this isn't a huge deal. > > I think we should just decide now, and stick with it. I really don't have a > preference, because I don't think that doctests should be used as > extensively as they are. I know a big reason they were used before is > because they were faster, which now a moot point. If we just say "we will > never have fixtures or transactions on doctests", then we can just be done > with it. > > 1: http://code.djangoproject.com/ticket/5624
There is two issues at work here. 1) Is #5625 a good idea? 2) Do we need to implement it right now? Regardless of the answer to (1), (2) is the more pressing concern - given that we're days away from a v1.1 feature freeze, and we're probably behind schedule as it is, now isn't the time to start with unnecessary feature creep. As far as I can tell, #5625 can be safely deferred to v1.2 without losing functionality or being boxed into a corner by #8138. Given that there isn't any urgency brought on by a need to meet v1.1 commitments, I suggest that we should defer this discussion to the next planning cycle. Russ %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
