django 4x support #58
Draft
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
changed setup for fork testing
updated setup for testing
updated setup for testing
updated setup for testing
trying to get it to install fork not main package...
fix for 4.1 urls
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Reason for PR
With django 3.2 losing support later this year (2024), it is important for new and old projects to have support for more recent versions of django. With that in mind, I'm opening this PR with the hopes of making DMP compatible with more recent versions of django. These changes appear to work with django 4.1, but may not be reverse compatible yet.
PLEASE NOTE: This is a WIP build. I have not extensively tested it.
CHANGES