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

use eval to uncan References #1458

Merged
merged 1 commit into from Mar 1, 2012
Merged

use eval to uncan References #1458

merged 1 commit into from Mar 1, 2012

Conversation

minrk
Copy link
Member

@minrk minrk commented Mar 1, 2012

as opposed to dict.get()

This allows things like Reference('obj.attr') or Reference('obj[item]'), or even view.map(Reference('obj.method'), seq), rather than requiring an assignment into the global namespace via execute before Reference can be used to point to any of these objects.

as opposed to dict.get

This allows things like `Reference('obj.attribute')` or `Reference('obj[item]')`, or even `view.map(Reference('obj.method'), seq)`, rather than requiring an assignment into the global namespace via `execute` before Reference can be used to point to an object.
@ellisonbg
Copy link
Member

This is great and it looks fine. I say merge away.

minrk added a commit that referenced this pull request Mar 1, 2012
use eval to uncan References

allows things like `Reference('obj.attr')` or `Reference('obj[item]')`
@minrk minrk merged commit c849352 into ipython:master Mar 1, 2012
mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this pull request Nov 3, 2014
use eval to uncan References

allows things like `Reference('obj.attr')` or `Reference('obj[item]')`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants