Skip to content

Added Manifest file#31

Merged
Tinche merged 1 commit into
Tinche:masterfrom
kszucs:manifest
Oct 21, 2017
Merged

Added Manifest file#31
Tinche merged 1 commit into
Tinche:masterfrom
kszucs:manifest

Conversation

@kszucs

@kszucs kszucs commented Oct 20, 2017

Copy link
Copy Markdown
Contributor

@Tinche Tinche merged commit d366624 into Tinche:master Oct 21, 2017
@Tinche

Tinche commented Oct 21, 2017

Copy link
Copy Markdown
Owner

Thanks! Do you need me to do a release to PyPI?

@kxepal

kxepal commented Oct 21, 2017

Copy link
Copy Markdown

The only file that should be mentioned there is LICENSE. Others are redundant and get included by default.

@kszucs

kszucs commented Oct 22, 2017

Copy link
Copy Markdown
Contributor Author

@Tinche a release would be great! Thank You!

@kszucs

kszucs commented Oct 23, 2017

Copy link
Copy Markdown
Contributor Author

@Tinche please ping me here conda-forge/staged-recipes#4192 after the release

Comment thread MANIFEST.in
recursive-include aiofiles *.py

include README.rst
include MANIFEST.in

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for a comment after merging but MANIFEST.in is not needed in the file.
Maybe it doesn't make a harm but no other project has the line IMHO.
I'm pretty sure aio-libs: aiohttp, yarl, multidict and others works pretty well.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MANIFEST.in, MANIFEST and setup.py don’t need to be in MANIFEST.in, indeed.

Comment thread MANIFEST.in
@@ -0,0 +1,6 @@
recursive-include aiofiles *.py

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The line should be removed: setuptools/distutils has a rule to include all .py files from mentioned packages.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is true.

@Tinche

Tinche commented Nov 30, 2017

Copy link
Copy Markdown
Owner

Uh, it works like it is now, so I'm not in a rush to fix it. If someone wants to submit a cleanup PR, I'll be happy to merge it in :)

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.

5 participants