Message280908
| Author |
josh.r |
| Recipients |
josh.r |
| Date |
2016年11月16日.02:07:57 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1479262078.78.0.696001774496.issue28709@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
On further checking, looks like there is a lot of work that should be done to initialize heap types (see PyType_FromSpecWithBases) that PyStructSequeuence_Init2 doesn't do (because it thinks it's working on a static type). I think the solution here is decouple PyStructSequeuence_NewType from PyStructSequeuence_Init2 (or to minimize code duplication, make both of them call a third internal function that accepts additional flags, e.g. to make the type a HEAPTYPE, BASETYPE, or both, and performs the additional work required for those flags if given); Init2 clearly expects a static type, and definitionally, NewType is producing a heap/dynamic type. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2016年11月16日 02:07:58 | josh.r | set | recipients:
+ josh.r |
| 2016年11月16日 02:07:58 | josh.r | set | messageid: <1479262078.78.0.696001774496.issue28709@psf.upfronthosting.co.za> |
| 2016年11月16日 02:07:58 | josh.r | link | issue28709 messages |
| 2016年11月16日 02:07:57 | josh.r | create |
|