Specify package_data in setup.py (minecraft.yaml must be included). #175
Conversation
This file contains hidden or 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
pymclevel requires minecraft.yaml to be shipped, otherwise IOError: [Errno 2] No such file or directory: 'pymclevel/minecraft.yaml'
Author
|
This would presumably fix #172. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
pymclevel requires
minecraft.yamlto be shipped, otherwise we obtainThis is currently happening if installing pymclevel right from git via pip (i.e. via
$ pip install git+git://github.com/mcedit/pymclevel.git). By default, only Python files are included in the distribution build. There is a canonical mechanism for including non-Python files into the distribution build, as explained here: https://docs.python.org/2/distutils/setupscript.html#installing-package-dataI have used the
package_datamethod in order to includeminecraft.yamland the license as well as readme into the dist build. This is currently untested, but this method generally works for my packages.