-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Including non-python files to package #223
Conversation
fixes #127 * Add Project.include_directory method * Include directories in distutils plugin * Add tests for Project._manifest_include_directory
Including non-python files to package
This doesn't add the files to the |
cc @sdomme |
cc @michikuehne |
@esc isn't it enough to have a recursive include in the manifest? According to the docs this will add the folder to the tarball or whatever |
No it isn't, this will only add the files to the tarball. When I install something with pip, however this downloads the tarball and then executes the setup.py contained within. Thus, with the current implementation, the files are in the tarball, but they are then not installed... I mean, it is fine if this is the intended purpose, but I don't yet see a use case for this. |
@glujan what was the intent of this feature? |
I didn't need installing those extra files at that time of writing but also I will write a patch for it.
|
hey, is this still broken? I need to deploy package resources. |
If it is, what is the current best way to ship resources files? |
No description provided.