-
Notifications
You must be signed in to change notification settings - Fork 1
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
Release 0.1.2 #73
Release 0.1.2 #73
Conversation
Hotfix server initialization bug
Merge latest master hotfix to dev
Features/info button custom id
to keep fct send_mail() generic
After upgrading django, I ran into error: INstalling gdal into env via conda solved the problem.
Same here with new Django version. For handlers:
|
As @henhuy already said, this seems to be a django 2.2 related issue. (cf. thread on SO)
You do not have to, @henhuy and I did.. |
@henhuy We had a serious GDAL django bug before which was really a pain in the ..., remember? We had to fix this manually. Does django 2.2 fix this? EDIT: I was wrong, it was a problem with libgeos (django bug tracker). As it was merged I guess it's included in v2.2 |
BTW: The current situation reveals that it might be a good idea to restrict the version range of packages to a specific release, in this case django 2.2. (before, the django 2.1-optimized code was tested with 2.2 all the time according to the current versionless |
I'd like to release today, let me summarize the work to be done:
|
I don't have time to work on this today, the WAM core is independent of the WAM APP though, I think the release can be done and we'll make the fixes to WAM_FRED app on monday :) |
Right, I ensured my app to work properly so it's ok for me. Just wanted to have everything fixed in one go :) |
Fixes/duplicate installed apps
django expects them to be used like this, even if they seem not to be used
Waiting for #64...