-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] Drop txmongo support? #381
Comments
Hi. If you think you can fix txmongo easily and get away with it for a few months, then it may be worth doing. But otherwise, let's not carry the burden of a lib that is not actively maintained. Since dropping it would be a breaking change, you may want to ship a major release. Time to see what other issue we could cram in there (probably none). Or maybe just don't bother, pin the pymongo version in the tests and ensure CI runs on appropriate MongoDB version if that is not too hard. And yes, as you said, add a deprecation notice for future removal, so we get to see if someone takes over txmongo development. If nobody does, then dropping it is the way to go. |
We're (maintainers) still around, just had a lot of life issues in the way. We do accept PRs. We're now in the process of migrating away from travis-ci to github actions. We also have support for later versions of mongodb in the works as well. |
twisted/txmongo#290 merged; will release soon. |
It seems txmongo is increasingly hard to support.
txmongo
cannot be imported withpymongo >= 4
(see twisted/txmongo#278)Even if the import issues are fixed,
txmongo
internally uses anOP_QUERY
command which is incompatible with Mongo server instances >= 6.0 (see https://www.mongodb.com/docs/manual/reference/mongodb-wire-protocol/#footnote-op-query-footnote).txmongo
is not actively developed.Should txmongo support remain, or just be deprecated?
The text was updated successfully, but these errors were encountered: