Uploaded image for project: 'Motor'
  1. Motor
  2. MOTOR-583

Stop returning futures from Motor methods

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • 4.0
    • Affects Version/s: None
    • Component/s: None
    • None

      We should re-write methods that currently return futures as async def functions that return a value. Doing so usually results in a backward-breaking API change as the new return value can no longer be canceled, for example, which is why this must be done in Motor 3.0.

      Some examples of such methods:
      AgnosticGridOut.open()
      AgnosticBaseCursor.to_list()

            Assignee:
            Unassigned Unassigned
            Reporter:
            prashant.mital Prashant Mital (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: