pymongo compatibility broken with version 2.3
Hello, I know this is not particular subject for this mailing list, but this info might help someone else using pymongo for mongodb with pypy. --- Latest release of the mongodb driver, pymongo (version 2.3, off 29th, August) does not work anymore with Pypy 1.9 and fails to start up with something like this: " (env) D:\gg_webdev>pypy dbskin.py Fatal Python error: PyThreadState_Get: no current thread This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. " But from my code side, there is no greenlet or similar in usage. The problem just arrived when upgrading the driver. So I'm not sure whats the concrete problem with this new version - also after consulting the changelog of the driver ( https://jira.mongodb.org/browse/PYTHON/fixforversion/11146 ) there is nothing mentioned about threading or anything alike that - but it's definitely the culprid. Nevertheless, version 2.2.1 (pymongo-2.2.1_-py2.7.egg) does work like a charm. Jan
On Thu, Aug 30, 2012 at 12:45 PM, Jan Riechers <janpeterr@freenet.de> wrote:
Hello,
I know this is not particular subject for this mailing list, but this info might help someone else using pymongo for mongodb with pypy.
---
Latest release of the mongodb driver, pymongo (version 2.3, off 29th, August) does not work anymore with Pypy 1.9 and fails to start up with something like this:
" (env) D:\gg_webdev>pypy dbskin.py Fatal Python error: PyThreadState_Get: no current thread
This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. "
But from my code side, there is no greenlet or similar in usage. The problem just arrived when upgrading the driver.
So I'm not sure whats the concrete problem with this new version - also after consulting the changelog of the driver ( https://jira.mongodb.org/browse/PYTHON/fixforversion/11146 ) there is nothing mentioned about threading or anything alike that - but it's definitely the culprid.
Nevertheless, version 2.2.1 (pymongo-2.2.1_-py2.7.egg) does work like a charm.
Jan _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
It's clearly doing something with CPython C API. Is it the default behavior? Cheers, fijal
2012/8/30 Jan Riechers <janpeterr@freenet.de>:
(env) D:\gg_webdev>pypy dbskin.py Fatal Python error: PyThreadState_Get: no current thread
This error message does not appear anywhere in pypy code, it certainly comes from CPython... This message is typical of an extension module that was not recompiled for pypy; it still links with python27.dll, and the call to PyThreadState_Get() jumps into an uninitialized CPython interpreter... Extension modules need to be recompiled for pypy. -- Amaury Forgeot d'Arc
participants (3)
-
Amaury Forgeot d'Arc -
Jan Riechers -
Maciej Fijalkowski