[issue25682] __package__ not set to None under pdb in Python 3

Irit Katriel added the comment: Thanks Keith. Closing and we can look into it if someone else has an issue. -- stage: -> resolved status: open -> closed ___ Python tracker __

[issue25682] __package__ not set to None under pdb in Python 3

Keith Prussing added the comment: Caveat: It's been a few years so I'm trying to recall what I was doing at the time and what my original problem was. I understand and expect pdb to populate __package__ and __main__ to be what it expects when run as a module with -m. However, I believe my e

[issue25682] __package__ not set to None under pdb in Python 3

Irit Katriel added the comment: pdb imports the module with importlib, and populates __main__ with data from its spec, including the package. This doesn't contradict the fact that the python command line can have only one "-m". What is the actual problem here? -- nosy: +iritkatriel

[issue25682] __package__ not set to None under pdb in Python 3

Change by Brett Cannon : -- components: +Library (Lib) -Extension Modules nosy: -brett.cannon ___ Python tracker ___ ___ Python-bug

[issue25682] __package__ not set to None under pdb in Python 3

Changes by SilentGhost : -- nosy: +brett.cannon, eric.snow, ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue25682] __package__ not set to None under pdb in Python 3

New submission from Keith Prussing: When a module is run under pdb in Python 3, __package__ is set to the empty string instead of None. The attached minimum working example depicts this behavior. The results are summarized in the following table. === == == Command