-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
some methods of uninitialized io.IncrementalNewlineDecoder objects raise SystemError #75899
Comments
Given an uninitialized IncrementalNewlineDecoder: each of the following calls would raise a SystemError ('null argument to In contrast, the following call would raise a ValueError ISTM that getstate(), setstate(), and reset() should have the same behavior as |
Is IncrementalNewlineDecoder subclassable? |
Yes, although i don't know if there are usecases for that. |
There is other issues with IncrementalNewlineDecoder.__init__ -- it leaks references when called repeatedly. The simplest solution of both issues will be moving the initialization to the new method. But this class looks designed for subclassing, and this can break subclasses that change arguments before passing them to the superclass' constructor. |
With regard to refleaks in __init__() methods, i started looking for similar refleaks |
The patch for this issue had some outstanding questions/changes to be made before being merged, but now a new PR needs to be opened to replace the original one. Anyone who is interested can pick this up, but please only open one PR for this and please also credit the original author as per the dev guide. Thank you! |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: