[issue11329] PyEval_InitThreads() not safe before Py_Initialize()

2011-02-26 Thread Juraj Ivancic

New submission from Juraj Ivancic :

It seems that PyEval_InitThreads() can no longer be called before
Py_Initialize(). I get a fatal error in PyThreadState_GET().
This contradicts the documentation

http://docs.python.org/release/3.2/c-api/init.html#PyEval_InitThreads

Minimal repro:

#include "Python.h"
int main()
{
 PyEval_InitThreads();
 return 0;
}

Everything works if Py_Initialize() is called first.

--
components: Interpreter Core
messages: 129515
nosy: Juraj.Ivancic
priority: normal
severity: normal
status: open
title: PyEval_InitThreads() not safe before Py_Initialize()
type: crash
versions: Python 3.2

___
Python tracker 
<http://bugs.python.org/issue11329>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue22223] argparse not including '--' arguments in previous optional REMAINDER argument

2014-08-20 Thread Juraj Ivancic

Changes by Juraj Ivancic :


--
nosy: +Juraj.Ivancic

___
Python tracker 
<http://bugs.python.org/issue3>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com