-
Notifications
You must be signed in to change notification settings - Fork 18
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
0.7.0 breaking changes - compatibility tracking issue #319
Comments
Thanks for the ping @federicobond 👍 |
@federicobond thanks for the heads up, do you have any example of what tondo by any chance? |
If you are doing things like: from openfeature.api import EvaluationContext You will have to change it to point to the canonical location: from openfeature.evaluation_context import EvaluationContext Easiest way to check support is running |
@jonathannorris FYI |
…#319 Signed-off-by: Thomas Poignant <thomas.poignant@gofeatureflag.org>
It should be ok for GO Feature Flag, waiting for the SDK to be released to release the new version of the provider. |
@federicobond do you know when v0.7.0 will be released? |
Thanks for the heads up. I just cut the 0.7.0 release! 🎉 |
* Stop using provider.provider as mentionned in open-feature/python-sdk#319 Signed-off-by: Thomas Poignant <thomas.poignant@gofeatureflag.org> * Remove usage of status Signed-off-by: Thomas Poignant <thomas.poignant@gofeatureflag.org> * remove unused init Signed-off-by: Thomas Poignant <thomas.poignant@gofeatureflag.org> --------- Signed-off-by: Thomas Poignant <thomas.poignant@gofeatureflag.org>
See upstream related issue open-feature/python-sdk#319
* Stop using provider.provider as mentionned in open-feature/python-sdk#319 Signed-off-by: Thomas Poignant <thomas.poignant@gofeatureflag.org> * Remove usage of status Signed-off-by: Thomas Poignant <thomas.poignant@gofeatureflag.org> * remove unused init Signed-off-by: Thomas Poignant <thomas.poignant@gofeatureflag.org> --------- Signed-off-by: Thomas Poignant <thomas.poignant@gofeatureflag.org>
With 0.7.0, we are taking a more strict approach to exporting names in our public API. In #306 we began using
__all__
inside each package to explicitly declare the names that are exported from it, thus enforcing a canonical import path for each class/function.Package maintainers: if you were previously importing names from non-canonical locations, you will need to update your imports to point to the canonical ones. Your code should then be able to work with both current and 0.7.0 SDK versions.
We will be releasing 0.7.0 next week probably, and we will be following it up with a 1.0 shortly after 🎉
If you have any other questions, feel free to leave a comment here.
Packages that may need updating
The text was updated successfully, but these errors were encountered: