-
Notifications
You must be signed in to change notification settings - Fork 17
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
Updates required for new python/django #204
Comments
Trying to get tests passing on this branch; https://github.com/marksweb/django-app-helper/tree/feature/204-upgrades |
The I didn't expect to need to fix anything around that given that's how the test suite has been running previously 🤔 |
Looks like a circular import error: https://github.com/pietzschke/django-app-helper/runs/5187464956?check_suite_focus=true |
@pietzschke Yes, things very quickly got complicated as I started to update I'm not sure if it translates well, but in English I think we'd called this a "chicken & egg situation" because it's hard to know what needs to change first! |
@marksweb i would say we need a new version on filer first, using the gettext_lazy functions: But the tests on cms maybe fail anyway 🤔 |
@pietzschke Yes, I thought that a release of django-filer that brings some of the changes in, without going as far as my django 4 support which might break things as it has to drop support. I don't think I've done it on django-filer yet, but I've been putting pre-commit hooks on projects that belong to the django-cms association. Two of the hooks I've been using are py-upgrade and django-upgrade. If we're looking at moving support django >=2.2 I think running these hooks will make upgrades an automated process. Support for python 3.6 also needs to go as it's EOL so py-upgrade can be targeted at >=3.7 to bring the python up to date. |
@marksweb Okay great, i will try to add the pre-commit hooks tomorrow, run them and include the code locally for testing in the app helper. I will let you know ✌️ |
@marksweb @pietzschke sorry for the long delay, I will tackle this really soon to get this application back on track |
@yakky No need to apologise. If we can help out with this or any of your other cms apps, let me know & I'll reach out to the cms core team. |
Description
Updates to the app are required for new python/django so that apps which depend on this application can continue to develop.
I've made a start on this, but require an issue to reference in my branch.
Proposed solution
Update tox/github workflows & then take it from there.
The text was updated successfully, but these errors were encountered: