A single (but rather important) line was missed in #1292, which, if not corrected, may allow package managers to install any new releases of Zappa on Py3.7, even though all logic needed to support Py3.7 has now been removed from Zappa.
This PR is a 1-line (1-char, to be precise 🙃) fix which must be merged before any new release of Zappa can be published.
coverage: 74.831%. remained the same
when pulling 58f6cbe86d5d51e83166744cab31aa1b1db031a7 on jav/py3.12
into 77689e2a992f19f70c1372c3a48f930e45337431 on master.
Description
A single (but rather important) line was missed in #1292, which, if not corrected, may allow package managers to install any new releases of Zappa on Py3.7, even though all logic needed to support Py3.7 has now been removed from Zappa.
This PR is a 1-line (1-char, to be precise 🙃) fix which must be merged before any new release of Zappa can be published.