I have completed this prep on branch `dw/8565` However, these updates were made in concert with pre-release Ming changes. We shouldn't merge this branch until a new version of Ming has been published that includes its own API migration prep.
--- **[tickets:#8565] Prepare for Upgrade to Pymongo 4** **Status:** open **Milestone:** unreleased **Created:** Thu Jun 27, 2024 07:56 PM UTC by Dillon Walls **Last Updated:** Thu Jun 27, 2024 07:58 PM UTC **Owner:** Dillon Walls There are quite a few methods that were removed or changed in the jump from pymongo3 to pymongo4. Many of these have been back-ported to pymongo3. In coordination with Ming, we should incrementally work towards pymongo4. A good way to accomplish this is to keep pymongo3 but migrate to the new api in as many places as possible. --- Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
