Add Python 3.11-dev to Github actions

[Pierre-Sassoulas]

Current problem

Seems like tomllib has been accepted and merged python/cpython#31498 but not yet released to any of the images available on Github.

Next release is expected on 2022-04-05 so we'll need to wait a bit.

Desired solution

Add 3.11-dev when github actions are up to date and released.

Additional context

#5919 (comment)

[cdce8p]

@HacKanCuBa This doesn't look like a pylint / astroid issue. I've I had to guess, maybe take a look at pydantic_factories?

Besides, I was able to set a Python 3.11.0a7 environment and run both pylint and pytest. We just have a lot a failing tests at the moment. IMO it doesn't really make sense to fix them atm, probably best to wait for the first beta release next month.

[HacKanCuBa]

Oh my, I posted it in the wrong project xD
Yes, it is indeed a Pydantic issue, sorry :P I was a bit sleepy, I miss-typed :P

[ssbarnea]

To be honest I do think that it would highly desirable to enable py311 pipeline. It already in beta, I can easily make a PR if that is ok.

[DanielNoord]

@ssbarnea Agreed! However, we can't until we release a new version of astroid.

We're almost done with the release of pylint 2.14 which will probably be the last version without support for 3.11.
After that, I (and probably other maintainers) will focus on getting astroid 2.12 releasable, which includes support for 3.11.

[ssbarnea]

I just discovered something that looks like serious problem E0611: No name 'path' in module 'os' (no-name-in-module)... when obviously os.path did not disappear.

[DanielNoord]

I just discovered something that looks like serious problem E0611: No name 'path' in module 'os' (no-name-in-module)... when obviously os.path did not disappear.

Is this with astroid on main? Or only with 2.12?

[ssbarnea]

Apparently this happens only with astroid stable (2.11.5) but when installed from its main branch pylint worked. Maybe it worth making a 2.12 prerelease of it and use that as conditional dependency when python is 3.11 ? It might be an easy way to slowly enable 3.11 compatibility.

[DanielNoord]

Apparently this happens only with astroid stable (2.11.5) but when installed from its main branch pylint worked. Maybe it worth making a 2.12 prerelease of it and use that as conditional dependency when python is 3.11 ? It might be an easy way to slowly enable 3.11 compatibility.

I think we're nearing the release of 2.12 anyway. There are no real blockers in terms of PRs, just a number of PRs we/I would like to get in but haven't gotten around to reviewing. The issue with astroid is that most of the current maintainers of pylint are not as experienced with the internals of astroid so reviewing PRs and iterating on them takes considerably longer.
We're getting more and more experienced, but it takes some time.

[jacobtylerwalls]

@ssbarnea thanks for testing! Do you have a reproducer for the issue with os.path? If so, could you open an issue on the astroid repository?

but when installed from its main branch pylint worked.

Installing pylint will pin astroid to a specific version, not stable. You can install astroid stable after installing pylint to make sure you are testing with astroid main branch.

[ssbarnea]

Using astroid from master made pylint work, so I will wait for astroid to be released. If the issue does not happen on astroid@master, I doubt there is a good reason to file a bug with astroid.

[jacobtylerwalls]

Apparently this happens only with astroid stable (2.11.5) but when installed from its main branch pylint worked.

Sorry, I misunderstood your post. I thought you meant pylint's main branch. Thanks for clarifying. 👍🏻