On Thu, Jun 2, 2016 at 3:49 PM, Ghislain Vaillant wrote:
> Hi Sandro,
>
> I engaged with the pydap community and I can confirm that the project
> has moved on from the old 2.x API. Since pydap 3.x is now using a new
> namespace (pydap instead of dap), then both package versions should be
> co-inst
Hi Sandro,
I engaged with the pydap community and I can confirm that the project
has moved on from the old 2.x API. Since pydap 3.x is now using a new
namespace (pydap instead of dap), then both package versions should be
co-installable.
Since I need the pydap 3.x API for hdf-compass, I propose
I believe upstream has moved on from the API of 2.x (dap namespace) to
using 3.x (pydap namespace). My assumption is based on the facts that:
1) the upstream repository [1] provide tags for 3.x releases only,
2) active issues, such as Python 3 support, are milestoned for 3.2.x [2],
[1] https://
for a start, you can try to get upstream to reply to this (old)
question: https://groups.google.com/forum/#!topic/pydap/6A6q-Y6qwtE
On Thu, Jan 28, 2016 at 9:24 AM, Ghislain Vaillant wrote:
> Forwarding to d-python, as it seems like a more appropriate place to
> discuss this matter.
>
>
> ---
4 matches
Mail list logo
