-
Notifications
You must be signed in to change notification settings - Fork 23
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
Loosen jinja versions requirements - fixes #41 #42
Conversation
@zerwes Any chance this can be merged ? this is blocking us from using the lib and I would like to avoid forking just for this simple change. |
thank you for the fix |
Thanks @zerwes !! Can this please be pushed to pypi ? |
@zerwes Maybe less busy time ? any chance this can be pushed to pypi ? |
@AvnerCohen ... Sorry, not much time spare (children, wife, house, job ... the full catastrophe), but I tried to make release 0.4.17 with your PR ...
python 2.7 is dead, long live python 2.7 ... :) |
Thanks @zerwes Totally understand life and so. If this is the case, I would actually suggest to drop python 2.7 support and publish this PR both together as part of 0.5 This way there will be no need to spend any time on solving this for a minor patch on 0.4x. |
@zerwes ping please :) |
No description provided.