From owner-freebsd-python@freebsd.org Tue Jun 20 03:49:34 2017 Return-Path: Delivered-To: freebsd-python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC97ED8D804 for ; Tue, 20 Jun 2017 03:49:34 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A317D719CC for ; Tue, 20 Jun 2017 03:49:34 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: by mailman.ysv.freebsd.org (Postfix) id 9F907D8D801; Tue, 20 Jun 2017 03:49:34 +0000 (UTC) Delivered-To: python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9EE9AD8D800; Tue, 20 Jun 2017 03:49:34 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 814C6719CB; Tue, 20 Jun 2017 03:49:34 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id v5K3nR15075582 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 19 Jun 2017 20:49:27 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id v5K3nRL9075581; Mon, 19 Jun 2017 20:49:27 -0700 (PDT) (envelope-from sgk) Date: Mon, 19 Jun 2017 20:49:27 -0700 From: Steve Kargl To: Kubilay Kocak Cc: freebsd-ports@freebsd.org, python@FreeBSD.org Subject: Re: [PATCH] lang/python27 -- Fix namespace collision Message-ID: <20170620034927.GA75540@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20170618182905.GA67867@troutmask.apl.washington.edu> <20170618183112.GA67920@troutmask.apl.washington.edu> <9090f327-3266-35b3-8bf3-f83b7c741fe2@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9090f327-3266-35b3-8bf3-f83b7c741fe2@FreeBSD.org> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jun 2017 03:49:34 -0000 On Tue, Jun 20, 2017 at 01:06:28PM +1000, Kubilay Kocak wrote: > On 6/19/17 4:31 AM, Steve Kargl wrote: > > On Sun, Jun 18, 2017 at 11:29:05AM -0700, Steve Kargl wrote: > >> Both IEEE-754 2008 and ISO/IEC TS 18661-4 define the half-cycle > >> trignometric functions cospi, sinpi, and tanpi. When libm (aka > >> math.h) grows support for sinpi(x), lang/python27 has a namespace > >> collision. The attached patch fixes the problem. > >> > > Is this issue relevant only for particular (and/or future) FreeBSD > versions ('where libm grows supports for x, y') or independent of base > entirely? It will be an issue with a future BSD. It seems to take a long time before any of my libm improvements are committed. At the moment, bde and I are probably the only people with sinpi(x) in our libm. I do, however, anticipate that glibc will get these functions in the future as portions of ISO/IEC TS 18661-4 have already been implemented. > Also, could you open an upstream issue regarding this please, as a > long-term target for all local (Python port) patches is that they are > included upstream. In the 5 minutes that I've searched, I've found https://bugs.python.org/ but there are no instructions on how to submit a bug report. -- Steve 20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4 20161221 https://www.youtube.com/watch?v=IbCHE-hONow