arrow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe L. Korn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARROW-379) Python: Use setuptools_scm/setuptools_scm_git_archive to provide the version number
Date Mon, 19 Dec 2016 16:10:59 GMT

    [ https://issues.apache.org/jira/browse/ARROW-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15761562#comment-15761562
] 

Uwe L. Korn commented on ARROW-379:
-----------------------------------

Pulling the source code from git instead of a tarball via HTTP in the pyarrow recipe might
solve this issues as this should enable {{setuptools_scm}} to determine the version. Sadly
you cannot determine a version from non-tagged git archives.

An extreme workaround is to set {{SETUPTOOLS_SCM_PRETEND_VERSION}} to force a version from
the outside but that should really be the last resort.

> Python: Use setuptools_scm/setuptools_scm_git_archive to provide the version number
> -----------------------------------------------------------------------------------
>
>                 Key: ARROW-379
>                 URL: https://issues.apache.org/jira/browse/ARROW-379
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Python
>            Reporter: Uwe L. Korn
>            Assignee: Uwe L. Korn
>              Labels: newbie
>
> Instead of relying on a hardcoded string, it would be better to infer the version number
from the SCM. This would get rid of the custom code in the release script (which I'm not sure
if it is actually working) and also provide better (i.e. increasing) dev-versions. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message