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

Generate package list automatically in find_packages #646

Merged
merged 1 commit into from Aug 1, 2011

Conversation

minrk
Copy link
Member

@minrk minrk commented Jul 30, 2011

Previously, the package list was manually specified, which meant that it became out of date any time a package was added, and IPython would become uninstallable. This would not be noticed for some time by developers, who always use setupegg.py --develop or symlinks.

This update immediately revealed that IPython.zmq.tests and IPython.extensions.tests were never included in 0.11. Other than that, there is no difference in the package list.

Wait for after 0.11, in case of unforeseen side effects.

@minrk
Copy link
Member Author

minrk commented Aug 1, 2011

@fperez is there any reason that we should not do it this way? The only one I see is that you can change what's installed by creating new files inside the IPython dir, but this doesn't strike me as anything but an improvement.

@fperez
Copy link
Member

fperez commented Aug 1, 2011

Nope, that's certainly the right way to do it. Merge away!

Previously, the package list was manually specified, which meant that
it became out of date any time a package was added, and IPython would
become uninstallable. This would not be noticed for some time by
developers, who always use `setupegg.py --develop` or symlinks.

This update immediately revealed that IPython.zmq.tests and IPython.extensions.tests were never included in 0.11.  Other than that, there is no difference in the package list.
@minrk minrk merged commit 1eea56b into ipython:master Aug 1, 2011
jasongrout added a commit to jasongrout/ipython that referenced this pull request Feb 16, 2015
A bug in pyzmq forces us to have a workaround, which can be deleted when the pyzmq dependency is upgraded to fix pyzmq issue ipython#646.

Thanks to @minrk for helping work on the code and also for the bugfix in pyzmq.
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