Message161673
| Author |
pitrou |
| Recipients |
anacrolix, neologix, pitrou, sbt |
| Date |
2012年05月26日.17:56:20 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1338054810.3332.11.camel@localhost.localdomain> |
| In-reply-to |
<1338054136.37.0.000201640149964.issue14059@psf.upfronthosting.co.za> |
| Content |
> > RawValue uses ctypes, right? That's problematic for platforms which don't
> > support ctypes.
>
> Are there many posix systems (we care about) where ctypes doesn't
> work?
It depends what you call "caring about" :-)
But proprietary Unix C compilers generally don't mix very well with
ctypes.
> It would be fairly easy to use memoryview instead of ctypes. (In fact
> Value/RawValue could be implemented that way when using a typecode
> instead of a ctypes type.)
That would be a good idea then. Also, not using ctypes could make code
theoretically more robust. |
|