On Thu, Feb 25, 2010 at 6:58 AM, zpcspm <[email protected]> wrote: > If I understand it right, this might be exactly the case where > coverage.py can help.
Yes. coverage.py is an important tool. I want to use it asap. I have two more thoughts re the lessons learned from the recent failure: 1. Time alone doesn't fix anything, nor does time alone prove much about bugs or their absence. 2. Proper software practices are the same regardless of their position in a release cycle. The start of a release cycle isn't a license for laziness. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" 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/leo-editor?hl=en.
