[
https://issues.apache.org/jira/browse/ARROW-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15762212#comment-15762212
]
Uwe L. Korn commented on ARROW-430:
-----------------------------------
Alternatively it would be nice to have a simple {{python/pom.xml}} that is also
updated by maven on a release.
> Python: Better version handling
> -------------------------------
>
> Key: ARROW-430
> URL: https://issues.apache.org/jira/browse/ARROW-430
> Project: Apache Arrow
> Issue Type: Improvement
> Affects Versions: 0.1.0
> Reporter: Uwe L. Korn
> Fix For: 0.2.0
>
>
> 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}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
