-
Notifications
You must be signed in to change notification settings - Fork 75
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
🐛(dogwood/3/fun) pin django-classy-tags
version to 0.8.0
#248
Conversation
@madmatah I think the other flavors will have the same problem!? |
Thanks ! I checked after your comment : On Hawthorn :It seems to be OK because
On Eucalyptus :The installed version is 2.0.0 and need to be pinned, yep. |
So should we pin it to 0.8 instead if that's what Hawthorn is running on!? |
@sampaccoud Yes we can do that to be sure. |
7ca6ccb
to
f164c84
Compare
django-classy-tags
version to 1.0.0django-classy-tags
version to 0.8.0
`django-classy-tags` 2.0.0 dropped support for python 2.x. As a result, we get fatal errors in our recent builds. We pin it to version 0.8.0 because that's the version used in hawthorn base requirements.
Fixed - Pin django-classy-tags to 1.0.0 to avoid breaking changes in 2.0.0
`django-classy-tags` 2.0.0 dropped support for python 2.x. As a result, we get fatal errors in our recent builds. We pin it to version 0.8.0 because that's the version used in hawthorn base requirements.
Fixed - Pin django-classy-tags to 0.8.0 to avoid breaking changes
f164c84
to
7b2fea5
Compare
Done! I'm ready for a final review if the CI checks pass 🙂 |
@madmatah are the |
Purpose
Recent builds of dogwood.3-fun install
django-classy-tags
2.0.0, that is not compatible anymore with python 2.x.Same problem with eucalyptus flavor.
Proposal
django-classy-tags
version to 0.8.0