You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
assignee=Noneclosed_at=<Date2010-02-22.23:49:17.948>created_at=<Date2007-08-25.11:25:16.725>labels= ['extension-modules', 'type-bug']
title='Cleanup pass on _curses and _curses_panel'updated_at=<Date2010-02-22.23:49:17.947>user='https://github.com/larryhastings'
I made a pass cleaning up _curses and _curses_panel. Mainly I cleaned
up the header file, moving unnecessary things into the two .c files.
I also changed the way information is passed from _curses to
_curses_panel. Instead of a Py_CObject which points to functions--which
Neil Norwitz suspected could be a security hole--it now passes cleaner
information (one type, one int * pointer). Finally, I made a
code-cleanup pass as per PEP-7.
Unfortunately, the patch is hard to review with all the whitespace
cleanup distracting from semantic changes. Can you produce a patch with
only those changes?
The major reason I undertook this patch was to fix the security hole of the CObject. That entire class of security holes is now fixed by the capsule object. The rest of the diffs aren't interesting enough to worry about. So I'm abandoning my patch.
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: