setuptools-scm[toml] dependency causing issue in Airflow ArangoDB Provider

[pateash]

Hi, Team

We are trying to add ArangoDB provider to @apache/airflow.

The dependency

setuptools-scm[toml] (>=3.4)
automatically adds all files added to version control to the package that is built. This basically means that we have no way to control which of the source code files are used in which package.

The effect of this change was that when we build the airflow package, all providers are added to the package even if we did not include them which is caused our CI to fail.

Please find more information on PR apache/airflow#22548

[potiuk]

Yeah. This is crazy stuff really.

[joowani]

@pateash @potiuk taking a look

[joowani]

setuptools-scm[toml] does seem pretty disruptive. I can remove it from the dependency. It's a shame since it was very useful for auto versioning.

[potiuk]

setuptools-scm[toml] does seem pretty disruptive. I can remove it from the dependency. It's a shame since it was very useful for auto versioning.

You can add it as an extra

[aMahanna]

Hi @potiuk and @pateash

I have opened a PR to re-introduce the auto versioning mechanic of setuptools-scm, but this time without specifying it as a setup.py dependency.

This should not affect airflow's configuration of python-arango, but nevertheless I wanted to give you a heads up

[potiuk]

Thnks for letting us know. It's in build-system of pyproject.toml so I think it will be fine :)