As discussed in Slack - yes - that would have to be the case, but fortunately (following after Jens's inquisitiveness) the versions of WTForms that introduced breaking changes have also dropped Python 3.8 support so the last issue with Python 3.8 is solved and we do not have to do anything!
Good. That would be some effort to bring it back for FAB. J. On Fri, Nov 1, 2024 at 2:48 PM Jens Scheffler <j_scheff...@gmx.de.invalid> wrote: > Hi Jarek, > > we dropped support for Python 3.8 for all providers. If FAB should be > installed in 2.10.3 in Python 3.8... we would need to add support back > again? > > Jens > > On 01.11.24 14:45, Jarek Potiuk wrote: > > Also I have found today that we have a problem with FAB provider as it > > cannot be installed on Python 3.8 - but we need the fix for Airflow > 2.10.3 > > to be installable on Python 3.8 as well - so we need to release rc3 > anyway. > > > > On Thu, Oct 31, 2024 at 7:48 PM Jarek Potiuk <ja...@potiuk.com> wrote: > > > >> -1 binding. I found today that our provider packages (also previous > ones) > >> are not fully reproducible. The package produced this morning was > different > >> from the same package produced in the afternoon - simply because flit > >> (which we are using to build our packages) released a new version > 3.10.0 4 > >> hours ago - and we did not have flit version pinned in the build > >> requirements. > >> > >> I think this is the day of the weirdest bugs and coincidences I > >> encountered ever. > >> > >> Fix in https://github.com/apache/airflow/pull/43557 > >> > >> This is the difference: > >> > >> > >> On Thu, Oct 31, 2024 at 11:22 AM Elad Kalif <elad...@apache.org> wrote: > >> > >>> Hey all, > >>> > >>> I have just cut the new wave Airflow Providers packages. This email is > >>> calling a vote on the release, which will last for 24 hours - which > means > >>> that it will end on November 01, 2024 10:20 AM UTC and until 3 binding > +1 > >>> votes have been received. > >>> > >>> Consider this my (binding) +1. > >>> > >>> Airflow Providers are available at: > >>> https://dist.apache.org/repos/dist/dev/airflow/providers/ > >>> > >>> *apache-airflow-providers-<PROVIDER>-*.tar.gz* are the binary > >>> Python "sdist" release - they are also official "sources" for the > >>> provider > >>> packages. > >>> > >>> *apache_airflow_providers_<PROVIDER>-*.whl are the binary > >>> Python "wheel" release. > >>> > >>> The test procedure for PMC members is described in > >>> > >>> > https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-pmc-members > >>> > >>> The test procedure for and Contributors who would like to test this RC > is > >>> described in: > >>> > >>> > https://github.com/apache/airflow/blob/main/dev/README_RELEASE_PROVIDER_PACKAGES.md#verify-the-release-candidate-by-contributors > >>> > >>> > >>> Public keys are available at: > >>> https://dist.apache.org/repos/dist/release/airflow/KEYS > >>> > >>> Please vote accordingly: > >>> > >>> [ ] +1 approve > >>> [ ] +0 no opinion > >>> [ ] -1 disapprove with the reason > >>> > >>> Only votes from PMC members are binding, but members of the community > are > >>> encouraged to test the release and vote with "(non-binding)". > >>> > >>> Please note that the version number excludes the 'rcX' string. > >>> This will allow us to rename the artifact without modifying > >>> the artifact checksums when we actually release. > >>> > >>> The status of testing the providers by the community is kept here: > >>> https://github.com/apache/airflow/issues/43545 > >>> > >>> The issue is also the easiest way to see important PRs included in the > RC > >>> candidates. > >>> Detailed changelog for the providers will be published in the > >>> documentation > >>> after the > >>> RC candidates are released. > >>> > >>> You can find the RC packages in PyPI following these links: > >>> > >>> https://pypi.org/project/apache-airflow-providers-amazon/9.1.0rc2/ > >>> https://pypi.org/project/apache-airflow-providers-fab/1.5.0rc2/ > >>> > >>> Cheers, > >>> Elad Kalif > >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > For additional commands, e-mail: dev-h...@airflow.apache.org > >
