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 | bhy |
|---|---|
| Recipients | alexandre.vassalotti, amaury.forgeotdarc, bhy |
| Date | 2008年07月23日.17:34:58 |
| SpamBayes Score | 0.009858423 |
| Marked as misclassified | No |
| Message-id | <1216834500.93.0.299217947817.issue3208@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I think there is reason that CFunctionObjects are immutable: single CFunctionObject is shared by mutiple Python interpreters, so any change of CFunctionObject would affect other Python interpreters. Is that right? If it should be immutable, then we should use something like static array to assign annotations to CFunctionObject, and the value also should be immutable, that means the value couldn't be abitrary PyObject. (by value I mean the value of every __annotations__ dict items.) For SWIG, there's a way to bypass the Python side proxy, eg. for a simple C function, in the shadow module we directly let 'func=_cmod.func', where _cmod is the C DLL module. So the annotation information would be lost if we can't directly assign annotation to C function. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月23日 17:35:01 | bhy | set | spambayes_score: 0.00985842 -> 0.009858423 recipients: + bhy, amaury.forgeotdarc, alexandre.vassalotti |
| 2008年07月23日 17:35:01 | bhy | set | spambayes_score: 0.00985842 -> 0.00985842 messageid: <1216834500.93.0.299217947817.issue3208@psf.upfronthosting.co.za> |
| 2008年07月23日 17:35:00 | bhy | link | issue3208 messages |
| 2008年07月23日 17:34:59 | bhy | create | |