-
-
Notifications
You must be signed in to change notification settings - Fork 140
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
.pyi files should be identified as python #51
Comments
I'm hesitant to classify them directly as python as they have quite different formatting style (for instance I wouldn't run flake8 on them). That said, they aren't classified at all yet. Would you be OK with them (for now) being classified as |
Wow, thanks for the fast response. I'm working on adding stubs to attrs, which uses pre-commit to run black to reformat python files, but
I have a solution that works for now, but I wanted to notify the authors of the various projects so that a better solution can be worked out. I'm going to go point this out over at |
for pre-commit (once hooks:
- id: black
- id: black
name: black (pyi)
types: [pyi] let me get |
here's the PR to classify |
pyi is now classified as of v1.1.3 |
thanks!
…On Tue, Jul 10, 2018 at 10:05 PM Anthony Sottile ***@***.***> wrote:
pyi is now classified as of v1.1.3
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#51 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAD3E_ToAdRA3Kluy97W5EwBvFFwNnvxks5uFYe2gaJpZM4VKek_>
.
|
.pyi files are the basis for PEP 484 static type checking, and should be identified as python files.
The text was updated successfully, but these errors were encountered: