-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding official py3.7 support #622
Comments
Hey @m1keil if you could try add 3.7 to tox and run tests, if everything passes then I am happy to add official support for 3.7. If there are things that are breaking then for v2 we will support >=2.7-3.6 for now. Plan is to drop Py2 for v3. |
Note that this commit suppressed DeprecationWarnings due to dependencies which have not yet updated their use of collections.abc. Signed-off-by: Brendan Devenney <[email protected]>
I tinkered with this a bit when I was getting set up. For what it's worth, the only issues I experienced were with the test dependencies:
There is an outstanding deprecation warning coming from
Suppose it comes down to whether you want to silence deprecation warnings in the project @ngfgrant, but Python 3.7 support seems functional. I've pushed the code I have (see above) for example. |
@devenney thanks - going to update this anyway. Also going to evaluate moving from PyYaml in favour of ruamel as it is better maintained and PyYaml. |
Note that this commit suppressed DeprecationWarnings due to dependencies which have not yet updated their use of collections.abc. Signed-off-by: Brendan Devenney <[email protected]>
Note that this commit suppressed DeprecationWarnings due to dependencies which have not yet updated their use of collections.abc. Signed-off-by: Brendan Devenney <[email protected]>
Note that this commit suppressed DeprecationWarnings due to dependencies which have not yet updated their use of collections.abc. Signed-off-by: Brendan Devenney <[email protected]>
Note that this commit suppressed DeprecationWarnings due to dependencies which have not yet updated their use of collections.abc. Signed-off-by: Brendan Devenney <[email protected]>
Note that this commit suppressed DeprecationWarnings due to dependencies which have not yet updated their use of collections.abc. Signed-off-by: Brendan Devenney <[email protected]>
Note that this commit suppressed DeprecationWarnings due to dependencies which have not yet updated their use of collections.abc. Signed-off-by: Brendan Devenney <[email protected]>
Note that this commit suppressed DeprecationWarnings due to dependencies which have not yet updated their use of collections.abc. Add pyenv to CI: support multiple Python versions * Bump CI Docker image version (to 0.4) * Add pyenv to Docker image * Support py27, py36, py37 Fix CI interaction with moto 1.3.7. Works around getmoto/moto#1924 by ensuring garbage defaults are set in the environment. Update setup.py for Python3.7 support Add package requirements for testing on python3.7/win
Note that this commit suppressed DeprecationWarnings due to dependencies which have not yet updated their use of collections.abc. Add pyenv to CI: support multiple Python versions * Bump CI Docker image version (to 0.4) * Add pyenv to Docker image * Support py27, py36, py37 Fix CI interaction with moto 1.3.7. Works around getmoto/moto#1924 by ensuring garbage defaults are set in the environment. Update setup.py for Python3.7 support Add package requirements for testing on python3.7/win
Note that this commit suppressed DeprecationWarnings due to dependencies which have not yet updated their use of collections.abc. Add pyenv to CI: support multiple Python versions * Bump CI Docker image version (to 0.4) * Add pyenv to Docker image * Support py27, py36, py37 Fix CI interaction with moto 1.3.7. Works around getmoto/moto#1924 by ensuring garbage defaults are set in the environment. Update setup.py for Python3.7 support Add package requirements for testing on python3.7/win
Note that this commit suppressed DeprecationWarnings due to dependencies which have not yet updated their use of collections.abc. Add pyenv to CI: support multiple Python versions * Bump CI Docker image version (to 0.4) * Add pyenv to Docker image * Support py27, py36, py37 Fix CI interaction with moto 1.3.7. Works around getmoto/moto#1924 by ensuring garbage defaults are set in the environment. Update setup.py for Python3.7 support Add package requirements for testing on python3.7/win
Note that this commit suppressed DeprecationWarnings due to dependencies which have not yet updated their use of collections.abc. Add pyenv to CI: support multiple Python versions * Bump CI Docker image version (to 0.4) * Add pyenv to Docker image * Support py27, py36, py37 Fix CI interaction with moto 1.3.7. Works around getmoto/moto#1924 by ensuring garbage defaults are set in the environment. Update setup.py for Python3.7 support Add package requirements for testing on python3.7/win
Note that this commit suppressed DeprecationWarnings due to dependencies which have not yet updated their use of collections.abc. Add pyenv to CI: support multiple Python versions * Bump CI Docker image version (to 0.4) * Add pyenv to Docker image * Support py27, py36, py37 Fix CI interaction with moto 1.3.7. Works around getmoto/moto#1924 by ensuring garbage defaults are set in the environment. Update setup.py for Python3.7 support Add package requirements for testing on python3.7/win
Note that this commit suppressed DeprecationWarnings due to dependencies which have not yet updated their use of collections.abc. Add pyenv to CI: support multiple Python versions * Bump CI Docker image version (to 0.4) * Add pyenv to Docker image * Support py27, py36, py37 Fix CI interaction with moto 1.3.7. Works around getmoto/moto#1924 by ensuring garbage defaults are set in the environment. Update setup.py for Python3.7 support Add package requirements for testing on python3.7/win
3.7 was released more than 6 months ago. 3.8 is scheduled to be released in October. Personally, I've been using Sceptre v2 with 3.7 for few months now without any issues. Is it time to add py37 to tox?
The text was updated successfully, but these errors were encountered: