Hi Lewis, Hmm, that's a rather complicated dependency issue. I'd say trying to replace the netcdftime functionality just to support Python 3.4 isn't worth it. I am actually personally of the opinion that anyone who is using Python 3 should be on 3.5+ anyway since that particular release made some pretty drastic improvements. It's why I plan to keep things simple when bcdt comes around (which should hopefully be soonish) by making it python 3.5+ only.
As for pydap I think your proposed approach is fine. Thanks, Alex On Fri, Jun 29, 2018 at 2:32 PM, lewis john mcgibbney <lewi...@apache.org> wrote: > Hi Alex, > Thanks for this yes I agree. > The point I was making is that the build is busted. > Let me propose then that we > 1) drop Pydap support for the Python 2.7 build, > 2) enable it for the Python 3. > > Then what do we do about the following issue for the Python 3.4 build? > > UnsatisfiableError: The following specifications were found to be in > conflict: > - netcdftime -> python=3.6 > - python=3.4 > > We could remove the netcdftime dependency and replace the functionality > with some equivalent. I am not sure where the equivalent is though. Any > ideas? Anything we can pull from the netcdf depndency? > > Lewis > > On Thu, Jun 28, 2018 at 6:27 AM, <dev-digest-h...@climate.apache.org> > wrote: > > > > > From: "Goodman, Alexander (398K)" <alexander.good...@jpl.nasa.gov> > > To: "dev@climate.apache.org" <dev@climate.apache.org> > > Cc: > > Bcc: > > Date: Tue, 26 Jun 2018 13:46:58 -0700 > > Subject: Re: Availability of Pydap > > This shouldn't be a big deal. Previously we excluded pydap for our > python 3 > > builds, so in the worst case scenario we can always do the reverse. I > > honestly don't think it's that important of a dependency anyways since > the > > base netCDF4 library already provides some opendap functionality.... > > > > > -- Alex Goodman Data Scientist I Science Data Modeling and Computing (398K) Jet Propulsion Laboratory California Institute of Technology Tel: +1-818-354-6012
