python < 3.12 causes issues with other poetry projects, can you use < 4.0 about sceptre HOT 3 CLOSED

If you want to avoid using virtual environments, I'd suggest using pipx... which is used for installing tools (like Sceptre) into isolated, independent virtual environments. It should make it a lot easier to install Sceptre for use without mixing it with other environments.

from sceptre.

Hi @pc-fmarin, on this I think we'll have to say that we cannot and will not do this. I don't really see the point in allowing all future minor versions of Python... such would assume there won't be any breaking or incompatible changes between now and Python 4. History proves that assumption to be pure hubris.

For the sake of stability of Sceptre, we always make sure to explicitly test and certify that Sceptre is compatible with each Python version. Even upgrading to support Python 3.10 required us to make changes to core Sceptre code in order for it not to be broken. I do not foresee supporting 3.12 to be any different. While some libraries make sense to pin up to the next major version, we cannot do this with the Python version itself.

I'll also note that Sceptre will perform most at its most stable if it is installed into its own virtual environment as a standalone application, not mixed in with your application dependencies. This is not out of step with other IaC tools. For example, AWS SAM CLI recommends that it be installed in its own virtual environment rather than pip-installed into the same environment as other dependencies. I would recommend that you establish a separate virtual environment for Sceptre and then there won't be any version incompatibilities. Alternatively, (just from a pure application architecture best-practices perspective), I'd encourage you to not use >3.9, <4.0 as your python dependency.

from sceptre.

FWIW, we just ran into deploy failures (first time that sceptre >= 4.2.0 was picked up by our pipeline):

ERROR: botocore 1.31.1 has requirement urllib3<1.27,>=1.25.4, but you'll have urllib3 2.0.3 which is incompatible.

After seeing this issue, tried with <4.2.0, and that resolved it. Suspecting the poetry update? I don't disagree with the suggestion to use virtual environments, but we are not python devs...and trying to figure out this stuff is more difficult as a result. :(

from sceptre.