- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message403347
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.
| Author | shihai1991 |
|---|---|
| Recipients | petr.viktorin, seberg, shihai1991 |
| Date | 2021-10-07.03:06:19 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1633575979.66.0.515480285344.issue45315@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
> the simplest solution is calling `type_set_name`, even if that runs some unnecessary checks. Hm, I haven't find any case who use dynamical tp_name of Type_Spec temporarily. If we meet this user case, Adding a new object pointer of type name in is an other option maybe:) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2021-10-07 03:06:19 | shihai1991 | set | recipients: + shihai1991, petr.viktorin, seberg |
| 2021-10-07 03:06:19 | shihai1991 | set | messageid: <1633575979.66.0.515480285344.issue45315@roundup.psfhosted.org> |
| 2021-10-07 03:06:19 | shihai1991 | link | issue45315 messages |
| 2021-10-07 03:06:19 | shihai1991 | create | |

