Python: Better version handling #15338
Description
We need better version handling for Python releases. setuptools_scm sadly conflicts a bit a with the workflow of conda-forge+git. In general, it seems that generating a version from a non-tagged git archive is not possible.
For tagged archives, we can use git's export-subst functionality but that will result in non-deterministic tarballs from Github.
My currently preferred (when not really clean but at least integrated into the release process) solution would be to read java/pom.xml and use this version number. For PEP-440 compability we would need to replace SNAPSHOT with pre1.
Reporter: Uwe Korn / @xhochy
Assignee: Uwe Korn / @xhochy
Note: This issue was originally created as ARROW-430. Please see the migration documentation for further details.