python and HUGE_STACK_SIZE
in [Ports]
|
Prev: FreeBSD Port: tomcat-6.0.24
Next: Unknown Facts
From: Steven Kreuzer on 24 Mar 2010 18:20 A coworker of mine got bit by this bug on and off for the last few weeks and it appears he might not be the only one as documented in this blog: http://tomster.org/blog/archive/2006/09/27/size-does-matter If python needs to be compiled with HUGE_STACK_SIZE on FreeBSD, is there a reason to provide the option to not compile python with it, or at the very least, should it default to being on? I'm not a python guy, so I am just asking in case what is in the blog post is true. -- Steven Kreuzer http://www.exit2shell.com/~skreuzer -- Steven Kreuzer http://www.exit2shell.com/~skreuzer _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Xin LI on 24 Mar 2010 19:11 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [freebsd-python@ cc'ed] On 2010/03/24 15:20, Steven Kreuzer wrote: > A coworker of mine got bit by this bug on and off for the last few weeks and it appears he might not > be the only one as documented in this blog: > > http://tomster.org/blog/archive/2006/09/27/size-does-matter > > If python needs to be compiled with HUGE_STACK_SIZE on FreeBSD, is there a reason > to provide the option to not compile python with it, or at the very least, should it default to > being on? Ah, yes this is the thing I turn on on all systems I have myself... I'd vote for enabling it by default. Cheers, - -- Xin LI <delphij(a)delphij.net> http://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iQEcBAEBAgAGBQJLqpwyAAoJEATO+BI/yjfBrwwIAJfEAeJ9QXTvgOeMRyAdekcU teYGqTVP1W3qE7adxvM/2MMQm4ogyJtAJBu9UQVAwiYtckNd1mpaIuQdfDvuc1fD vD5OT+8Sy+TXqxLi2A29HZkOCvOoYuZ03WwyF5YMpMU6uPHGa0fnx+gNtXGuOxSN V45ZWxlEwNNKv+WYZzehF5jJvIPLXadrPYP/y53loIXqxA5htV+ZPpiGeidwTDun u+o5AjLrcRKRM+hrf10X6gfCgJZpQyqeL88fDqhUX6uL1QIQJHg1nBHQ+6DbZrR9 R2cCadkhCF2X3nC3stTDi/KvuAZ4rZZo02lUf8MdxK7PX8T9cd4A7brHCltxoOU= =UaWe -----END PGP SIGNATURE----- _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Chuck Swiger on 24 Mar 2010 19:50 Hi-- On Mar 24, 2010, at 4:11 PM, Xin LI wrote: >> If python needs to be compiled with HUGE_STACK_SIZE on FreeBSD, is there a reason >> to provide the option to not compile python with it, or at the very least, should it default to >> being on? > > Ah, yes this is the thing I turn on on all systems I have myself... I'd > vote for enabling it by default. 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. I don't have any objection to turning it on, but it's not needed by default for most things. YMMV. Regards, -- -Chuck _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Adam Vande More on 25 Mar 2010 01:07 On Wed, Mar 24, 2010 at 5:50 PM, Chuck Swiger <cswiger(a)mac.com> wrote: > > 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. > > I don't have any objection to turning it on, but it's not needed by default > for most things. YMMV. > > 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? -- Adam Vande More _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Steven Kreuzer on 26 Mar 2010 17:03
On Mar 25, 2010, at 1:07 AM, Adam Vande More wrote: > On Wed, Mar 24, 2010 at 5:50 PM, Chuck Swiger <cswiger(a)mac.com> wrote: > >> >> 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. >> >> I don't have any objection to turning it on, but it's not needed by default >> for most things. YMMV. >> >> > 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 _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org" |