Skip to content
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

chore: update MANIFEST.in to reflect changes to filenames #438

Merged
merged 1 commit into from
Jun 1, 2017

Conversation

mrterry
Copy link
Contributor

@mrterry mrterry commented Jun 1, 2017

Looks like the .rst files got converted to .md, but MANIFEST.in wasn't
updated. This also fixes the sdist, since setup.py expects README.md &
CONTRIBUTING.md to be in the source tarball.

Closes #437

@bbangert
Copy link
Member

bbangert commented Jun 1, 2017

Argh! Thanks! Can you update the commit message per the CONTRIBUTING doc?

@mrterry mrterry changed the title Update MANIFEST.in to reflect changes to filenames chore: Update MANIFEST.in to reflect changes to filenames Jun 1, 2017
@mrterry mrterry changed the title chore: Update MANIFEST.in to reflect changes to filenames chore: update MANIFEST.in to reflect changes to filenames Jun 1, 2017
@mrterry
Copy link
Contributor Author

mrterry commented Jun 1, 2017

@bbangert I think it follows the style guide now. Please let me know if i misinterpreted something.

@bbangert
Copy link
Member

bbangert commented Jun 1, 2017

Oh, the commit itself needs to be updated, ie:
7d5d59c

So that it indicates that it closes it inside the PR (the changelog tool will auto-link everything together). The easiest way to change it is to amend your commit and just change the message with 'git commit --amend', then force push to override the existing one.

Sorry about the hassle!

Looks like the .rst files got converted to .md, but MANIFEST.in wasn't
updated.  This also fixes the sdist, since setup.py expects README.md &
CONTRIBUTING.md to be in the source tarball.

closes python-zk#437
@mrterry
Copy link
Contributor Author

mrterry commented Jun 1, 2017

no worries. everybody has a slightly different process. please excuse the thrashing.

@bbangert
Copy link
Member

bbangert commented Jun 1, 2017

Looks great, thanks!

@bbangert bbangert merged commit 8d1f27a into python-zk:master Jun 1, 2017
@jasonyzhang
Copy link

Will the fix be reflected in the tarball on pypi?

@bbangert
Copy link
Member

bbangert commented Jun 1, 2017

Yes, I'm pushing a new tag for 2.3.1 that should be uploaded to pypi once tests pass.

@jasonyzhang
Copy link

Thanks!

@bbangert
Copy link
Member

bbangert commented Jun 1, 2017

Looks like 2.3.1 has been released, let me know if there's any other issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

kazoo 2.3 source tarball does not include README
3 participants