Allow dependencies to be installed inside a .sublime-package #1291
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
My dependency can be packed inside a `.sublime-package`, there no need to it be on the loose user packages folder. When I need it, I just import like: ```python from DependencyName.file_name import CoolClass ```
|
This isn't needed. Usually, Python packages expect to be in an unextracted way and there is no downside in having PC unextract them when installing. The only reason I could see for this is when the dependencies clutter the packages folder, in which case #800 is the proper fix. |
|
Moving then to a different folder as |
evandrocoan
added a commit
to evandrocoan/EstimatedTimeLeft
that referenced
this pull request
Dec 9, 2017
Allow dependencies to be installed inside a .sublime-package wbond/package_control#1291
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My dependency can be packed inside a
.sublime-package, there noneed to it be on the loose user packages folder. When I need it, I
just import like:
Then if I create the file
on.sublime-packageon the root of my directory, the dependency will be packaged inside a.sublime-package, instead of the default unpacked.