This repository was archived by the owner on Jan 12, 2024. It is now read-only.
Use Django 1.9+ location for postgresql backend #1
Conversation
This file contains hidden or 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
This was renamed in [Django Ticket #25175](https://code.djangoproject.com/ticket/25175) and there's an ongoing discussion about removing the old name.
Author
Contributor
|
@adamchainz thanks for the PR! AFAICT, this would break in Django 1.8, right? I'd prefer to wait with merging this until 1.8 is EOL'd. Or alternatively a fallback to import the legacy location if the import of |
Author
|
Tada |
Contributor
|
Awesome, thanks! I'll push an update soon! |
|
@beniwohli can this be merged / released to PyPI? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
This was renamed in Django Ticket #25175 and there's an ongoing discussion about removing the old name.