https://bugs.kde.org/show_bug.cgi?id=401512
--- Comment #6 from David E. Narvaez <david.narv...@computer.org> --- (In reply to Kevin Kofler from comment #4) > So, after looking at the code and the documentation, I suspect the issue is > not really the reference count of the tuple itself, but of the individual > arguments, which would explain why you do not hit this assertion if the > function has no arguments. I agree that the issue seems to be the refcount of the arguments, but how would you explain that the patch in comment #2 works around the issue? On a separate note, the assertion was added 3 years ago here https://github.com/boostorg/python/commit/bc2f77a3db0b3b428ef7bc205804ce5625e46001 so it seems this has been broken since Boost 1.63 or so? -- You are receiving this mail because: You are watching all bug changes.
