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
Include contrib module in installed package #5
Conversation
👍 |
version bump and changelog entry? |
I was gonna retract my statement, but it is on YolaPI. So it should still need the version bump. |
Yeah, I usually like to do those in a separate pull, but this change is all about the released package, so I'm going to add it to this one. Stand by... |
Bumped. Can I get a new thumb? |
👍 |
Include contrib module in installed package
Yeah, some people think it should be another pull, and some people think version bumps and changelog changes should happen in master. Generally our client libraries get one pull of changes per version bump, so I'm not against them going in the same pull. I should've commented saying that it's okay if you were gonna do it in another PR or somewhere else. |
I don't think we want a global Otherwise what happens if two libraries ship a |
It is |
Oops, yeah. My CHANGELOG entry is wrong. I'll fix it. |
See conversation that begins here: #5 (comment)
In that case, why did you need to switch to find_packages? |
From https://docs.python.org/2/distutils/setupscript.html#listing-whole-packages
I've read this like 4 times, and I'm still not sure my interpretation is correct. If I understand things correctly Justin made this change because |
Right, I always forget about that. This is why |
I remember going through this confusion with healthcheck too. On Wed, Mar 4, 2015 at 9:53 AM, Stefano Rivera notifications@github.com
|
See https://github.com/yola/yolacom/pull/1775#issuecomment-76513787