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.

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

Also capture execution results using sys.displayhook #9851

Merged
merged 2 commits into from Aug 31, 2016

Conversation

@takluyver
Copy link
Member

@takluyver takluyver commented Aug 9, 2016

From discussion on mailing list. It's not clear if this is what we want to do, or if it should be controlled by a separate option, but it's submitted for consideration.

From discussion on mailing list. It's not clear if this is what we want
to do, or if it should be controlled by a separate option, but it's
submitted for consideration.
@minrk
Copy link
Member

@minrk minrk commented Aug 9, 2016

I think it makes more sense to more people this way. Relatively few people really understand or care about the difference between displayhook and display.

@minrk minrk added this to the 5.2 milestone Aug 9, 2016
@Carreau
Copy link
Member

@Carreau Carreau commented Aug 24, 2016

+1; @takluyver is there a need for a line in the what's new ?

@takluyver
Copy link
Member Author

@takluyver takluyver commented Aug 31, 2016

I've added a whatsnew entry.

@Carreau Carreau merged commit 8714ee2 into ipython:master Aug 31, 2016
Carreau added a commit to Carreau/ipython that referenced this pull request Sep 18, 2016
…splayhook

From discussion on mailing list. It's not clear if this is what we want to do, or if it should be controlled by a separate option, but it's submitted for consideration.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.