From owner-freebsd-python@FreeBSD.ORG Fri Mar 26 23:43:54 2010 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 862FE106566B for ; Fri, 26 Mar 2010 23:43:54 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 130908FC08 for ; Fri, 26 Mar 2010 23:43:53 +0000 (UTC) Received: (qmail 23381 invoked by uid 399); 26 Mar 2010 23:17:13 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 26 Mar 2010 23:17:13 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4BAD4078.6000300@FreeBSD.org> Date: Fri, 26 Mar 2010 16:17:12 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.7) Gecko/20100218 Thunderbird/3.0.1 MIME-Version: 1.0 To: Steven Kreuzer References: <4702BA39-7C18-45C3-9920-9E460502B58F@freebsd.org> <4BAA9C32.6040606@delphij.net> <2D129848-8A41-4BB5-A58C-A9A35D5FBD9A@mac.com> <6201873e1003242207m49351c55id94341d872fd8e17@mail.gmail.com> In-Reply-To: X-Enigmail-Version: 1.0.1 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org, freebsd-python@freebsd.org Subject: Re: python and HUGE_STACK_SIZE X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Mar 2010 23:43:54 -0000 On 03/26/10 14:03, Steven Kreuzer wrote: > So, it seems like most of the time python scripts will work with HUGE_STACK_SIZE > turned off, but every once and a while some scripts will fail in non obvious ways > that could leave a person scratching their head for weeks trying to get to the bottom of it > > To me, it seems like the best behavior would be to default to compiling with that set. I'll create > a patch over the weekend and open a PR >From the discussion (not speaking from experience or python knowledge) it seems like an OPTION is the way to go, with the open question being defaults to on or defaults to off. What is the impact of HUGE_STACK_SIZE when it's compiled in, and how will it affect those running python stuff who don't actually need it? If it turns out that only a few ports need it and the impact is undesirable those ports that do need it could be adapted to test for it somehow and suggest that the user re-install python with the option. Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/