[SDK-39]: Changed to version 2.0.0, after addition of X-SDK headers #6
Conversation
…and added keywords. Similar to the .NET version, I decided to be consistent with that - even though we've changed the name of the package, there is a smaller chance of confusion if we bump the version to 2.0.0
|
I'll change the readme in this PR too, so I'll be adding at least another commit to it |
|
I'll also change the install command which is in the integration guide documentation once the package has been published |
|
Having the version number consistent across the SDKs would be ideal, but I think it's quite hard to achieve, especially since we will have bugfix releases for individual issues. I'm not that bothered about it. |
|
It wasn't really the version number consistent across the SDKs that I was talking about - that would be very hard to do! I was talking about the consistency (with .NET) in naming this version 2.0.0, even though technically it could be 1.0.0, as it's a new package. |
|
Removed my commit from master. It has already been pulled into this branch. It looks a bit weird to me, but hopefully, it's all good now. There are also a few references to the old package name in the examples. |
|
I've added requirements changes for the example projects in that last commit. There are instances of import "yoti_python_sdk" in the README and the example projects, but these refer to the internal folder name in the project. |
|
After having a lot of issues with uploading the new package (SO Issue , |
Changed to version 2.0.0, after addition of X-SDK headers and added keywords. Similar to the .NET version, I decided to be consistent with the versioning there - even though we've changed the name of the package and could feasibly start at 1.0.0 as it's a new package, there is a smaller chance of confusion if we use 2.0.0. I'll publish the package once this change is approved.