Kwankyu Lee writes: > > I understand this as practically saying that we should avoid breaking > existing doctests as much as possible and try to be consistent in new > doctests as much as possible. > > And how the new doctests would be written is determined when we actually > write the code. So how about opening one meta ticket and lots of individual > tickets for the cmp cases to tackle, and defer discussions to each ticket? > > Though I think, like Jeroen, setting forth some guiding principles outright > would be useful to start. I guess a dictator who knows very well the > coercion framework may do this...
To enable people knowing less about the whole cmp thing to help out, it might make sense to maintain a wiki page about the core issues to be aware of when porting, the main mechanisms, and perhaps links to tickets exemplifying some typical cases. Best, Johan -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
