KoviAnusha commented on code in PR #56921:
URL: https://github.com/apache/airflow/pull/56921#discussion_r2458841737
##########
airflow-core/docs/release-process.rst:
##########
@@ -74,12 +74,12 @@ Deprecation policy
From time-to-time existing features will be deprecated, or modules will be
renamed.
-When this happens, the existing code will continue to work but will issue a
DeprecationWarning (or a subclass) when the code is executed.
+When this happens, the existing code will continue to work but will issue a
DeprecatedImportWarning (or a subclass) when the code is executed.
This code will continue to work for the rest of the current major version --
if it works on 2.0.0, it will work for every 2.Y.Z release.
So, for example, if we decided to start the deprecation of a function in
Airflow 2.2.4:
-* Airflow 2.2 will contain a backwards-compatible replica of the function
which will raise a DeprecationWarning
+* Airflow 2.2 will contain a backwards-compatible replica of the function
which will raise a DeprecatedImportWarning
Review Comment:
Addressed
##########
airflow-core/src/airflow/exceptions.py:
##########
@@ -472,14 +474,14 @@ class PodReconciliationError(AirflowException): # type:
ignore[no-redef]
"""Raised when an error is encountered while trying to merge pod
configs."""
-class RemovedInAirflow4Warning(DeprecationWarning):
+class RemovedInAirflow4Warning(DeprecatedImportWarning):
Review Comment:
Addressed
--
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]
