Erik Cederstrand
Erik Cederstrand
Hi Ram, See my comment in https://github.com/AutoViML/featurewiz/issues/112#issuecomment-2120340238 for a motivation. Thanks!
No longer using this package. Closing.
If you need to customize the way `exchangelib` handles connections, you should create a custom HTTP adapter for `requests`. There's documentation for that at https://ecederstrand.github.io/exchangelib/#proxies-and-custom-tls-validation
I would suggest asking in a forum dedicated to `requests` instead. This is outside the scope of exchangelib as such.
Closing as this issue concerns configuration or extension of `requests`, not `exchangelib`.
I believe this was fixed in exchangelib 5.4.0. See https://github.com/ecederstrand/exchangelib/issues/1301 Try upgrading and report back your findings here.
That's just your server resetting the connection. Exchange servers will do that once in a while. If you want exchangelib to handle that gracefully, then add a retry policy: https://ecederstrand.github.io/exchangelib/#fault-tolerance
Connection errors come and go. It's not necessarily correlated with you installing different versions of exchangelib. Unless this is a persistent error and you cannot get any data at all...
How does the error manifest? Did you add a retry policy? Do you have a stack trace? And does the stack trace happen before the retry policy is set to...
This solution is fine with me. My use case is a Microsoft Exchange client that needs to translate from `pytz` timezones to Windows timezone names, and I ended up storing...