-
-
Notifications
You must be signed in to change notification settings - Fork 58
Filter warning for batched_dot until we change it #455
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
Conversation
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.
LGTM
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.
Don't filter ignore on the tests but when calling the function internally. Users shouldn't see warnigs they have no control over (that's why we fail on the tests)
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.
looks good if tests pass. Why are we calling compile_pymc though? That's just a name change... People seem to be getting the point of deprecation warning wrong :)
Does a name change not warrant a DeprecationWarning? What else would we use
if we intend to remove `compile_pymc` eventually?
…On Sat, 12 Apr 2025, 16:30 Ricardo Vieira, ***@***.***> wrote:
***@***.**** approved this pull request.
looks good if tests pass. Why are we calling compile_pymc though? That's
just a name change... People seem to be getting the point of deprecation
warning wrong :)
—
Reply to this email directly, view it on GitHub
<#455 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAACCUIVMT3SAY4M44V2ECD2ZEPPBAVCNFSM6AAAAAB277PCCCVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDONRSGE3TGMZUHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Yes it warrants, but here in extras we should just have updated, not ignored it. That's a silly reaction to the warning |
They are updated in #453
…On Sat, 12 Apr 2025, 17:11 Ricardo Vieira, ***@***.***> wrote:
Yes it warrants, but here in extras we should just have updated, not
ignored it. That's a silly reaction to the warning
—
Reply to this email directly, view it on GitHub
<#455 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAACCUNUHYXGIUEC76YL3ID2ZEUKJAVCNFSM6AAAAAB277PCCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJYHA3DQNJWGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
*ricardoV94* left a comment (pymc-devs/pymc-extras#455)
<#455 (comment)>
Yes it warrants, but here in extras we should just have updated, not
ignored it. That's a silly reaction to the warning
—
Reply to this email directly, view it on GitHub
<#455 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAACCUNUHYXGIUEC76YL3ID2ZEUKJAVCNFSM6AAAAAB277PCCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOOJYHA3DQNJWGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
While we figure out how to remove deprecated functionality in #453 this PR should get
main
building properly again!