pythonPackages.django-raster: 0.3 -> 0.3.1 #23701
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
cc @FRidh |
lsix
force-pushed
the
update_django-raster
branch
from
c1b05a0
to
1ca372e
Compare
FRidh
approved these changes
Mar 10, 2017
|
Will you check for and push to 17.03? |
|
Yes, I’ll check that everything is fine with |
|
Y'know you can probably get rid of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation for this change
django-raster-0.3.1fixes the celery-4 compatibility. This allows to drop completely the old celery-3 branch.This should probably be incorporated into 17.03 to drop completely
celery_3(which was only used bydjango_raster)Things done
(nix.useSandbox on NixOS,
or option
build-use-sandboxinnix.confon non-NixOS)
nix-shell -p nox --run "nox-review wip"./result/bin/)