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

python3Packages.pylint: 2.10.2 -> 2.11.1 #141107

Closed
wants to merge 3 commits into from
Closed

python3Packages.pylint: 2.10.2 -> 2.11.1 #141107

wants to merge 3 commits into from

Conversation

superherointj
Copy link
Contributor

@superherointj superherointj commented Oct 9, 2021

  • python3Packages.pylint: 2.10.2 -> 2.11.1
    • python3Packages.astroid: 2.7.3 -> 2.8.2
    • python3Packages.python-lsp-server: unlock pylint

pylint upgrade came up as a dependency of fixing spyder for Python38. As this seems a change with large effects. I'll try to avoid this. [Back to drawing board.]

@mweinelt
Copy link
Member

Pylint and astroid are already part of #141037.

@mweinelt
Copy link
Member

❯ nom-build -A python3Packages.spyder
error: python-language-server-0.36.2 not supported for interpreter python3.9

Pretty sure python-language-server still does not support python3.9 (and jedi 18.0), so the situation is bad.

@superherointj
Copy link
Contributor Author

❯ nom-build -A python3Packages.spyder
error: python-language-server-0.36.2 not supported for interpreter python3.9

Pretty sure python-language-server still does not support python3.9 (and jedi 18.0), so the situation is bad.

I was fixing it for Python 3.8.

@superherointj
Copy link
Contributor Author

Pylint and astroid are already part of #141037.

I can close this then.

@mweinelt
Copy link
Member

mweinelt commented Oct 10, 2021

You can try to fix it based on python-unstable if you like, but it's only going to be open for a few more hours before it hits staging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants