DeprecationWarning has unclear origin: should_run_async will not call transform_cell automatically in the future

[courtarro]

This deprecation appears when I have warnings enabled, as of some time within the past week or so, and it is unclear what its origin is. How would I go about finding what component is causing this warning to appear?

For the record, the following code causes the problem to appear:

import warnings
import pandas as pd
warnings.simplefilter('always')
pd.read_csv('filename.csv')

I could turn off warnings, obviously, but I need them for other situations. Hiding the issue doesn't really fix it, of course. I have the standard contrib notebook extensions installed also.

[Carreau]

Sorry those are just internal APIs.I transfered this issue to IPykernel repository.

[lingyunfeng]

me too

[lingyunfeng]

print ('hello')
hello
/usr/local/miconda3/envs/py37/lib/python3.7/site-packages/ipykernel/ipkernel.py:287: DeprecationWarning: should_run_async will not call transform_cell automatically in the future. Please pass the result to transformed_cell argument and any exception that happen during thetransform in preprocessing_exc_tuple in IPython 7.17 and above.
and should_run_async(code)

[lingyunfeng]

I Find a idea to this problem.

change ipkernel.py:287 line code :
#and should_run_async(code)
and should_run_async(code,transformed_cell=code)
@courtarro @Carreau

[Carreau]

and should_run_async(code,transformed_cell=code)

no, that is wrong, that will break many of the magics and specific IPython syntax.

[Carreau]

look at how IPython is doing it:

preprocessing_exc_tuple = None
        try:
            transformed_cell = self.transform_cell(raw_cell)
        except Exception:
            transformed_cell = raw_cell
            preprocessing_exc_tuple = sys.exc_info()

        ...
        elif self.should_run_async(
            raw_cell,
            transformed_cell=transformed_cell,
            preprocessing_exc_tuple=preprocessing_exc_tuple,
        ):
            ...

[lingyunfeng]

so ,I can only use 'warnings' function.
import warnings
warnings.simplefilter('once')#"error", "ignore", "always", "default", "module"

[hellodanylo]

Another workaround is to downgrade IPython to 7.10 until this issue is resolved in IPyKernel

[jckling]

Same problem here

[mattpodolak]

I got this error as well, it seems like if it's triggered once it will print out in every cell afterward.

It first occurred when printing out values from a list:

post_to_comments_list[:10]

All the following cells triggered this warning as well, including this cell:

tst_arr = [1, 2, 3]

[asford]

Does this need a owner? Would a fix for this fit in the 6.0 release timeline?

[Carreau]

#605 is not a proper fix, it re-introduces the exact bug that was painfully fixed in CLI IPython.

[Carreau]

Sorry it does not reintroduce it, the bug is still there in IPykernel ; it just mute the error message.

[gansanay]

I am still getting this warning at each cell in jupyterlab. python==3.9.2, ipykernel==5.5.3, ipython==7.21.0.

[cam4ani]

me too

[Carreau]

Do you have a file and line number for this warning ? it would be helpful to know which lines trigger it.

[stridera]

.venv/lib/python3.8/site-packages/ipykernel/ipkernel.py:283: DeprecationWarning: `should_run_async` will not call `transform_cell` automatically in the future. Please pass the result to `transformed_cell` argument and any exception that happen during thetransform in `preprocessing_exc_tuple` in IPython 7.17 and above.
  and should_run_async(code)

[gboeing]

@Carreau this warning is still appearing with ipykernel=5.5.3, ipython=7.22.0, python=3.9.2:

miniconda3/envs/ox/lib/python3.9/site-packages/ipykernel/ipkernel.py:283: DeprecationWarning: `should_run_async` will not call `transform_cell` automatically in the future. Please pass the result to `transformed_cell` argument and any exception that happen during thetransform in `preprocessing_exc_tuple` in IPython 7.17 and above.
  and should_run_async(code)

[Carreau]

@Carreau this warning is still appearing with ipykernel=5.5.3, ipython=7.22.0, python=3.9.2:

That appear to be expected, the fix in only on the master branch that will become 6.0.

[gboeing]

Ah, thanks. I see now the fix is in #617. Looking forward to it in the 6.0 release.

[vvid643]

Hi, can anyone help me with installing this commit into my already installed package?

macOS 11.3.1
ipykernel==5.5.5
ipython==7.21.0
Python 3.8.8