From owner-freebsd-python@FreeBSD.ORG Fri Feb 8 11:02:40 2013 Return-Path: Delivered-To: python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 60C904D9 for ; Fri, 8 Feb 2013 11:02:40 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) by mx1.freebsd.org (Postfix) with ESMTP id 2B379C33 for ; Fri, 8 Feb 2013 11:02:40 +0000 (UTC) Received: by mail-ie0-f174.google.com with SMTP id k10so4887168iea.33 for ; Fri, 08 Feb 2013 03:02:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=Ia6svP6cCcPor2lmsBhdfOeHtD38UDcytmAfdgPeifc=; b=XcYac8qtFdtVRSwn4/e08i7uAi/RPqrAJ393WTP8xz1O+vQjj2u4xabTiuqQ3GCMUx p5GyTskPx5L3mk/mD7ACr+iYjrtt6D/PuEjJzBGRdyIRjktmFxN0YM71o7h9xHtmGoYK VQBSnPFAUNImSk3ReTe1YuqcVlOzczkGjjTE78djzVCnhwaFS82/78UyAbi5uSPpqTV3 mhbmOu3Y6kc0TIKRaZf/UMdp87Ok48Uxrt8si7AQzUWBXxhw99tqbF05TVObUCcklHu9 UFr++uKV4f7dFf6NZq/c2Rz9R8NkMlK03AVPnUrFVYHGOhscWeSEWTR2PueAyL/5azQc VlZA== X-Received: by 10.43.65.145 with SMTP id xm17mr8117250icb.35.1360321359905; Fri, 08 Feb 2013 03:02:39 -0800 (PST) Received: from [192.168.1.7] (ppp59-167-128-11.static.internode.on.net. [59.167.128.11]) by mx.google.com with ESMTPS id kf2sm14730684igc.0.2013.02.08.03.02.36 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 08 Feb 2013 03:02:38 -0800 (PST) Message-ID: <5114DB3B.2090902@gmail.com> Date: Fri, 08 Feb 2013 22:02:19 +1100 From: Kubilay Kocak User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "Mikhail T." Subject: Re: Question about a new Python port References: <5111ACB4.5050506@aldan.algebra.com> In-Reply-To: <5111ACB4.5050506@aldan.algebra.com> X-Enigmail-Version: 1.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: python@FreeBSD.org X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 11:02:40 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 6/02/2013 12:07 PM, Mikhail T. wrote: > Hello! > > Attached is a shar for a new port -- of the bencode-module > . Everything is fairly > straightforward about it, except: > > 2. The new port also drops an egg -- without even the egg-info file > -- maybe, all such ports should be forced (by bsd.python.mk) to > properly unzip and install the contents? Instead of unzipping at > run-time every time? It works either way, I'm sure, but it seems to > me, the .egg concept was created for the benefit of people, who do > not use anything like the Ports system. > > Thanks for the feedback. Yours, > > -mi I've tried a few things in the past regarding zipped eggs, overriding pyeasyinstall_args with a -Z in the Makefile. I've settled mostly on adding zip_safe=False into setup.py's until such time as we can figure out a clear way forward regarding python packaging. - -- Ta, Koobs -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJRFNs7AAoJEODRMIXMJgkAL8oIAIrzpdTfzFrfLMjJr7qZZrsS sIeu8LFN+YlyrnMVgLrgF7Pqw890WFapHL1XHeFiGF7EI45arbn+KEJq9r2DH+qi nQrBTAT6rdhuJ5C/XTS1xiT3RJkL3aN4GVawrVrkTWLjstLH1FCN9DT0DDOpXaK6 I6W+9OhPTL9decQA8JMSShzzOb9ny6J+8uq8ZCXywg5BEiJsLxL7jS4uRDG4HWu6 3npI6mD2kNDJgU1ZbLvBiN7qz0GFavXyD6FqhWnM5b+FlxmdvOyvqASdIw6iQBrx A+8iVpBMru+zSya3ubnZY7nhwfaPGlbw536Ib9bpNf6nGJEhmiYrXhElJEgjgPU= =wLvV -----END PGP SIGNATURE-----