Skip to content
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.

Sign up for GitHub

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

Jump to bottom

%run script.ipy raises "ERROR! Session/line number was not unique in database." #328

Closed
minrk opened this issue Apr 1, 2011 · 2 comments · Fixed by #329
Closed

%run script.ipy raises "ERROR! Session/line number was not unique in database." #328

minrk opened this issue Apr 1, 2011 · 2 comments · Fixed by #329
Labels
bug
Milestone
old

Comments

@minrk
Copy link
Member

minrk commented Apr 1, 2011

running an IPython script (*.ipy) with %run will cause an error in the history manager:

In [1]: run script.ipy
ERROR! Session/line number was not unique in database. History logging moved to new session 427
@takluyver
Copy link
Member

See here: #329

@takluyver
Copy link
Member

Do not store file contents in history when running a .ipy file.

closed by 7d1bdfa

markvoorhies pushed a commit to markvoorhies/ipython that referenced this issue Apr 21, 2011
@takluyver
Do not store file contents in history when running a .ipy file.
7d1bdfa 
closes ipythongh-328
@takluyver takluyver mentioned this issue Apr 2, 2011
Merged
mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this issue Nov 3, 2014
@takluyver
Do not store file contents in history when running a .ipy file.
4b0e99a 
closes ipythongh-328
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
old
Development

Successfully merging a pull request may close this issue.

Do not store file contents in history when running a .ipy file. takluyver/ipython
2 participants
@minrk @takluyver