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 2017-03-15 02:40 by MSeifert, last changed 2022-04-11 14:58 by admin. This issue is now closed.
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-11 14:58:44 | admin | set | github: 73999 |
2017-03-16 02:53:00 | MSeifert | set | messages: + msg289703 |
2017-03-15 04:25:20 | rhettinger | set | status: open -> closed resolution: not a bug messages: + msg289639 stage: resolved |
2017-03-15 04:17:32 | xiang.zhang | set | nosy:
+ rhettinger |
2017-03-15 04:08:48 | MSeifert | set | messages: + msg289638 |
2017-03-15 03:36:38 | xiang.zhang | set | nosy:
+ xiang.zhang messages: + msg289636 |
2017-03-15 02:41:35 | MSeifert | set | title: PyTuple_GetSlice documentation incorrect -> PyTuple_GetSlice does not always return a new tuple |
2017-03-15 02:40:50 | MSeifert | create |