Closed belm0 closed 3 years ago
after disabling the numba dependency, other imports fail oddly under jit-no-frame, so this probably isn't too specific to numba
File "/home/dev/.local/lib/python3.8/site-packages/asks/sessions.py", line 294, in _handle_exception
await sock.close()
File "/home/dev/.local/lib/python3.8/site-packages/anyio/_networking.py", line 211, in close
from . import move_on_after
ImportError: cannot import name 'move_on_after' from 'asks' (/home/dev/.local/lib/python3.8/site-packages/asks/__init__.py)
As you mentioned no-frame mode is very experimental. In fact we recently concluded we can't quite make it work as-is for our needs. Instead we've shifted to working on -X jit-shadow-frame
which seems to get about the same perf wins but has a little bit of extra overhead to keep track of the call-stack for things like unwinding, stack-traces etc. You could try it now, but again this is super experimental and we're not using it in production yet. I'd suggest you check-in again on this in about a month or so.
(noted that cinder jit is experimental, and jit-no-frame is more experimental) (also, it's silly to have multiple jitters going on, and we want to exorcise numba from our app dependencies)
things are fine with plain jit:
import problem with jit-no-frame:
numba version: 0.51.2