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.

Sign up for GitHub

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

Jump to bottom

simplify pyenchant requirement #3805

Merged
merged 1 commit into from
Jul 21, 2017
Merged

simplify pyenchant requirement #3805

merged 1 commit into from
Jul 21, 2017

Conversation

alex
Copy link
Member

@alex alex commented Jul 21, 2017

No description provided.

reaperhulk
reaperhulk approved these changes Jul 21, 2017
View reviewed changes
Copy link
Member

@reaperhulk reaperhulk left a comment

Choose a reason for hiding this comment

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

I guess making it be 1.6.11+ won't matter since our packagers probably don't care about docs testing?

@alex
Copy link
Member Author

alex commented Jul 21, 2017

I don't think any of them do. And also if they're shipping the very latest of cryptography, it shouldn't be a problem to do the same for pyenchant :-)

@reaperhulk reaperhulk merged commit 0a8bdff into master Jul 21, 2017
@reaperhulk reaperhulk deleted the alex-patch-2 branch July 21, 2017 17:57
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@reaperhulk reaperhulk reaperhulk approved these changes

Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@alex @reaperhulk