Do we still need a maintenance release 3.3?

[FlorianWilhelm]

Right now there is an alpha version 3.3a1 release and some milestones which are 100% fullfilled. Does it make sense to release a version 3.3 or directly jump to 4.0?

[abravalheri]

I think we can release the 3.3 immediately (maybe just add the auto fix for the line endings with pre-commit?) since 4.0 seems like will take some time yet to be 100% ready

[FlorianWilhelm]

Alright, I'll work on that and prepare something it.

[FlorianWilhelm]

@abravalheri Was there an easy fix to the Windows unit tests? On the current master, I get on tests invoking putup:

stdout = 'running test\n******************************* DEPRECATED *******************************\npytest-runner is deprecated...91: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1124)\n'

[FlorianWilhelm]

Does that mean that tox is somehow caching the environments on Windows and we have to disable that cache and force it to reinstall certifi and pip every time?

[abravalheri]

I think it might be some optimisation of the pytest virtualenv plugin we are using in the master to create the virtualenvs.... I think last time I fixed this issue with this particular test file what I did is to stop relying on the plugin and started either avoiding the virtualenvs or using the venv extension in v4.

[abravalheri]

Hi Florian, I am curious, have you managed to solve the SSL error this time? If it just happens for Windows in v3.3 I would be happy to skip the tests, given it is clearly not a problem with our main code...

[FlorianWilhelm]

Yes, I solved it by backporting some of your code from the 4.0.x branch, mainly tests/systems/helpers.py. It just seems as if under Windows tox somehow breaks out of the virtual environment in some cases and your code fixes this by explicitly calling the right interpreter and settings the env variables. It's unfortunate that we need so much boilerplate code to run unit tests but on the other hand, fixing these problems upstream would take so much longer.

[abravalheri]

That should be fine. I saw you also added a few env vars. Hopefully it will take time until we see another SSL error on windows again.

[abravalheri]

🥳 Thank you very much @FlorianWilhelm for working on v3.3 and the automatic release mechanism via github actions!!