Yes, thanks Brian. I red your comments on IRC, they were very informative.
One observation though, the QGIS team is working on QGIS3 which is scheduled [1] for 2017-12-08 (less than a month now) and it is Qt5/PyQt5/Python3 based. So python2.7 won't be provided anymore (at least by QGIS). We have some time left until next release : Current LTR : *LTR* 2.18.8 2.14.15 2017-05-19 Next LTR: *LTR* 3.4.0 2.18.24 2018-07-27 But I think we should be able to include QGIS3 in one or 2 releases (so 2018 or 2019). There is plenty of time to discuss it, but including QGIS3 will be challenging for us ! And we might loose some libraries too. Great to see that OTB and ossim went well, I know by experience that OTB can be tricky to install. Best regards, Nicolas Roelandt [1] http://qgis.org/en/site/getinvolved/development/roadmap.html#location-of-prereleases-nightly-builds 2017-11-11 12:46 GMT+01:00 Angelos Tzotsos <gcpp.kal...@gmail.com>: > Thanks Brian for testing and providing feedback! > > Best, > Angelos > > > On 11/10/2017 06:19 PM, Brian M Hamlin wrote: > >> hi Angelos, all >> >> Yesterday I went through the gdal 2.2.2 transition experimental PPA, and >> used a basic strategy to install parts.. from foundation upwards.. and >> across related groups. I did not detect any conflicts .. Particularly with >> the otb set, and ossim, which are challenging to package well, >> and therefore may be more likely to contain bugs in packaging. >> This summary is for two purposes.. one is to signal to Angelos that >> someone looked at the set >> The second is.. I am quite excited about a new strategy for our python >> analytics here that occurred to me >> while doing the QGis testing. >> QGis LTS, based in python2 and qt4, in practice pulls in almost the >> whole matplotlib python set that we use. pandas is the next CORE component >> that would be needed.. with that, and a little charting support.. the whole >> analytics chain is there (python-grass is there, too.. not clear on those >> details) >> >> I believe that the Python2 conversation with the Numpy core team is now >> over.. they are high-achievers, and also have limited resources, so they >> have to have a single goal .. the new single goal for Numpy core is Python3 >> by 2020. (to be in synch between say.. Pandas 0.18 and Numpy, we may need >> to bump Numpy up a version or two.. TBD) >> >> Yet I believe, thinking about all the parts, that a solid analytics for >> geospatial, using the existing Python2 stack, >> is great value for users, and should be actively maintained for years to >> come. Managing that in a respectful way, that allows all the parties to do >> what they do best.. is the art here.. >> I look forward to the gdal 2.2.2 transition packaging to become widely >> available, in Debian and UbuntuGIS. And, I look forward to a new approach >> to the maintenance of the very valuable Python 2.7 stack with Matplotlib, >> Cartopy, Pandas and others .. >> best regards from Berkeley >> -Brian M Hamlin >> >> >> _______________________________________________ >> Live-demo mailing list >> Live-demo@lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/live-demo >> http://live.osgeo.org >> http://wiki.osgeo.org/wiki/Live_GIS_Disc >> > > > -- > Angelos Tzotsos, PhD > Charter Member > Open Source Geospatial Foundation > http://users.ntua.gr/tzotsos > > > _______________________________________________ > Live-demo mailing list > Live-demo@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/live-demo > http://live.osgeo.org > http://wiki.osgeo.org/wiki/Live_GIS_Disc > -- Bien cordialement, Nicolas Roelandt mail: roelandtn....@gmail.com mobile: +33 (0)6 42 40 42 55 twitter: @*RoelandtN42* <https://twitter.com/RoelandtN42>
_______________________________________________ Live-demo mailing list Live-demo@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/live-demo http://live.osgeo.org http://wiki.osgeo.org/wiki/Live_GIS_Disc
