tgrandje opened a new pull request, #48229:
URL: https://github.com/apache/airflow/pull/48229
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
Thank you for contributing! Please make sure that your code changes
are covered with tests. And in case of new features or big changes
remember to adjust the documentation.
Feel free to ping committers for the review!
In case of an existing issue, reference it using one of the following:
closes: #ISSUE
related: #ISSUE
How to write a good git commit message:
http://chris.beams.io/posts/git-commit/
-->
<!-- Please keep an empty line above the dashes. -->
---
As discussed in https://github.com/apache/airflow/discussions/46266 there
are (and will be more) usecases for `sqlalchemy>0.2.0` usage. As far as I know,
this will stay there untill Airflow 3 is released. Until then, (I think) there
is a good point for documenting on how to deal with this, even if this is
**not** intended behaviour: `pandas` for instance cannot work with Airflow as
of yet.
The current PR :
* adds a general warning on using dependencies in a virtualenv which are not
compatible with airflow (this subject was not documented yet I think)
* adds a note in the virtualenv tutorial listing the known side effects to
using sqlalchemy>0.2.0.
--
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]
