seems like #2370 was too short-sighted as
We'll need to check out
- How this affects our building process
- How we can reasonably protect our users from install problems. Mind you, installation problems of 3rd party deps is not fully our problem, but if the majority of our users can't install it, then our package is worthless.
One could just pin cryptography to < 3.4 for starters and just wait a bit until the dust settles …
seems like #2370 was too short-sighted as
setup.pyapparently fails as for some reason this tried to build cryptography from sources? At least on RTDWe'll need to check out
One could just pin cryptography to < 3.4 for starters and just wait a bit until the dust settles …