Re: zope.testing.testrunner.debug.post_mortem and try/finally
Marius Gedminas <[email protected]>
| Newsgroups | gmane.comp.web.zope.devel |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Dec 02, 2009 at 01:36:37PM -0500, Benji York wrote:
> Here's another idea: a testrunner option that takes a file name and line
> number and inserts a breakpoint at that position. That way you can get
> the same effect as editing the code without actually having to do so.
Is that possible? I once spent hours studying pdb docs and found no way
to set a breakpoint in advance, without modifying the source file in
question, and without having the user to do manual interaction at the
beginning.
The closest that I can come is
import pdb
dbg = pdb.Pdb()
dbg.set_break(filename, lineno)
dbg.runcall(entry_point)
but this breaks into the pdb prompt at once, without waiting for the
breakpoint to get triggered, and I have to manually 'c' to get unstuck.
What am I missing?
Marius Gedminas
--
http://pov.lt/ -- Zope 3 consulting and development
_______________________________________________
Zope-Dev maillist - [email protected]
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
signature.asc
(application/pgp-signature, 191 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFLFuTLkVdEXeem148RAqJ9AJ0ULNC891YkvbUdiCiILk48Wwwv7gCfQfsP EU8KNwdR2TKkbkpwOfIhiFY= =N6cO -----END PGP SIGNATURE-----