Repository navigation
weakref: treat explicit None callback as no callback - #8298
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
📝 WalkthroughWalkthrough
ChangesWeak reference callback handling
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
📦 Library DependenciesThe following Lib/ modules were modified. Here are their dependencies: [x] lib: cpython/Lib/weakref.py dependencies:
dependent tests: (222 tests)
Legend:
|
youknowone
left a comment
There was a problem hiding this comment.
I expected to use and_then, but looks reasonable. Thanks!
Summary
weakref.ref(obj, None)being treated as having a callback instead of no callback.test_shared_ref_without_callback, which was previously marked@unittest.expectedFailuredue to this bug.Summary by CodeRabbit
Nonecallback as no callback.