René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"expose globals in bpdb debugging","articleBody":"I love bpython!\r\n\r\nI haven't dived into the codebase too deeply, but would it be easy to expose the globals when performing post-mortem debugging?  Right now I can only access the locals in the bpython debugger - to interact with the globals (for instance, debugging functions I might have defined in the same module as the function the pm debugging is in), I have to drop out of bpdb, losing all of it's benefits.\r\n\r\n```python\r\ndef debug():\r\n    print('global debugging!')\r\n\r\ndef broken():\r\n    def internal_debug():\r\n        print('local debugging!')\r\n    do_bad_thing_here()  # pm debugging drops me here\r\n```\r\n\r\nin the above example, I can do `\u003e\u003e\u003e intern\u003ctab\u003e`, and get `internal_debug` to complete and get its help, and run it, but if I try to do `\u003e\u003e\u003e debug()\u003center\u003e` I get an error about the name \"debug\" not being defined.\r\n\r\nI can do `\u003e\u003e\u003e exit()` to get back to `(BPdb) ` and then do `(BPdb) debug()\u003center\u003e` and `debug` is available and executes correctly.\r\n\r\nI've found code that looks like it's only exposing the locals (https://github.com/bpython/bpython/blob/2349722c9ce9b6f9d7ad5f411a1b5d2859a6b116/bpdb/debugger.py#L47), but I'm not sure how easy it is to make it expose the globals, too.  \r\n\r\nI'll circle back and investigate more, but on the chance someone else knows better or gets to a PR first, I figured I'd post this issue.","author":{"url":"https://github.com/toejough","@type":"Person","name":"toejough"},"datePublished":"2017-11-01T14:48:22.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/713/bpython/issues/713"}