[Bug 204793] www/mod_python35: Fatal Python error: PyEval_SaveThread: NULL tstate

2016-03-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204793 Olli Hauer changed: What|Removed |Added Resolution|--- |FIXED Status|In Progress

[Bug 204793] www/mod_python35: Fatal Python error: PyEval_SaveThread: NULL tstate

2016-03-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204793 Kubilay Kocak changed: What|Removed |Added Keywords|needs-patch, needs-qa |patch Resolution|FIXED

[Bug 204793] www/mod_python35: Fatal Python error: PyEval_SaveThread: NULL tstate

2016-03-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204793 --- Comment #10 from commit-h...@freebsd.org --- A commit references this bug: Author: ohauer Date: Tue Mar 15 14:02:10 UTC 2016 New revision: 411163 URL: https://svnweb.freebsd.org/changeset/ports/411163 Log: - update patch to reflect l

[Bug 204793] www/mod_python35: Fatal Python error: PyEval_SaveThread: NULL tstate

2016-03-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204793 Olli Hauer changed: What|Removed |Added Resolution|--- |FIXED Status|New

[Bug 204793] www/mod_python35: Fatal Python error: PyEval_SaveThread: NULL tstate

2016-01-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204793 SBB changed: What|Removed |Added Attachment #165267|0 |1 is obsolete|

[Bug 204793] www/mod_python35: Fatal Python error: PyEval_SaveThread: NULL tstate

2016-01-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204793 --- Comment #7 from SBB --- (In reply to Kubilay Kocak from comment #6) Ok, I will give that a try today or tomorrow. Thanks for explaining this and your patience! -- You are receiving this mail because: You are on the CC list for the bu

[Bug 204793] www/mod_python35: Fatal Python error: PyEval_SaveThread: NULL tstate

2016-01-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204793 --- Comment #6 from Kubilay Kocak --- (In reply to SBB from comment #5) That's a great effort (and correct, for a patch against the upstream sources), though what is preferable is a patch against the port itself, creating a files/patch-* f

[Bug 204793] www/mod_python35: Fatal Python error: PyEval_SaveThread: NULL tstate

2016-01-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204793 --- Comment #5 from SBB --- Created attachment 165267 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165267&action=edit Do not import site.py patch I'm not 100% sure if this is what you are asking for as this is my first time po

[Bug 204793] www/mod_python35: Fatal Python error: PyEval_SaveThread: NULL tstate

2016-01-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204793 Kubilay Kocak changed: What|Removed |Added See Also||https://github.com/grisha/m

[Bug 204793] www/mod_python35: Fatal Python error: PyEval_SaveThread: NULL tstate

2016-01-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204793 --- Comment #3 from SBB --- The fix committed here seems to have fixed the problem. I've been running a patched version for a month now with out issue. https://github.com/grisha/mod_python/commit/5bb5d6d0113f6bbd72966a5c1f3e6d40c2e9c8fd -

[Bug 204793] www/mod_python35: Fatal Python error: PyEval_SaveThread: NULL tstate

2015-11-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204793 --- Comment #2 from SBB --- Ah, yes, I saw that issue as well but forgot to mention it. I've posted my information there as well. I'm not sure exactly how to get a backtrace, ie what commands to run but simply running "gdb /usr/local/sbin/

[Bug 204793] www/mod_python35: Fatal Python error: PyEval_SaveThread: NULL tstate

2015-11-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204793 Kubilay Kocak changed: What|Removed |Added CC||pyt...@freebsd.org Keywo