-
Notifications
You must be signed in to change notification settings - Fork 393
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
Unable to remove lines_to_next_cell
metadata
#139
Comments
Hello Andre, For the next release I have been thinking of removing the I am not in a position to test your example right now, but I will later on. Meanwhile, you may want to edit the metadata filter manually (in the notebook metadata), or give a try to the following configuration,
|
Hello Andre, I confirm that I have been able to reproduce the issue. I have added a test, and provided a fix in the branch 0.9.0. I will let you know (well, I think GitHub will automatically close this issue) when the new version becomes available - this may well take a few more days. |
Thanks for the great support @mwouts ! |
Hello Andre, it has been a while... The new release candidate should solve this. Can you test and confirm? It is available with
Note that you will have to change your configuration, as the Thanks! |
Hi @mwouts , Sorry for the delay! I've tried to reproduce the behavior I described above and I can confirm that the But, I get the For reference, here is the full content: # + {"ExecuteTime": {"start_time": "2019-02-04T14:32:07.977074Z", "end_time": "2019-02-04T14:32:07.980676Z"}}
import os
# + {"ExecuteTime": {"start_time": "2019-02-04T14:32:08.178820Z", "end_time": "2019-02-04T14:32:08.184917Z"}}
print('hello1')
# -
# + {"ExecuteTime": {"start_time": "2019-02-04T14:32:08.964653Z", "end_time": "2019-02-04T14:32:08.969993Z"}}
print('hello3')
# -
What do I need to do in the config then, to make sure no metadata is saved at all? |
Hello @andrethrill ... well, I am a bit surprised! My expectations are:
May I ask you to have a look at the notebook metadata using the Jupyter notebook metadata editor? I expect that you will find a non-trivial metadata filter there, which probably explain what you observe. If you want that Jupytext always save your notebooks with no metadata, use |
Hi again @mwouts . Here's what I've done: Created a new import os
print('hello1')
print('hello2') And saved it. Then opened it using the notebook interface. Executed the 3 cells: Checked the Edit-->Edit Notebook Metadata: Saved the "notebook". And this is its content: # + {"ExecuteTime": {"start_time": "2019-02-06T11:53:21.208644Z", "end_time": "2019-02-06T11:53:21.213071Z"}}
import os
# + {"ExecuteTime": {"start_time": "2019-02-06T11:53:21.463238Z", "end_time": "2019-02-06T11:53:21.468873Z"}}
print('hello2')
# -
# + {"ExecuteTime": {"start_time": "2019-02-06T11:53:21.870293Z", "end_time": "2019-02-06T11:53:21.875642Z"}}
print('hello2')
# -
I was expecting the contents of the In the
(I know you said the |
That is interesting, thanks @andrethrill for reporting this so carefully. I will have a look. |
Andre, there was indeed an issue with the combination of the user and the default filter. The fix is on its way. What I advice for now is that you remove the default cell metadata filter filter (as, anyway the metadata |
@andrethrill , this should be solved in the latest rc:
Thanks for reporting this, it was a nasty bug! |
@mwouts I can confirm the bug is fixed! Thanks for your great support. |
Excellent. Thank you André. |
If I have the following global configs:
When I open a
.py
script that has the following content:Then hit the button "Save and Checkpoint" in the browser interface and open the script again in a text editor, the new content of the script is:
I've also tried to have in the global configs the following:
But the behavior is still the same.
Shouldn't the
c.ContentsManager.freeze_metadata
option save no metadata at all when the original files have no metadata?If not, how can I remove the
lines_to_next_cell
metadata in this scenario?Thanks in advance!
The text was updated successfully, but these errors were encountered: