The multiple venv for different Python versions sounds exactly like what tox does
Then setup a github action that does nightly builds. Which will catch issues caused by changes that only tested against one python version or on one platform
py313 is a good version to test against cuz there were many modules removed or depreciated or APIs changed
good luck. Hope some of my advice is helpful
BFF 1: Chuck is going to be so surprised. We've hired the best caterers, cosplay theme, fireworks, yard ales, twister themed blind laser tag, there will be balloons, ball pool, athletic challenge course, fabulous entertainment from top notch talent, show girls, the wine will flow like water
BFF 2: Tell me you didn't invite that grifter, mypy
BFF 1: I ... err ... hum. Opps
mypy enters the conversation
Don't use lambda use def function instead
BFF 2: Man i hate that guy. Rains on our parade and sucks the fun out of the room (and this entire thread).
Just activate the venv and then put it out of your mind. Can activate it with either a relative or absolute path. Doesn't matter which