[
https://issues.apache.org/jira/browse/ARROW-13083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17364380#comment-17364380
]
Krisztian Szucs commented on ARROW-13083:
-----------------------------------------
{{setuptools_scm}}'s API only allows us to pass a git describe command, but git
describe won't reach the new tags from the master branch since they are placed
on release branches which diverge from master. We could calculate a version
number ourselves but vendoring internal code from {{setuptools_scm}} is
questionable.
Another approach could be to merge (not rebase) the release branches to the
master branch so git describe can reach the tags.
cc [~apitrou]
> [Python] Wrong SCM version detection both in setup.py and crossbow
> ------------------------------------------------------------------
>
> Key: ARROW-13083
> URL: https://issues.apache.org/jira/browse/ARROW-13083
> Project: Apache Arrow
> Issue Type: Bug
> Components: Python
> Reporter: Krisztian Szucs
> Priority: Major
>
> Wanted to install nightly wheels for a rust integration test when I noticed
> that the nightly wheels get produced with base version 3.0.0.
> This is due to the recently changed release workflow. Now we're creating tags
> from release branches without a post rebase step, so setuptools_scm fails to
> find the correct version number on diverged branches.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
