amoghrajesh commented on issue #55889:
URL: https://github.com/apache/airflow/issues/55889#issuecomment-3326985583
@eladkal you might be right!
We also have a prek hook for that it seems:
```
- id: check-no-airflow-deprecation-in-providers
language: pygrep
name: Do not use DeprecationWarning in providers
description: Use AirflowProviderDeprecationWarning in providers
entry: "^\\s*DeprecationWarning*"
pass_filenames: true
files: ^providers/.*/src/airflow/providers/.*\.py$
```
So i believe we continue using `AirflowProviderDeprecationWarning` for
providers. But I wonder if we could subclass `FutureWarning` instead of
`DeprecationWarning` for provider warnings instead? The motivation behind this
it:
FutureWarning family → user-visible API change notices used even by NumPy,
Pandas for their API changes
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
