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

Stop installing terryfy. #99

Merged
merged 1 commit into from
Oct 23, 2018
Merged

Stop installing terryfy. #99

merged 1 commit into from
Oct 23, 2018

Conversation

jamadden
Copy link
Member

No description provided.

Copy link
Member

@mgedmin mgedmin left a comment

Choose a reason for hiding this comment

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

LGTM once the MANIFEST.in typo is fixed

MANIFEST.in Outdated
@@ -1,3 +1,4 @@
pruny terryfy
Copy link
Member

Choose a reason for hiding this comment

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

Typo -- I think you meant prune.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yikes, how'd that happen. Thanks.

Copy link
Member Author

Choose a reason for hiding this comment

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

python setup.py sdist outputs a warning:

reading manifest template 'MANIFEST.in'
warning: manifest_maker: MANIFEST.in, line 1: unknown action 'pruny'

But check-manifest -v does not.

Copy link
Member

@mgedmin mgedmin Oct 23, 2018

Choose a reason for hiding this comment

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

Yeah, it would be good if check-manifest would syntactic validity as well -> mgedmin/check-manifest#85

packages=find_packages(),
# Make sure we don't get 'terryfy' included in wheels
# created on macOS CI
packages=find_packages(include=("BTrees",)),
Copy link
Member

Choose a reason for hiding this comment

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

This is BTW a yet another reason to prefer a src subdirectory at the project root ;)

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.

None yet

2 participants