Update package name in MANIFEST.in #11
Merged
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
try -> trypackage. The incorrect package/folder name was causing installations to not correctly grab script.template, meaning that the "--editor" flag would not work because script.template could not be found.
|
Good catch 🎉 ! Thanks 🍻 |
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.
from
trytotrypackage. It looks like the package name change was introduced in edf0430, but MANIFEST.in didn't get updated.The incorrect package/folder name was causing the
--editorflag to fail because installations didn't bundletrypackage/script.templateHope this helps, let me know if there's anything else you would like me to do!