-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Login refused with Python 2.7 #64
Comments
Python 2 was sunsetted on Jan 1 2020 and is no longer supported - https://www.python.org/doc/sunset-python-2/ I removed Python 2 support in my fork years ago - https://github.com/moderation/garmin-connect-export Do you have enough users who can't or work upgrade to Python 3 to justify the troubleshooting time and support? |
- the script now requires Python 3.x, see #64 - the `--verbose` option now also saves some intermediate responses from Garmin
- the script now requires Python 3.x, see #64 - the `--verbose` option now also saves some intermediate responses from Garmin
Version 3.2.0 now explicitly denies working with Python 2.x If you're impacted by this change (no possibility to upgrade to Python 3.x) I'm afraid you'll have to solve/work around this issue yourself. I neither have the time nor the knowledge to make the script work again with Python 3.x and as @moderation mentioned Python 2.7 hasn't officially been supported any more for more than 18 months. |
When trying to understand #60 I noticed that the exact same login request works with Python 3.x (3.9 in my case) and fails with Python 2.7.18
With Python 2.7.18 the request for a login ticket fails with HTTP status 403 (forbidden).
Somewhere between 2021-05-09 (of when I have a log of a successful request) and 2021-05-27 (issue #60 created) something must have changed on Garmin's servers.
I'm not an expert and haven't found so far what exactly is different between HTTP requests from Python 2.7 and Python 3.x
The text was updated successfully, but these errors were encountered: