improve deprecation error messages #715
Merged
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 deprecation message for not providing a df to one of the methods that needs it always referenced the constructor, but they'll also be printed if someone reuses a dataset built with another method, e.g. the following code
would show the deprecation warning about providing the df to the constructor, even though it wasn't provided to it. This changes the message slightly to suggest that the df may come from either the constructor or a previous method.
Also now raises an informative error if the df wasn't provided at all, e.g. the following code
would raise a confusing error about the StatsForecast object not having a
ga
attribute. This now asks for thedf
argument to be provided.