Hi Matt, thanks for the answer.
On Mon, Nov 2, 2015 at 1:53 PM, Matt Wilkie <map...@gmail.com> wrote: > > I've been disengaged in Osgeo4w this year but as the original author of > the External Packages wiki page I'll throw in my 2c: The package maintainer > pool for o4w is very small, so in my opinion it's better to leverage pip > and pypa since there are more people and resources keeping that going. > I also see pip as really advantageous as opposed to solving individual packages. I would make sense to me to have is as a standard package in OSGeo4W if it is even possible from support point of view. > > With regards to Ipython, a quick test in a new install shows ipython > itself still works, for 32bit o4w. (Though I needed to change the get-pip > install procedure a bit; wiki page updated.) What are the notebook specific > errors? Thanks for testing it. Good to know it generally works. I don't have the error message anymore. I was probably just a local problem. I'll try on a next occasion. Vaclav
_______________________________________________ osgeo4w-dev mailing list osgeo4w-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/osgeo4w-dev
