-
Type: New Feature
-
Resolution: Unresolved
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
With the standardization of the syntax for asynchronous programming in Python, it should now be relatively simple to remove the motor_asyncio and motor_tornado submodules that create framework-specific Motor classes at import-time. Instead, we should provide a single, unified API to create framework-specific Motor classes; something like:
client = MotorClient.with_framework(asyncio)(connection_string, **kwargs)
- related to
-
MOTOR-586 Define an abstract class that defines an interface for integrating more frameworks
- Backlog