➜
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.
Created on 2010-11-05 23:05 by nascheme, last changed 2022-04-11 14:57 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| gc_cruft.txt | nascheme, 2010-11-05 23:05 | |||
| Messages (3) | |||
|---|---|---|---|
| msg120554 - (view) | Author: Neil Schemenauer (nascheme) *  |
Date: 2010-11-05 23:05 | |
I think it should be safe to remove some backwards compatibility cruft. This was introduced during the 2.3 development cycle. |
|||
| msg120557 - (view) | Author: Antoine Pitrou (pitrou) * |
Date: 2010-11-05 23:12 | |
Looks good to me. I suppose everything builds fine? |
|||
| msg125254 - (view) | Author: Antoine Pitrou (pitrou) * |
Date: 2011-01-04 00:02 | |
pyexpat.c needed a little fix (!). Committed in r87718, thank you! |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:08 | admin | set | github: 54542 |
| 2011-01-04 00:02:39 | pitrou | set | status: open -> closed messages: + msg125254 resolution: fixed stage: commit review -> resolved |
| 2010-11-05 23:12:56 | pitrou | set | versions:
+ Python 3.2 nosy: + pitrou messages: + msg120557 components: + Extension Modules, Interpreter Core stage: commit review |
| 2010-11-05 23:05:40 | nascheme | create | |