That would be nice. Unfortunately, PyMongo 2.x used **kwargs as a parameter
to Cursor to pass some undocumented internal options. Doing validation of
unknown options might be ugly, and 2.8 is no longer being developed. You
can read the API docs for the 2.8 series here:
PyMongo 2.9.x actually supports no_cursor_timeout. That release series was
meant to be a migration path to PyMongo 3.x. At some point Motor will
migrate to PyMongo 3.0, but it's not a high priority for us right now.
On Friday, April 15, 2016 at 9:32:38 AM UTC-7, a_l wrote:
Thanks. Should there have been an error on specification of the parameter,
it did take me a long while to isolate the issue down to the driver due to
the nature of the problem (and because the driver is so consistent
I'm using motor, which has an explicit requirement for pymongo to be at
You received this message because you are subscribed to the Google Groups "mongodb-user"