There are two instances where input() is used for user interaction (specifically in the LoginTwoFactorAuthChallenge and LoginAcid subtasks). These calls are synchronous, which causes issues when trying to use the library in an asynchronous environment.
Since the library is largely asynchronous, blocking input operations (like input()) break the flow when using it in modern async workflows. It would be beneficial to update these input() calls to non-blocking async input() calls or use another async-friendly input handling mechanism.
Affected Areas:
LoginTwoFactorAuthChallenge subtask: Uses input() to request a TOTP or 2FA code from the user.
LoginAcid subtask: Uses input() to request further authentication (e.g., via email or phone).
Suggested Solution:
Replace the synchronous input() calls with an asynchronous input mechanism.
Use asyncio or an async-compatible function to collect user input without blocking the event loop.
ugsystem
commented
2 days ago
There are two instances where
input()is used for user interaction (specifically in the LoginTwoFactorAuthChallenge and LoginAcid subtasks). These calls are synchronous, which causes issues when trying to use the library in an asynchronous environment.Since the library is largely asynchronous, blocking input operations (like input()) break the flow when using it in modern async workflows. It would be beneficial to update these input() calls to non-blocking async input() calls or use another async-friendly input handling mechanism.
Affected Areas:
Suggested Solution: