rather than _with_, Python.
>
> A more appropriate forum is probably the Python list
> (python-l...@python.org), about which you can discover more details at
> Python-list Info Page.
>
> Kind regards,
> Steve Holden
>
>
> On Thu, Jun 20, 2019 at 3:40 AM Ed Peschko wr
all,
I'm writing a function meant to print out the context of a given
function call when executed - for example:
1. def main():
2.
3. _st = stack_trace_closure("/path/to/log")
4. _st()
5. _st()
would print out
/path/to/file.py:4
/path/to/file.py:5
for each line when executed. Basic ide
Steve,
thanks for the response, and yes, I've experimented with reverse
debugging, and yes for the reasons specified in that article you gave
it isn't really practical with anything but small projects because of
the massive amounts of memory usage.
But that's really not what I'm asking for here.
all,
I was debugging a very long script that I was not all that familiar
with, and I was doing my familiar routine of being very careful in
evaluating expressions to make sure that I didn't hit such statements
as:
TypeError: unsupported operand type(s) for +: 'int' and 'str'
anyways the script h
ssion on bugs.python.org about the precise
> specification of \G for Python. OTOH I expect that most core devs won't find
> this a very interesting problem (Python relies on regexes for parsing a lot
> less than Perl does).
>
> Good luck!
>
> On Thu, Oct 26, 2017 at 11:03 PM, E
All,
perl has a regex assertion (\G) that allows multiple-match regular
expressions to be able to use the position of the last match. Perl's
documentation puts it this way:
\G Match only at pos() (e.g. at the end-of-match position of prior m//g)
Anyways, this is exceedingly powerful for matc
