Repository navigation
Expanding Pipenv should refresh the children #782
Description
Activity
great idea!
Reacted by TylerLeonhardtThis should probably apply to most if not all of these different tree items. Not just pipenv
Reacted by Eleanor Boyd- added a commit that references this issue
on Sep 8, 2025 ok so this requires adding a file watching to the path where pipenv create venvs (which is not in the project). Going to leave this as a feature request and I can implement it if enough people have interest in the pipenv refresh action.
- addedfeature-requestRequest for new features or functionalityRequest for new features or functionality
on Sep 8, 2025 Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.
For this one, we should detect FS events from
pipenvlocations to auto-refresh. This is something we already do forconda.why not listen to:
and then refresh? This would work for all the items in the tree
That is a good one to try. But, then users have to collapse and expand to get refresh. But we could support that.
Also given the way we have it setup right now, it gets stuck in an endless loop if I attempt to trigger a refresh on expand. Refresh cause a re-load of the view so it just keeps calling itself. Would have to make some design changes to stop this from occurring
- added a commit that references this issue
on Oct 23, 2025 - locked as resolved and limited conversation to collaborators
on Apr 25, 2026
Testing #776
pipenv install pytestIf I manually refresh the view, then it shows up. We should refresh on expansion.