c.ExecutePreprocessor.timeout does not work in config

Operating system

Windows 10

nbgrader --version

0.6.2

jupyterhub --version (if used with JupyterHub)

Nil

jupyter notebook --version

6.3.0

Expected behavior

Setting c.ExecutePreprocessor.timeout in config should change validation timeout window

Actual behavior

Setting c.ExecutePreprocessor.timeout to None or another other number has no effect on the default 30s

Additional info

I have looked at both issues #1004 and #1075 but nothing works

[wkirgsn]

I managed to set the timeout to 600s via nbgrader validate --Execute.timeout=600 and in the config file via c.Execute.timeout = 600.

See also

# nbgrader --help-all | grep -A16 Execute.timeout=
--Execute.timeout=<Int>
    Default: 30
    The time to wait (in seconds) for output from executions. If a cell
    execution takes longer, an exception (TimeoutError on python 3+,
    RuntimeError on python 2) is raised.
    `None` or `-1` will disable the timeout. If `timeout_func` is set, it
    overrides `timeout`.
--Execute.timeout_func=<Any>
    Default: None
    A callable which, when given the cell source as input, returns the time to
    wait (in seconds) for output from cell executions. If a cell execution takes
    longer, an exception (TimeoutError on python 3+, RuntimeError on python 2)
    is raised.
    Returning `None` or `-1` will disable the timeout for the cell. Not setting
    `timeout_func` will cause the preprocessor to default to using the `timeout`
    trait for all cells. The `timeout_func` trait overrides `timeout` if it is
    not `None`.

FYI @RonaldEnsing Pingback #1004 #1075

Neither of both suggestions works for me, there will be always the warning that config option “timeout” not recognized by “Execute” with the latest pypi release 0.7.0, and cells can only run for 30 seconds.

[davidnero]

c.Execute.timeout_func = lambda x: 500 can be used as a work-around in 0.7.1