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 }}
Repository navigation
Support debugging with interperter arguments (experimental debugger) #886
Brett Cannon (@brettcannon)
Considering the fact that we've never had this, and the fact that we don't support this when running other tools within the extension, I'd say we need to move this well past the March milestone.
I don't see the point in adding support for this if:
We don't already support this (there has been no request for such a feature, none that I can remember)
To help manage our issues and to better communicate what the team plans to work on we are closing issues that we don't plan to work on but would accept a pull request from a volunteer for. To be clear, closing this issue does not mean we won't consider a pull request for this enhancement as outlined in our contributing guide, just that the development team has no plans to work on it themselves.
Activity
DonJayamanne commentedon Mar 5, 2018
Brett Cannon (@brettcannon)
Considering the fact that we've never had this, and the fact that we don't support this when running other tools within the extension, I'd say we need to move this well past the March milestone.
I don't see the point in adding support for this if:
What do you think?
brettcannon commentedon Mar 5, 2018
I agree. I just dropped it from the milestone.
brettcannon commentedon Sep 20, 2018
To help manage our issues and to better communicate what the team plans to work on we are closing issues that we don't plan to work on but would accept a pull request from a volunteer for. To be clear, closing this issue does not mean we won't consider a pull request for this enhancement as outlined in our contributing guide, just that the development team has no plans to work on it themselves.