Taragolis commented on code in PR #37330: URL: https://github.com/apache/airflow/pull/37330#discussion_r1486440572
########## airflow/providers/qdrant/__init__.py: ########## @@ -14,3 +14,29 @@ # KIND, either express or implied. See the License for the # specific language governing permissions and limitations # under the License. +# +# NOTE! THIS FILE IS AUTOMATICALLY GENERATED AND WILL BE +# OVERWRITTEN WHEN PREPARING DOCUMENTATION FOR THE PACKAGES. +# +# IF YOU WANT TO MODIFY THIS FILE, YOU SHOULD MODIFY THE TEMPLATE +# `PROVIDER__INIT__PY_TEMPLATE.py.jinja2` IN the `dev/breeze/src/airflow_breeze/templates` DIRECTORY +# +from __future__ import annotations + +import packaging.version + +__all__ = ["__version__"] + +__version__ = "1.0.0" + +try: + from airflow import __version__ as airflow_version +except ImportError: + from airflow.version import version as airflow_version + +if packaging.version.parse(packaging.version.parse(airflow_version).base_version) < packaging.version.parse( Review Comment: > BTW. I think it's the 3rd or forth iteration on how we store Airflow version. That is why I would like to open discussion, because someone might have filling: "Lets stop to do this kind of stuff". I've planed initially that I've did it today, but a bit hectic day, so I hope I would have a time and prepare some options and pros and cons. > Yes. We could do that and do it even now, but it will be usable in providers where min_airflow_version is 2.9 Of we could even use conditions in jinja templates based on the version, configure it one time and when the time is coming for min 2.9 it would replaced automatically. -- 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]
