Python Tool Warning Insecure Writes
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi
I used Python tool to run some scripts and write data to workflows. Recently I noticed a warning as follows in all python tools created before.
Warning: Python (1): WARNING: Insecure writes have been enabled via environment variable 'JUPYTER_ALLOW_INSECURE_WRITES'! If this is not intended, remove the variable or set its value to 'False'.
[NbConvertApp] WARNING | Config option `template_path` not recognized by `NotebookExporter`.
if I use %env to check the jupyter environment variables, I can see
'JUPYTER_ALLOW_INSECURE_WRITES': '1'
I tried to change the variable to False but it did not permanently change the variable. When the workflow open again, the warning shows up again.
Does anyone know how to fix the warning?
- Labels:
- Python
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Haven't seen that one before. This is the only I can find on that issue: https://github.com/jupyter/notebook/issues/5197. Might be worth checking out, scroll to the bottom for what this person did to get it working.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Thanks.
I updated nbconvert and nbformat libraries to the latest versions in Alteryx env, and then the issue was fixed. But I am still not sure what caused the issue. In another computer with old versions of those 2 libraries did not trigger the same warning.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi,
I had the same error from a workflow that had been running fine for a long time. Seems either an update of Alteryx or Python, or perhaps one of our team running on their machine with a slightly different config must have triggered something.
The only way I found to fix it was to create a fresh workflow, copy across all tools except the python tool, add a new 'fresh' python tool, copy/paste the code, then run (i.e generate a new env). This seemed to fix it.
Cheers
