Hi Chris, On Jan 6, 12:59 pm, Christopher Lee <[email protected]> wrote:
> If you have a list of places where files are not being closed (and > should be), please send that to me so I can fix them. I meant the temporary files generated during testing. The tempfile module does this, forgot the details but the gist of it is that they cannot always be removed manually before the program ends. But I've addressed this myself. > How are you handling this test-skipping contingency? Each test module has a get_suite() function that builds a test suite. For MySQL tests there is a utility function that detects whether mysql is properly installed. If the module is not present or if it raises access errors of some type then the mysql tests are not added to the test suite. It also reports the nature of the problem. > How are you handling the XMLRPC server test? I have not gotten to the XMLRPC test but I think for that particular test it is fine to spawn a process after all it is a standalone server. > I dislike this behavior and have > been discussing several alternatives; the main question right now is > simply the trade-off of HOW MUCH to change vs. WHEN. My preference is would be for small changes soon. By small changes I mean making a pygr.Data like class that has the same functionality as the current module. In fact it could be developed in parallel to the existing module thus minimizing the disruptions. > Presumably you would only make doctests out of tests that provide an > example of an application that a user might actually want to do in > real-life... Yes absolutely, I singled out pygrdata_test because those tests consist of multiple steps that could be used to demonstrate how to use the components. Istvan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" 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/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
