On Tue, Apr 28, 2009 at 9:33 PM, Kirk Strauser <[email protected]> wrote: > On Apr 28, 2009, at 5:01 PM, Jorge Vargas wrote: > > On Tue, Apr 28, 2009 at 10:21 AM, Kirk Strauser <[email protected]> wrote: > > 1) When installing Python, be sure to select the HUGE_STACK_SIZE option. > > is this a second copy of python? is it a bug with the freeBSD package? > if this is the case could you send us a bug link so we can make a note > at http://www.turbogears.org/2.0/docs/main/DownloadInstall.html > > Neither. When installing python via the FreeBSD "ports collection", their > third-party software repository, HUGE_STACK_SIZE is a configuration menu > item that you can select. This advice isn't specific to TurboGears, > although it's apparently the most heavily threaded server-side Python > application I've installed and it triggered crashes. > I see, I'll remember to make a note the next time I'm working on docs.
> 2) When wondering why it's still crashing with the same errors, remember > that > > virtualenv copies in the Python binary and that you have to update that copy > > as well. > > unless you have 2 versions of python installed this should work, > otherwise it's a bug. virtualenv should pick up whatever python is > returned by "which python" in case you don't want to put it in your > path you can still use. also venv has a handy flag. > > I only have 1 version of python, but there are two copies of the python > executable: > k...@lite$ which python > /usr/local/bin/python > k...@lite$ source /opt/turbogears/bin/activate > (turbogears)k...@lite$ which python > /opt/turbogears/bin/python > Apparently virtualenv copies the python binary into the virtualenv's bin/ > directory, and that's what gets used from that point on. that is correct, this way it's a lot simpler for venv/python to talk to each other as the python executable knows how to load it's site-packages > The problem I had > was that I was reinstalling the system python with new compile options, the > copy of python inside the virtualenv wasn't replaced (nor should it have > been!). I wouldn't say it was a bug so much as a gotcha that I wanted to > warn the next person about. ahh I see, so after your reinstall a new venv will work as expected. > -- > Kirk Strauser > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
