Skip to content

Conversation

@mlhamel
Copy link
Contributor

@mlhamel mlhamel commented Nov 19, 2018

Description

When using mypy, to better deal with typing from dependent packages we need to "advertise" our support of typing. As it it describe at https://www.python.org/dev/peps/pep-0561/#packaging-type-information, if you want mypy to check for correct typing of dependant package and be able to ignore specific ones that don't support it, you need to add a specific marker in your setup.py.

How does this PR work?

This PR is adding the typing marker to the setup.py

@mlhamel mlhamel force-pushed the include-typing-marker-for-mypy branch from 1879773 to 5fc736d Compare November 19, 2018 20:25
@@ -1,4 +1,4 @@
pycodestyle==2.3.1
pycodestyle~=2.4
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm not sure I understand how it was working before cause it seems version 1.4.3 of autopep did depend of this (hhatto/autopep8@9583280#diff-2eeaed663bd0d25b7e608891384b7298)

Would it be better to stick to autopep8 <= 1.4.3 ?

Copy link
Member

Choose a reason for hiding this comment

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

Looks fine: I didn't see anything major going from 2.3 to 2.4.
It's impossible to be sure that no projects will tumble on that, but I think we should be going forward, not backward.
The minor version should be bumped.

@mlhamel mlhamel requested review from cfournie and pior November 19, 2018 20:38
Copy link
Member

@pior pior left a comment

Choose a reason for hiding this comment

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

LGTM

@mlhamel mlhamel merged commit 39c5177 into master Nov 20, 2018
@mlhamel mlhamel deleted the include-typing-marker-for-mypy branch November 20, 2018 20:21
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.

3 participants