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)

[HacKanCuBa]

I can say it currently doesn't work with latest 3.11.0a7: (unrelated, see below)

ImportError while importing test module '/builds/hackancuba/asgi-signing-middleware/asgi_signing_middleware/tests/tests_cookie_starlite.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/local/lib/python3.11/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
asgi_signing_middleware/tests/tests_cookie_starlite.py:26: in <module>
    from starlite import Request
.cache/poetry/virtualenvs/asgi-signing-middleware-4gCN4nBn-py3.11/lib/python3.11/site-packages/starlite/__init__.py:3: in <module>
    from .app import Starlite
.cache/poetry/virtualenvs/asgi-signing-middleware-4gCN4nBn-py3.11/lib/python3.11/site-packages/starlite/app.py:19: in <module>
    from starlite.asgi import StarliteASGIRouter
.cache/poetry/virtualenvs/asgi-signing-middleware-4gCN4nBn-py3.11/lib/python3.11/site-packages/starlite/asgi.py:10: in <module>
    from starlite.routes import ASGIRoute, HTTPRoute
.cache/poetry/virtualenvs/asgi-signing-middleware-4gCN4nBn-py3.11/lib/python3.11/site-packages/starlite/routes.py:18: in <module>
    from starlite.controller import Controller
.cache/poetry/virtualenvs/asgi-signing-middleware-4gCN4nBn-py3.11/lib/python3.11/site-packages/starlite/controller.py:6: in <module>
    from starlite.handlers import BaseRouteHandler
.cache/poetry/virtualenvs/asgi-signing-middleware-4gCN4nBn-py3.11/lib/python3.11/site-packages/starlite/handlers/__init__.py:1: in <module>
    from .asgi import ASGIRouteHandler, asgi
.cache/poetry/virtualenvs/asgi-signing-middleware-4gCN4nBn-py3.11/lib/python3.11/site-packages/starlite/handlers/asgi.py:8: in <module>
    from starlite.handlers.base import BaseRouteHandler
.cache/poetry/virtualenvs/asgi-signing-middleware-4gCN4nBn-py3.11/lib/python3.11/site-packages/starlite/handlers/base.py:21: in <module>
    from starlite.provide import Provide
.cache/poetry/virtualenvs/asgi-signing-middleware-4gCN4nBn-py3.11/lib/python3.11/site-packages/starlite/provide.py:10: in <module>
    from starlite.signature import SignatureModel
.cache/poetry/virtualenvs/asgi-signing-middleware-4gCN4nBn-py3.11/lib/python3.11/site-packages/starlite/signature.py:8: in <module>
    from pydantic_factories import ModelFactory
.cache/poetry/virtualenvs/asgi-signing-middleware-4gCN4nBn-py3.11/lib/python3.11/site-packages/pydantic_factories/__init__.py:3: in <module>
    from .extensions import (
.cache/poetry/virtualenvs/asgi-signing-middleware-4gCN4nBn-py3.11/lib/python3.11/site-packages/pydantic_factories/extensions/__init__.py:2: in <module>
    from .beanie_odm import BeanieDocumentFactory, BeaniePersistenceHandler
.cache/poetry/virtualenvs/asgi-signing-middleware-4gCN4nBn-py3.11/lib/python3.11/site-packages/pydantic_factories/extensions/beanie_odm.py:6: in <module>
    from pydantic_factories.factory import ModelFactory
.cache/poetry/virtualenvs/asgi-signing-middleware-4gCN4nBn-py3.11/lib/python3.11/site-packages/pydantic_factories/factory.py:93: in <module>
    from pydantic_factories.constraints.strings import (
.cache/poetry/virtualenvs/asgi-signing-middleware-4gCN4nBn-py3.11/lib/python3.11/site-packages/pydantic_factories/constraints/strings.py:3: in <module>
    from exrex import getone  # pylint: disable=import-error
.cache/poetry/virtualenvs/asgi-signing-middleware-4gCN4nBn-py3.11/bin/exrex.py:25: in <module>
    from re import sre_parse, U
E   ImportError: cannot import name 'sre_parse' from 're' (/usr/local/lib/python3.11/re/__init__.py)

👉 Full trace and context

[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