-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
passing environment variables to the kernel #359
Comments
TBH, I don't know.
I don't know whether There is a related option https://nbsphinx.readthedocs.io/en/latest/usage.html#nbsphinx_execute_arguments, but I guess this doesn't help in your case? |
I looked into |
I guess so. It's really hard to give any guarantees, because there are so many moving parts. But I'd say it seems to be currently a reasonable way to achieve what you want.
You should add that to the documentation! There is already a section "Controlling Notebook Execution" where this would fit. |
I'm trying to figure out where to add this: would that be a new subsection (i.e. linking to a new notebook in |
Yes, I think a new notebook would be nice for that. This new notebook could probably also mention |
xref pydata/xarray#3567
I'm trying to pass
PYTHONPATH
fromconf.py
to the kernels in order to make sure the notebook is executed using the source checkout instead of a version pulled by dependencies.I tried to modify
$PYTHONPATH
(as recommended in the related #96) by editingos.environ
inconf.py
, which seems to work:is this something I can rely on? If so, maybe you should add that to your documentation?
The text was updated successfully, but these errors were encountered: