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 memeplex
Recipients amaury.forgeotdarc, belopolsky, eryksun, meador.inge, memeplex
Date 2016-06-09.15:47:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1465487275.01.0.436194355819.issue27274@psf.upfronthosting.co.za>
In-reply-to
Content
> The first argument can be any type accepted by c_void_p.from_param, such as a ctypes pointer/array, str, bytes, or an integer address.

Now I see why you suggested ptr.as_void in 26565. Both issues are very related. Some functions are overloaded in the sense they automatically call c_void_p.from_param on their arguments; other functions aren't. Uniformity would dictate to treat all functions expecting an address the same way. Anyway this would not cover all use cases for ptr.toaddress or ptr.as_void or whatever it gets called.
History
Date User Action Args
2016-06-09 15:47:55memeplexsetrecipients: + memeplex, amaury.forgeotdarc, belopolsky, meador.inge, eryksun
2016-06-09 15:47:55memeplexsetmessageid: <1465487275.01.0.436194355819.issue27274@psf.upfronthosting.co.za>
2016-06-09 15:47:54memeplexlinkissue27274 messages
2016-06-09 15:47:54memeplexcreate