You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm tempted to just stop trying to handle inline magic, it's too complicated and unreliable and they don't come up particularly often anyway. Will try to get something together at the weekend
The text was updated successfully, but these errors were encountered:
Not sure about how much of a performance impact it would be, but a possibly more robust way to check if a cell contains magic might be to call IPythonInputSplitter().transform_cell on the whole cell, check if the source changed and only handle it differently if it does.
I'm pretty tempted to just ignore any cell which contains line magics and just treat that as a known limitation
I think I was being overly negative when I wrote that - in #595, we can handle cells with line magics and handle this bug. It does mean giving up on checking Python code within a line magic command, but that's a limitation I'm happy to live with for now
xref yt-project/yt#3287 :
I'm tempted to just stop trying to handle inline magic, it's too complicated and unreliable and they don't come up particularly often anyway. Will try to get something together at the weekend
The text was updated successfully, but these errors were encountered: