Issue 919299: API Ref: PyErr_SetInterrupt not Obsolete (original) (raw)
Issue919299
This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.
This issue has been migrated to GitHub: https://github.com/python/cpython/issues/40051
classification
Title: | API Ref: PyErr_SetInterrupt not Obsolete | ||
---|---|---|---|
Type: | Stage: | ||
Components: | Documentation | Versions: | Python 2.3 |
process
Status: | closed | Resolution: | fixed |
---|---|---|---|
Dependencies: | Superseder: | ||
Assigned To: | fdrake | Nosy List: | fdrake, kbk |
Priority: | normal | Keywords: | patch |
Created on 2004-03-19 06:21 by kbk, last changed 2022-04-11 14:56 by admin. This issue is now closed.
Files | |||
---|---|---|---|
File name | Uploaded | Description | Edit |
exceptions.tex.patch | kbk,2004-03-19 06:21 | Initial Exceptions Patch |
Messages (3) | ||
---|---|---|
msg45606 - (view) | Author: Kurt B. Kaiser (kbk) * ![]() |
Date: 2004-03-19 06:21 |
The API document Section 4. claims that this function is obsolete, but it is used in thread.interrupt_main(), which in turn is used in IDLE. Attached patch removes the 'obsolete' statement. If there is some reason that it is going to disappear, then we have to figure something out for thread.interrupt_main. | ||
msg45607 - (view) | Author: Fred Drake (fdrake) ![]() |
Date: 2004-03-25 14:37 |
Logged In: YES user_id=3066 Fixed in Doc/api/exceptions.tex 1.17. Someone should backport the change to Python 2.3.x and close this bug report. | ||
msg45608 - (view) | Author: Fred Drake (fdrake) ![]() |
Date: 2004-05-12 03:23 |
Logged In: YES user_id=3066 Fixed wording on trunk in Doc/api/exceptions.tex 1.18, backported the final fix for Python 2.3.4 as revision 1.15.10.2. |
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-11 14:56:03 | admin | set | github: 40051 |
2004-03-19 06:21:48 | kbk | create |