[DEV-10748] Fix for psycopg2.errors.InvalidCursorName while running tests #4052
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
…rrors.InvalidCursorName as seemingly certain functionality has been changed in newer versions. However, the version of Django we were previously using, 3.2.* the minor version is still compatible with python 3.10.13 so reverted back to that and the error resolved itself.
…n version 3.10.13 but so is django version 4.2.11. Testing this now to see if it causes any additional errors with existing functinality and tests.
ghost
approved these changes
Mar 20, 2024
Base automatically changed from
dev-10805-black-reformatting
to
dev-10645-python-upgrade-3.10
March 20, 2024 20:28
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.
The newer version of Django was resulting in the psycopg2.errors.InvalidCursorName as certain functionality has been changed in newer versions. Viewing the documentation and stackoverflow links I realized that this is a known issue while upgrading to the latest version of Django. However, the version of Django we were previously using, 3.2.* the minor version is still compatible with python 3.10.13 so reverted back to that.
Description:
Reverted the Django dependency version back to 3.2.*.
Technical details:
The technical details for the knowledge of other developers. Any detailed caveats or specific deployment steps should be outlined here.
Requirements for PR merge:
Area for explaining above N/A when needed: