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

Hot-fix master following release of python 3.10-rc's new version #4801

Conversation

Pierre-Sassoulas
Copy link
Member

Type of Changes

Type
βœ“ πŸ› Bug fix

Description

This is a hot fix, the real fix escape me right now.

@Pierre-Sassoulas Pierre-Sassoulas added Bug πŸͺ² Maintenance Discussion or action around maintaining pylint or the dev workflow labels Aug 4, 2021
@coveralls
Copy link

coveralls commented Aug 4, 2021

Coverage Status

Coverage remained the same at 92.587% when pulling 4039852 on Pierre-Sassoulas:fix-master-so-we-can-merge-again into a71cfe1 on PyCQA:main.

@Pierre-Sassoulas Pierre-Sassoulas added this to the 2.10.0 milestone Aug 4, 2021
@Pierre-Sassoulas Pierre-Sassoulas merged commit fbdab02 into pylint-dev:main Aug 4, 2021
@Pierre-Sassoulas Pierre-Sassoulas deleted the fix-master-so-we-can-merge-again branch August 4, 2021 18:20
@DanielNoord
Copy link
Collaborator

I wanted to fix this, but not quite sure what the original test is trying to test for.
In 3.10 you can assign types to create your own types, which is why the test is no longer emitting the warning.

@Pierre-Sassoulas
Copy link
Member Author

Yes the part that look like a type assignment in 3.10 was invalid before 3.10 and crashed in astroid <=2.6.4, see #4439

@DanielNoord
Copy link
Collaborator

So no need to change the tests to be able to also run on 3.10?

@Pierre-Sassoulas
Copy link
Member Author

Yes I think the change is ok as it is, if there was multiple use case in the functional test we'd have to separate them but there is just this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug πŸͺ² Maintenance Discussion or action around maintaining pylint or the dev workflow
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants