Python 3.11 support in smoke tests

[RobPasMue]

As title says: including Python 3.11 in smoke tests and package build stages as an experimental stage (i.e. if it fails, it won't compromise the workflow)

[germa89]

Honestly, I don't like the idea of having red cross in the CI if that implies "enforcing" the merge.

I'm going to wait a bit in PyMAPDL for the moment.

[RobPasMue]

Honestly, I don't like the idea of having red cross in the CI if that implies "enforcing" the merge.

I'm going to wait a bit in PyMAPDL for the moment.

It's not enforcing. For example, as soon as 2 people approve it, you will get the green box. It's just that some stages (which are categorized as experimental and are not required), fail in the workflow. I know it's not the cleanest way of having a workflow but it's the only easy way right now (apart from setting a different workflow that runs on a scheduled basis and tries out Python 3.11, e.g. every week)...

Honestly, I kind of prefer that last idea hahaha

[germa89]

Honestly, I kind of prefer that last idea hahaha

I think I prefer it too..... another completely (non-mandatory) workflow for running python 3.11. I could do that in PyMAPDL. Thank you!

[germa89]

Look good to me. Interesting use of include and the matrix variable outside of the matrix scope.

[RobPasMue]

@germa89 specific non-mandatory workflow implemented that runs every week and tries to build the package's wheelhouse and some minor smoke test. Maybe you can reuse it =) I think this way everything is more simple. Once this workflow starts working properly we can adapt the main workflow.