Fix pytest warnings#526
Draft
georgelgeback wants to merge 1 commit intomainfrom
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
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.
I got tired of seeing so many warnings, so I fixed them.
What I manually fixed:
Warning: Support for class-based
configis deprecated, use ConfigDict instead.SADeprecationWarning: Callable object passed to the
defaultparameter for attribute 'standard_food_preferences' in a ORM-mapped Dataclasses context is ambiguous. [...] If this callable is intended to produce Core level INSERT default values for an underlyingColumn, use themapped_column.insert_defaultparameter instead. To establish this callable as providing a default value for instances of the dataclass itself, use thedefault_factorydataclasses parameter.SADeprecationWarning: Callable object passed to the
defaultparameter for attribute 'latest_modified' in a ORM-mapped Dataclasses context is ambiguous, and this use will raise an error in a future release. If this callable is intended to produce Core level INSERT default values for an underlyingColumn, use themapped_column.insert_defaultparameter instead. To establish this callable as providing a default value for instances of the dataclass itself, use thedefault_factorydataclasses parameter.passlib used crypt which was about to be deprecated in a future python version. It's also been about 6 years since last update. We also don't use it??? It's not required-by any package according to pip and not imported.
Fakeredis had some warnings which an update fixed.