Increased python functionality #1
Conversation
This includes an API change: `assembler.python_processor` which was a `processor` object has been replaced by `assembler.python_processors` which is a list. Python processors are run sequencially, not on separate threads.
|
@kmsmith137 There are two sketchy things in this PR that you might be able to comment on. The first is a const_cast of the chunks packed data so I can wrap that data in an array. The second is that I don't fully understand how the memory management of the chunk's byte data works. I'm worried that the memory might be deallocated before the numpy array goes out of scope. This shouldn't be an issue in the current code since the python side is strictly sequential, however it might not be future proof. Both concerns are described in more detail in comments in the source. |
|
@kmsmith137 bump Some ARO folks have been looking at this and getting confused about versions, so I think we should converge on this ASAP. |
|
Also @misanthropealoupe, this is what I was referring to in my email. |
No description provided.