René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"No async version of .authenticate()","articleBody":"It looks like there's no `.authenticate_async()`, just a normal `.authenticate()` method in the API client.\n\nThus, if you want to use the client in an async codebase, you should run the authentication code in a synchronous context and only after authenticating the client you should switch back to running async code (unless you can afford to get the event loop stuck for the duration of the authentication, which shouldn't happen frequently). This might be doable at least in some codebases, but makes the usage a bit more cumbersome than if there was an async function available for authenticating. What's worse is that the `.call_async` also might call the the non-async `.authenticate()` if you have not yet authenticated the client (solvable by authenticating beforehand) or if there's an error (didn't check deep enough to be 100% sure, but I think this is what happens if the authentication has expired, so this would be a bit harder to prevent). So there's async code that might reach out to the non-async version of `.authenticate()` that does network access.\n\nAdding an async version of the `.authenticate()`, like `.authenticate_async()` should be somewhat simple to do and make it a lot easier to use the client in some cases and most importantly avoid accidentally getting the event loop stuck if there's a need to re-authenticate when making some call.","author":{"url":"https://github.com/joakimnordling","@type":"Person","name":"joakimnordling"},"datePublished":"2025-08-11T11:56:46.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/128/mygeotab-python/issues/128"}