Skip to content

make pylint dev requirement not install on < 3.8 #4885

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

Merged
merged 2 commits into from
Apr 17, 2019

Conversation

scbedd
Copy link
Member

@scbedd scbedd commented Apr 17, 2019

Python 3.8alphaX is failing to run the tests due to the following issue

The reason typed_ast is failing right now is because 3.8alpha removed pgen headers that the package leverages to pull out information used by pylint. (dependency path is pylint -> asteroid -> typed-ast)

This currently only affects servicebus because servicebus has an explicit dev dependency on pylint. If pylint was active on the repo in general, we'd end up needing to disable the 3.8 python until we come up with a way to deal with this.

@scbedd scbedd requested a review from annatisch as a code owner April 17, 2019 18:03
@adxsdk6
Copy link

adxsdk6 commented Apr 17, 2019

Can one of the admins verify this patch?

1 similar comment
@adxsdk6
Copy link

adxsdk6 commented Apr 17, 2019

Can one of the admins verify this patch?

@scbedd scbedd changed the title make pylint dev requirement not install on <= 3.8 make pylint dev requirement not install on < 3.8 Apr 17, 2019
Copy link
Member

@annatisch annatisch left a comment

Choose a reason for hiding this comment

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

Looks good to me - is anything (travis or devops) actually running this pylint pass at the moment?

@scbedd
Copy link
Member Author

scbedd commented Apr 17, 2019

Looks good to me - is anything (travis or devops) actually running this pylint pass at the moment?

Not that I'm aware of! I've got an item on the backlog to make it happen. However, for local dev, I feel that it's appropriate to be there. I'm glad you already had this, as otherwise we wouldn't even be aware that this package would run into this error. As it stands, at least we know about it now :)

@scbedd scbedd merged commit dfbc340 into Azure:master Apr 17, 2019
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