Message71630
I once fell into the same issue, but the patch should modify
_PyObject_Dump(), around the call to PyObject_Print.
string_print() is not the only function called by _PyObject_Dump, by far...
And beware that many people routinely run python in "debug mode" outside
gdb, for example during development.
That's why it's better to modify _PyObject_Dump only; we can be sure
that it only affects a debugger session. |
|
Date |
User |
Action |
Args |
2008-08-21 12:56:03 | amaury.forgeotdarc | set | recipients:
+ amaury.forgeotdarc, vstinner |
2008-08-21 12:56:03 | amaury.forgeotdarc | set | messageid: <1219323363.31.0.333373176417.issue3632@psf.upfronthosting.co.za> |
2008-08-21 12:56:02 | amaury.forgeotdarc | link | issue3632 messages |
2008-08-21 12:56:02 | amaury.forgeotdarc | create | |
|