-
Notifications
You must be signed in to change notification settings - Fork 68
Just My Code #194
Comments
Depends on #169 |
This should be enabled using |
@int19h @karthiknadig @qubitron
|
The first approximation is what the old ptvsd did, which is: all files installed anywhere in lib or site-packages (including user-global and virtualenv) are non-user code, which is the same as "stdlib". If the latter term is confusing, I propose that we change that. Once we have feature parity, that definition can certainly be extended. There have been user asks to treat Python built-in modules separate from site-packages, mostly for the purposes of debugging self-authored packages in a "natural environment", without the overhead of disabling JMC entirely (@zooba, is that right?). But all that stuff is post-VS-stable. |
BTW, this issue only tracks the feature parity version. There's a separate item for fine-grained JMC: #207 |
Let's focus on feature parity per @int19h and focus on fine-grained control later. |
Yep. They're already assigned to milestones accordingly - this one is in VSC milestone, and fine-grained isn't in any milestone at all (i.e. post-stable). |
Completed via #467 |
An option that allows the user to:
For the purposes of this item, "standard library" is defined as every package installed into the current Python environment (i.e. including site-packages).
The text was updated successfully, but these errors were encountered: