Fix for Django 1.10 loaddata #28
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
timgraham
reviewed
Nov 23, 2016
| try: | ||
| call_command("loaddata", "initial_data", verbosity=0) | ||
| except CommandError as exc: | ||
| # Django 1.10+ throws if the file doesn't exist, and not |
There was a problem hiding this comment.
throws (Java-ish) -> errors (or raises)
no comma
add period
As per release notes: > loaddata now raises a CommandError instead of showing a warning when the specified fixture file is not found.
419c76e to
bfd0683
Compare
|
I don't understand #24, they are being loaded by djangobench even if django itself doesn't automatically load them. It would require rewriting the 18 benchmarks using them so I think it's out of scope for this PR. |
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.
As per release notes: