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 Mason.Bially
Recipients Mason.Bially, amaury.forgeotdarc, gholling, theller
Date 2013-09-27.20:51:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I agree with Amaury that this is purely a user side concern. While I think it's important to note the behaviour of ctypes in the case that Thomas describes, I believe it's more important to fully support the range of behaviours allowed by C function callbacks.

I see the use cases for complex return types that don't fall under the concerns raised by Thomas as the following:

* Returning a pointer to already existing memory.
* Returning complex value types (structs of ints, doubles, chars, ect). This is especially important from a compatibility standpoint for C libraries which expect such return types.

Because I need this for my current project I will work on writing a patch.
Date User Action Args
2013-09-27 20:51:28Mason.Biallysetrecipients: + Mason.Bially, theller, amaury.forgeotdarc, gholling
2013-09-27 20:51:28Mason.Biallysetmessageid: <>
2013-09-27 20:51:28Mason.Biallylinkissue5710 messages
2013-09-27 20:51:28Mason.Biallycreate