-
Notifications
You must be signed in to change notification settings - Fork 91
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
Why GELFHandler is deprecated? #105
Comments
Sorry for breaking compatibility, Note: Similar changes were done with Any version of graypy 0.X.X should support the old definition of |
@Urahara see #106 for a possible solution to improve backwards compatibility from 0.3.X to 1.X.X. Though I'm not 100% sold on adding back class aliases that are immediately deprecated and are likely to be removed anyways within the future. If demand is high enough I can implement these changes, but, otherwise it might be easier to either update your older projects, or simply lock requirements of graypy to 0.3.X. |
@nklapste Thanks for clarify! What surprised me was that there were several releases in the last few days and i didn't know where these changes occurred. I think it would be nice to have this backward compatibility like you implemented on #106 using |
@Urahara The removal of Adding backwards compatibility for However, a similar case for |
I understand, but i think that who is having issues with |
Looking at the changes needed to accommodate backporting (see #108 and #106) and how they directly invalidate the API breaking notation of bumping graypy's version to 1.X.X. I think its better to not resolve the breaking changes introduced 1.X.X. Additionally, since in graypy 0.3.X If you wish to still use the |
I just run pip install graypy today on new machine that i using and them a get this error on older project.
The text was updated successfully, but these errors were encountered: