On Wed, Aug 27, 2014 at 3:29 PM, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > Hi, > > Now that pip is an optional spkg, I think it would be a good idea to: > 1) add some word about it in the documentation > 2) use it to replace some of the optional and experimental packages > I would like more comments (especially about 2) to see whether or not > it is a good idea. If it works, we might even move the pip spkg to > standard and use it during the build process. > > Running quickly through the list of optional packages, we can remove 4 of > them: > - beautiful soup > - pyopenssl > - pyqtx > - pyzmq > which just install nicely through pip. Could we keep backward > compatibility by setting a dependency to pip spkg and replace their > install script with "pip install PACKAGE"? > > For those three ones, we need to set extra options but it works as well: > - gnuplotpy > - nzmath > - pyx (need to use PyX==0.12.1, since it is the last one compatible > with python 2) > > And two packages just fail to install through pip. > - pybtex > - sip > > It would greatly simplify the life of package maintainer!
Just a +1 from me to this project. When I started the whole spkg business, the state of Python package management was a total mess/disaster. Today with pip things are much, much better. William -- William Stein Professor of Mathematics University of Washington http://wstein.org wst...@uw.edu -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
