-
Notifications
You must be signed in to change notification settings - Fork 125
Python Buffer Protocol #1502
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: RB-10.6
Are you sure you want to change the base?
Python Buffer Protocol #1502
Conversation
|
I don't have a solution for the test failures in the Linux debug build, but I do have some information about it. If I comment out cortex/include/IECore/TypeTraits.h Line 39 in 650eabf
A bunch of others will break from removing that include, but it's something to go on. I also tried commenting out individual specializations in I'm guessing it's some kind of optimization issue between debug and release builds, but beyond that hunch I'll have to keep poking at it and see what happens. |
|
Oh, one more piece of information. If I go back to only the first commit, 20550fb, the tests pass. If I simply add Then if I remove one of the two pairs of specializations at cortex/include/IECore/HalfTypeTraits.h Lines 88 to 98 in 650eabf
it passes again. But if I try that trick with the full set of commits, where |
fd98b45 to
6dfdc6f
Compare
This adds a new lightweight buffer object to
IECorePythonwhich supports Python's buffer protocol.The buffer can be obtained from numeric-based
*VectorDatatypes with read-only or read-write access. Read-only buffers are advantageous because they will not need to make copies of the underlying data that read-write buffer may need to do forTypedDatacopy-on-write functionality.Types that act as a consumer for Python's buffer protocol include Python's native
memoryviewobject and Numpy'sndarrayobject.Checklist