Il giorno 23/gen/2012, alle ore 09:54, C Anthony Risinger ha scritto: > On Sun, Jan 22, 2012 at 7:16 PM, C Anthony Risinger <[email protected]> wrote: >> On Sun, Jan 22, 2012 at 2:18 PM, C Anthony Risinger <[email protected]> wrote: >>> >>> however, i am now getting a SIGSEGV on normal SIGINT while at the >>> --pyshell prompt: >> >> if i change plugins/python/python_plugin.c:201-202 from: >> >> if (uwsgi.has_threads) >> PyGILState_Ensure(); >> >> ... to: >> >> //if (uwsgi.has_threads) >> PyGILState_Ensure(); >> >> ... python 3.2.2 and 2.7.2 no longer segfault (my terminal is still >> messed up and requires a `reset`, but this is a different bug that has >> always existed). > > after grepping the source and poking around a bit, i see the ini files > in buildconf use: > > threading = 1 > > ... but the option is defined as: > > enable-threads > threads-* > > ... i dont see anywhere in the C code that uses the `threading` as a > configuration option ... should these be changed? > >
The options in build profiles are only parse by uwsgiconfig.py By the way, have you tried latest tip ? I have added a check for python availability (as pyshell will destroy the python environment on exit) in "atexit" hook I am heavy updating http and fastrouter plugins, if you get errors on their build remove them from the build profile -- Roberto De Ioris http://unbit.it JID: [email protected] _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
