3 ms·
This looks incredibly useful for my current project! We have lots of arrays of objects having trajectories of different lengths to deal with, and I often end u
by radarsat1 5y ago
This looks incredibly useful for my current project! We have lots of arrays of objects having trajectories of different lengths to deal with, and I often end up having to use numpy with dtype=object, which feels, well, "awkward". It can be very hard to convince numpy arrays to have items that are actually lists, but I like using the vectorized syntax. I've found it sometimes necessary to have Pandas dataframes containing lists too, which I also find awkward.
Just a note, I noticed that there is an unfortunate error in the page describing the bike route calculations. Right in the box where it's supposed to show how much faster things are after JIT, instead a traceback is displayed ending with:
> ImportError: Numba needs NumPy 1.20 or less
I don't think this is intentional. This is in the output box just above the phrase "But it runs 250× faster than the pure Python code:". The box below it shows no timings.
I guess this is a danger of having a "live" backend to render and serve documentation.