-
Notifications
You must be signed in to change notification settings - Fork 74
remove temp directory after validation #64
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
Conversation
|
Hi Maor, welcome and thanks for that. Looking through your change I remembered that this could be done through a context, like in the examples for May I add your name to Markus |
|
hey! thanks for replying :) |
|
Terrascript is meant to be compatible with Python 3.3+ only. This was an early design decision after I had many nightmares, making a different project compatible with Python 2 and Python 3. |
|
i totally agree with the approach. but if i may - |
|
There is another big question that needs answering first. Terraform 0.12 will introduce some major changes and I have to decide whether any future Terrascript releases will remain backward compatible with Terraform 0.11.x or whether I start "from scratch", e.g. Terrascript2. And, as a consequence, would a Terrascript2 support Python 3 and Python 2. In my view the best approach would be to use the Python 2 backports.tempfile module which supports |
|
i think i'll go with your first suggestion, and will migrate existing python2 projects to python3. this has to be done either way :) regarding CONTRIBUTORS.md - feel free, and thank you! |
|
For the fun of it I tried a quick test against Python 2.7 but immediately ran into issues that would require more work (https://www.travis-ci.org/mjuenema/python-terrascript/builds/514390932). Python 2 support is definitely something for later. |
|
for later or for never :) |
Great work on this! Thanks a lot!
Please accept my humble contribution ;)