3.0 migration support.

    • Type: Epic
    • Resolution: Done
    • Priority: Major - P3
    • 2.9
    • Affects Version/s: None
    • Component/s: None
    • None
    • 3.0 migration support.
    • None
    • Done
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This Epic tracks the work required to make PyMongo 2.9 a migration path to PyMongo 3.0. The work will mostly involve backporting key new APIs introduced in 3.0 that replaced existing API elements in 2.x. The end result should allow applications to be written against PyMongo >= 2.9 instead of PyMongo 2.x or 3.x.

      Note that some deprecated features of PyMongo 2.x have been removed from PyMongo 3.x and no migration path will exist.

      • MasterSlaveConnection - Use replica sets instead, which now support up to 50 members.
      • request_start, request_end, in_request - Use the default write concern (w=1) instead of w=0, which is on it's last legs in MongoDB.
      • compile_re - PyMongo 3 never attempts to compile regular expressions from the server to match objects.
      • use_greenlets - Use gevent.monkey.patch_all() instead.

              Assignee:
              Bernie Hackett
              Reporter:
              Bernie Hackett
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:
                None
                None
                None
                None
                None