Guido van Rossum writes:
> I suggest that you move this discussion to python-ideas to ferret out
> a possible implementation and API; or to find out work-arounds.
Okay. Done.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mai
ro...@gnu.org wrote:
But the
expectation is that the programmer thinks it matches what is currently
on A that the programmer is debuggging. Can I tell for certain?
You can always find out by compiling the source and
comparing the resulting bytecode with what is currently
on A. Not that this is
On Mon, Feb 2, 2009 at 10:48 AM, wrote:
> Brett Cannon writes:
> > On Mon, Feb 2, 2009 at 00:52, Rocky Bernstein wrote:
> > > As I've mentioned, I've been re-examining from ground up the whole
> > > state of affairs in writing a debugger.
> > >
> > > One of the challenges of a debugger or a
Brett Cannon writes:
> On Mon, Feb 2, 2009 at 00:52, Rocky Bernstein wrote:
> > As I've mentioned, I've been re-examining from ground up the whole
> > state of affairs in writing a debugger.
> >
> > One of the challenges of a debugger or any source-code analysis tool
> > is verifying that th
On Mon, Feb 2, 2009 at 00:52, Rocky Bernstein wrote:
> As I've mentioned, I've been re-examining from ground up the whole
> state of affairs in writing a debugger.
>
> One of the challenges of a debugger or any source-code analysis tool
> is verifying that the source-code that the tool is reportin
As I've mentioned, I've been re-examining from ground up the whole
state of affairs in writing a debugger.
One of the challenges of a debugger or any source-code analysis tool
is verifying that the source-code that the tool is reporting on
corresponds to the compiled object under execution. (For d
