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 Jan 21, 2020. It is now read-only.
After installation via Package Manager I can not access any Pipenv commands. The Console shows me the following messages:
Package Control: The dependency 'requests' is not currently installed; installing...
Package Control: The dependency 'requests' has successfully been installed or updated
Package Control: The dependency 'parse' is not currently installed; installing...
Package Control: The dependency 'parse' is not available
Package Control: The dependency 'parse' could not be installed or updated
It seems the "parse" dependency can not be found. Is this a bug or is there a workaround I am not aware of?
The text was updated successfully, but these errors were encountered:
Looking at the package, it has a dependencies.json which sublime plugins can use to specify which other external dependencies their package has and sublime will install them (from package control). Request exists, but parse does not.
Looks like @kennethreitz actaully bundled the source for these two dependncies in with the source in a vendor folder, along with some others, and was using them instead.
So, all that needs doing is to delete the dependencies.json. I forked the repository and deleted the dependencies.json added my own repository to sublime and installed the package. pipenv doesn't show up in the PATH that sublime sees currently, for myself, but that's a different issue, the package is installed and commands are available.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After installation via Package Manager I can not access any Pipenv commands. The Console shows me the following messages:
It seems the "parse" dependency can not be found. Is this a bug or is there a workaround I am not aware of?
The text was updated successfully, but these errors were encountered: