-
Notifications
You must be signed in to change notification settings - Fork 607
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
Deprecate sklearn instrumentation #2708
Conversation
This is more like remove than deprecate, I was thinking that we may drop it when we remove support for python 3.8 maybe? |
This is deprecation. We no longer will publish it, but the sklearn instrumentation packages that have been published so far will continue to exist. Supporting 3.8 or not is a topic unrelated to this PR, the reason we want to deprecate this instrumentation is because the
|
Might want to include this in the CHANGELOG.md that this is deprecated at least. We do have precedence of simply deleting packages when they are being deprecated, although, we should probably be more transparent to users. #1366 |
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.
Should we remove the package from the CI in the core repo?
You are breaking current opentelemetry-bootstrap users no? It won't install the package anymore. BTW it's not that I care this specific package but would like to avoid surprises downstream :) boto instrumentation probably is in an even worse state. |
Trying to install |
It is already added. |
I'll do that ✌️ |
Fixes #2176