Closed ethanbb closed 6 months ago
Can you tell me what version of ipyparallel you have? I'm going to look over changes to the APIs to see if they may have changed it.
This was on version 8.7.0.
Given that we're sorting it right after, I don't think there's a good reason for that not to be map_sync; it's unfortunate that the async object doesn't implement the rest of a map api by immediately loading everything if a call requires everything. Maybe it did that in the past, but the level of inheritance used in ipyparallel makes looking over various versions of the package a lot of work.
The return value for map_sync should be sortable. If you'd like to turn this into a PR after verifying it fixes the issue, that'd be great, but if you'd rather me do it, that's also fine.
OK thanks, let me verify and let you know. I know what you mean about looking over the ipyparallel code...it's not very readable.
All good, submitted the PR.
Your setup:
I'm getting the following error when running CNMF with ipyparallel:
This seems to be because of the following code in
cnmf/spatial.py
, which callsmap_async
on the dview and then tries to sort the return value:I think most of the other code uses
map_sync
for the ipyparallel case - is that what was intended here? Oddly, this code doesn't seem to have changed recently; seems like someone would have run into this already.