Skip to content

Conversation

@Taragolis
Copy link
Contributor

Remove remaining Airflow 2.3 compat part which initially was add in #28979 and partially removed in #33301

I'm not sure but seems like from airflow.lineage.entities import File it is a part of experimental linage and has nothing to do with AIP-53.


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

Copy link
Contributor

@eladkal eladkal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Papermill doesnt seem to be maintained
https://github.com/nteract/papermill
I think we will need to suspend this provider if that doesnt change

@Taragolis
Copy link
Contributor Author

I don't know about of Papermill state but we have 3 users of this provider at least in January 🤣 , who helps with testing on actual Papermill environment. However I agree if service/library doesn't maintained for a long period than better suspend it, and maybe it help to find regular maintainers

I've also check that we have some providers which seems like abandoned in our side, no changes for a long period of time and sometimes from initial version. I guess nothing we could do with that

@eladkal eladkal merged commit 55fbdfe into apache:main Sep 29, 2023
@eladkal
Copy link
Contributor

eladkal commented Sep 29, 2023

I've also check that we have some providers which seems like abandoned in our side, no changes for a long period of time and sometimes from initial version.

In most cases that is OK.
Some integrations are just simple thus do not require many changes.
I stated papermill as it does not support Python 3.11 the PR to add support for it is open for long time and mantainers ignore it thus the upstream library seems abandoned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants