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 | rhettinger |
|---|---|
| Recipients | Rhamphoryncus, barry, brett.cannon, jlaurila, ncoghlan, rhettinger |
| Date | 2008年07月10日.10:12:32 |
| SpamBayes Score | 0.04102837 |
| Marked as misclassified | No |
| Message-id | <1215684755.14.0.0559398223919.issue3329@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I think it is reasonable to get a macro definition change into 2.6. The OP's request is essential for his application (running Python on Nokia phones) and it would be a loss to wait two years for this. Also, his request for a macro will enable another important piece of functionality -- allowing a build to intercept and instrument all calls to the memory allocator. Barry, can you rule on whether to keep this open for consideration in 2.6. It seems daft to postpone this discussion indefinitely. If we can agree to a simple, non-invasive solution while there is still yet another beta, then it makes sense to proceed. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月10日 10:12:35 | rhettinger | set | spambayes_score: 0.0410284 -> 0.04102837 recipients: + rhettinger, barry, brett.cannon, ncoghlan, Rhamphoryncus, jlaurila |
| 2008年07月10日 10:12:35 | rhettinger | set | spambayes_score: 0.0410284 -> 0.0410284 messageid: <1215684755.14.0.0559398223919.issue3329@psf.upfronthosting.co.za> |
| 2008年07月10日 10:12:33 | rhettinger | link | issue3329 messages |
| 2008年07月10日 10:12:32 | rhettinger | create | |