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
Updated incorrect level-setting code to use setLevel(). #16325
Conversation
Thanks @vsajip for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7. |
Thanks @vsajip for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8. |
I'm having trouble backporting to |
GH-16326 is a backport of this pull request to the 3.7 branch. |
(cherry picked from commit 1d094af) Co-authored-by: Vinay Sajip <vinay_sajip@yahoo.co.uk>
Thanks @vsajip for the PR 🌮🎉.. I'm working now to backport this PR to: 3.8. |
(cherry picked from commit 1d094af) Co-authored-by: Vinay Sajip <vinay_sajip@yahoo.co.uk>
GH-16327 is a backport of this pull request to the 3.8 branch. |
Apparently .level is not even a property and I guess starting from 3.7 treatment has changed, or broke. May be smth like (scheduled for 3.9 with backport requests for 3.8) python/cpython#16325 was intended to fix it, I did not investigate deep enough -- just fixed the issue we started to experience (Closes datalad#3545)
Apparently .level is not even a property and I guess starting from 3.7 treatment has changed, or broke. May be smth like (scheduled for 3.9 with backport requests for 3.8) python/cpython#16325 was intended to fix it, I did not investigate deep enough -- just fixed the issue we started to experience (Closes #3545) CPed from DataLad: https://patch-diff.githubusercontent.com/raw/datalad/datalad/pull/3935.patch
No description provided.