You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.
It's more a question of what is a module, in general. Our existing ptvsd implementation treats any .py file (more generally, co_filename of the code object) as a module - and only uses sys.modules as a means to populate the initial list, for the lack of better alternatives. If we're changing to tracking sys.modules exclusively, that would be a user-visible semantics change.
OTOH, with existing VS debugger as a baseline, we don't need to accurately track modules as they get loaded (because it doesn't). We just need to make sure that everything that we report that has an associated module ID - in particular, stack frames - has the corresponding module entry. This means that one possible implementation is to do no tracking at all, but instead report module as loaded when it's first seen in a stack trace, which is probably much easier.
Generate moduleEvent on import, reload, and del.
The text was updated successfully, but these errors were encountered: