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

Redesign how Component instances are tracked and queried #117

Closed
ellisonbg opened this issue May 13, 2010 · 1 comment
Closed

Redesign how Component instances are tracked and queried #117

ellisonbg opened this issue May 13, 2010 · 1 comment
Milestone
0.11

Comments

@ellisonbg
Copy link
Member

The current design of IPython uses Components that 1) know how to configure themselves and 2) automatically track their instances and have an API for retrieving those instances. I think we need to rethink the auto-tracking and the querying API for Components as it feels a bit too magic. I think we want something that is a bit more pedestrian and explicit. Another problem is that Component.get_instances will return all instances and if you get multiple back, there really isn't a godo way of deciding which to use.
@ellisonbg
Copy link
Member Author

This was fixed this summer with the move from Component -> Configurable.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.11
Development

No branches or pull requests
1 participant
@ellisonbg