From owner-freebsd-ports@FreeBSD.ORG Fri Mar 26 21:28:54 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8032D106566B; Fri, 26 Mar 2010 21:28:54 +0000 (UTC) (envelope-from sjk4015@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.24]) by mx1.freebsd.org (Postfix) with ESMTP id 1F3078FC08; Fri, 26 Mar 2010 21:28:53 +0000 (UTC) Received: by qw-out-2122.google.com with SMTP id 5so2521257qwi.7 for ; Fri, 26 Mar 2010 14:28:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:content-type :mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=h0X0JnH1/Hkxa3hOqFb8cm/ScICIgw1nhTULMwZSCZY=; b=IPhxzjy1uCWn0YsUNzbJIa2w6ELDvVU8NBsylF7Mfl9pT16uUPM8reXn2lzo3trIbr /gA8L7n6q50AGwk86+qzcVvrctKv6f54NSVmzzpsk2Lbejt4tC68ivMAAojljXNeKDzw PMwDG+uqP6RUVlV4qUFbghcZ+RiRaTHlxQILI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=C9xgmWkGXQdILSNyUwSasIfpJ3oc7kUNcyGT9B2lCTNmvYMIHjh0bdawfX/YG2S66d mfXpbXpziRUnCT3U8kNZsUR89YnfbfNwDbXz7AsHFrKmVs6W8t3/Cg5va+oI9dzq6SHO djNBWQgeCW7pQz4mBTAifjZWB7JRHSSq4c/kw= Received: by 10.224.36.165 with SMTP id t37mr510061qad.338.1269637435203; Fri, 26 Mar 2010 14:03:55 -0700 (PDT) Received: from stevenmac.hudson-trading.com (smtp.hudson-trading.com [209.249.190.9]) by mx.google.com with ESMTPS id 5sm3965950qwh.5.2010.03.26.14.03.53 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 26 Mar 2010 14:03:54 -0700 (PDT) Sender: Steven Kreuzer Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1077) From: Steven Kreuzer In-Reply-To: <6201873e1003242207m49351c55id94341d872fd8e17@mail.gmail.com> Date: Fri, 26 Mar 2010 17:03:52 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4702BA39-7C18-45C3-9920-9E460502B58F@freebsd.org> <4BAA9C32.6040606@delphij.net> <2D129848-8A41-4BB5-A58C-A9A35D5FBD9A@mac.com> <6201873e1003242207m49351c55id94341d872fd8e17@mail.gmail.com> To: freebsd-ports@freebsd.org, freebsd-python@freebsd.org X-Mailer: Apple Mail (2.1077) Cc: Subject: Re: python and HUGE_STACK_SIZE X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Mar 2010 21:28:54 -0000 On Mar 25, 2010, at 1:07 AM, Adam Vande More wrote: > On Wed, Mar 24, 2010 at 5:50 PM, Chuck Swiger wrote: >=20 >>=20 >> I've run and written quite a bit of Python (including Trac, Mailman, = the >> Python IDE, our own custom stuff [like some log munging and web = processing >> stuff], and even a few graphical Python games) without ever turning >> HUGE_STACK_SIZE on. >>=20 >> I don't have any objection to turning it on, but it's not needed by = default >> for most things. YMMV. >>=20 >>=20 > Yes, I've had the same experience. When doing socket level python = stuff, > I've had to increase the buffer size, which seems to be at least = indirectly > related to stack size but setting it manually has been easy enough. = Are > there any negative repercussions to turning on huge ie like would = scripts > start using more memory, or is just giving them the ability to use it > without explicitly setting it? 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 -- Steven Kreuzer http://www.exit2shell.com/~skreuzer