On 8/10/07, Nick Coghlan <[EMAIL PROTECTED]> wrote: > Guido van Rossum wrote: > > If you really need to step through the Python code, you can just > > sabotage the loading of the non-Python version, e.g. remove or rename > > the .so or .dll file temporarily. > > > > I wonder about the usefulness of this debugging though -- if you're > > debugging something that requires you to step through the C code, how > > do you know that the same bug is present in the Python code you're > > stepping through instead? Otherwise (if you're debugging a bug in your > > own program) I'm not sure I see how stepping through the I/O library > > is helpful. > > > > Sounds like what you're really after is *understanding* how the I/O > > library works. For that, perhaps reading the docs and then reading the > > source code would be more effective. > > However we select between Python and native module versions, the build > bots need be set up to run the modules both ways (with and without C > optimisation). >
Part of Alexandre's SoC work is to come up with a mechanism to do this. -Brett _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
