From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: [PATCH 12/12] gnu: python: Add python-ipaddress. Date: Sat, 6 Aug 2016 20:20:17 -0400 Message-ID: <20160807002017.GA4762@jasmine> References: <20160805183730.19049-2-david@craven.ch> <20160805183730.19049-12-david@craven.ch> <20160805185019.GA20142@jasmine> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36298) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bWBpX-0003if-Ke for guix-devel@gnu.org; Sat, 06 Aug 2016 20:20:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bWBpT-0007CT-25 for guix-devel@gnu.org; Sat, 06 Aug 2016 20:20:38 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:55957) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bWBpR-00079b-2B for guix-devel@gnu.org; Sat, 06 Aug 2016 20:20:34 -0400 Content-Disposition: inline In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: David Craven Cc: guix-devel On Sat, Aug 06, 2016 at 02:52:37PM +0200, David Craven wrote: > > I believe we already have python2-ipaddress, although an older version. > > Ups, I missed that. Thanks. > > Can you answer some questions on best practices for packaging python packages? > > 1. Are python-setuptools inputs or native-inputs? It seems to be done > both ways but I guess it doesn't really matter since it's an interpreted > language. Almost always native-inputs, but there are a handful of packages that actually use setuptools at runtime. > 2. Pypi uri scheme changed in April to including a blake hash of the > files, but they introduced backwards compatible redirects after it > broke many existing tools [0]. Should new packages use the new > or the old scheme? IMO the old one is cleaner since we can use > (pypi-uri "package-name" version) to construct it instead of having > long hashes. If this is a best practice we should also have the > pypi importer suggest it instead of the new url's. We prefer to use pypi-uri. We used the long blake URLs while we were adjusting pypi-uri to work with the new PyPi URL scheme.