-
Notifications
You must be signed in to change notification settings - Fork 73
V8 #55
Conversation
I still have this error sometimes:
I had three of them when running on Python 2.7 but none when running on Python 3. The
Other than that, the code changes look good. I still want to check if all the changes in We should not release a new version without writing a migration guide for the library as well. At least considering the major changes that will break existing code. |
Is this reproducible? I can't get it to fail for me... I always get If you delete |
OK, so we'll release that when we have the migration guide. |
@lefcha just to be clear: there are two migration guides. One of them is the official documentation guide for the API. |
Hm, I didn't think of a Python migration guide, as I don't remember doing one that between Basically I thought that the API doc is enough as it describes all the changes in the API, and those changes are then reflected on the way you call our API using curl or through the Python lib. The examples are also updated to reflect the changed python functions (or the new ones). |
BTW, who is supposed to write the API doc changes between v7/v8 section? Roman, or was it handed over to someone (maybe even me and I don't remember)? |
Well, it will help everyone that has a working code with the current version. Writing a migration guide will point to the changes the developer has to look into and he can refer to the documentation for that. If we don't write one, it will be trial and error for the developer.
If I remember correctly, it was part of this task. Migrate the code for v8 and document it. |
I see, I'll fill in the missing changelog and also mention in somewhere in this lib what changed in the python code. |
OK, just added a new kinda changelog file, that documents all the changes between v7 and v8 specifically for the python module. I also found a few stuff missing or not migrated, so I fixed those too. |
Here's the changelog: https://github.com/Doist/todoist-python/blob/v8/CHANGES.md |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some small comments but it looks good overall! :)
CHANGES.md
Outdated
@@ -0,0 +1,79 @@ | |||
# Changes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we call it CHANGELOG
instead of CHANGES
and also change the file name to reflect it?
CHANGES.md
Outdated
@@ -0,0 +1,79 @@ | |||
# Changes | |||
|
|||
Here follows a list of the changes between `v7` and `v8` API versions: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would use just the version number as it will be the CHANGELOG file. We can use that for future changes as well. It is something I had I my tasks for a while now.
OK, the last 3 commits should:
|
@lefcha The content of the CHANGELOG is still the same, it still mention "Changes". Not sure if something was left behind. Other than that, we should merge this. :) |
Yes, you're right the changes were there in my local repo; for some reason I missed including them. |
No description provided.