You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pin pyop to the latest version of PyMongo 3.x until it has completely
migrated to PyMongo 4. Most of the key new methods and options from
PyMongo 4.0 are backported in PyMongo 3.12, making migration much
easier.
ClosesIdentityPython#51
Pin pyop to the latest version of PyMongo 3.x until it has completely
migrated to PyMongo 4. Most of the key new methods and options from
PyMongo 4.0 are backported in PyMongo 3.12, making migration much
easier.
Closes#51
TL;DR—Work around this problem by installing
pymongo==3.13
after installing pyop.PyMongo 3 depreciated
MongoReplicaSetClient
, and PyMongo 4 removed it (cf. https://github.com/mongodb/mongo-python-driver/blob/master/doc/migrate-to-pymongo4.rst). However, pyop still refers toMongoReplicaSetClient
, causing pyop to throw an AttributeError when configured to use a clustered MongoDB instance.For example, I'm using pyop via SATOSA's openid_connect_frontend with an Amazon DocumentDB cluster (cf., https://github.com/IdentityPython/SATOSA/blob/master/doc/one-to-many.md, https://github.com/IdentityPython/SATOSA/blob/master/example/plugins/frontends/openid_connect_frontend.yaml.example, and https://docs.aws.amazon.com/documentdb/latest/developerguide/connect_programmatically.html). The database URI looks something like this:
However, when SATOSA starts, I get the following error:
Downgrading to PyMongo 3.13 works around this problem. Long term, pyop should migrate to PyMongo 4 or newer.
The text was updated successfully, but these errors were encountered: