Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1D764200BE1 for ; Mon, 19 Dec 2016 17:11:06 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 1C07D160B21; Mon, 19 Dec 2016 16:11:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8AD72160B14 for ; Mon, 19 Dec 2016 17:11:05 +0100 (CET) Received: (qmail 83295 invoked by uid 500); 19 Dec 2016 16:10:59 -0000 Mailing-List: contact dev-help@arrow.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@arrow.apache.org Delivered-To: mailing list dev@arrow.apache.org Received: (qmail 82996 invoked by uid 99); 19 Dec 2016 16:10:59 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Dec 2016 16:10:59 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 773152C0059 for ; Mon, 19 Dec 2016 16:10:59 +0000 (UTC) Date: Mon, 19 Dec 2016 16:10:59 +0000 (UTC) From: "Uwe L. Korn (JIRA)" To: dev@arrow.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ARROW-379) Python: Use setuptools_scm/setuptools_scm_git_archive to provide the version number MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 19 Dec 2016 16:11:06 -0000 [ 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)