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
When modifying a python module, like when renaming a function "foo" into "bar", it is common to perform a "Find in files" operation to look for occurrences of "foo(" to be replaced elsewhere, including IPython notebooks.
Therefore, it can be interesting to include the .ipynb format
-> in the default filter for "Find in files"
-> in the proposed formats for the "Open" dialog
-> in the file explorer filter for file formats.
The text editor would then open the bare .ipynb text file. This would be interesting regardless of the support for the notebook in Spyder.
The js/json syntax coloring scheme could be used for this file type.
Besides,
-> global notebook manipulations could be added to the context menu, like "clear all output, convert to Python script" etc...
From sylvain....@gmail.com on 2014-03-23T11:34:33Z
When modifying a python module, like when renaming a function "foo" into "bar", it is common to perform a "Find in files" operation to look for occurrences of "foo(" to be replaced elsewhere, including IPython notebooks.
Therefore, it can be interesting to include the .ipynb format
-> in the default filter for "Find in files"
-> in the proposed formats for the "Open" dialog
-> in the file explorer filter for file formats.
The text editor would then open the bare .ipynb text file. This would be interesting regardless of the support for the notebook in Spyder.
The js/json syntax coloring scheme could be used for this file type.
Besides,
-> global notebook manipulations could be added to the context menu, like "clear all output, convert to Python script" etc...
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1767
The text was updated successfully, but these errors were encountered: