Re: Maintenance of pydap

2016-06-09 Thread Sandro Tosi 
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-installable.
>
> Since I need the pydap 3.x API for hdf-compass, I propose to introduce
> a new source package for it (which I am happy to maintain) and keep the
> old source package alive until all reverse dependencies relying on 2.x
> eventually move on.
>
> Hoe does that sound?

sounds good to me

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Re: Maintenance of pydap

2016-06-02 Thread Ghislain Vaillant 

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 to introduce
a new source package for it (which I am happy to maintain) and keep the
old source package alive until all reverse dependencies relying on 2.x
eventually move on.

Hoe does that sound?

Ghis

On 28/01/16 09:50, Ghislain Vaillant wrote:

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://github.com/robertodealmeida/pydap
[2] https://github.com/robertodealmeida/pydap/issues/7

Since dap 2.x is no longer actively maintained, then the question is
whether to introduce a new source package for pydap 3.x or just upgrade
the current source package to 3.x and take care of the rdep for
python-mpltoolkits.basemap.

Thoughts?
Ghis


On 28/01/16 09:26, Sandro Tosi wrote:

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
<ghisv...@gmail.com> wrote:

Forwarding to d-python, as it seems like a more appropriate place to
discuss this matter.


 Forwarded Message 
Subject: Maintenance of pydap
Date: Mon, 25 Jan 2016 08:00:32 +
From: Ghislain Vaillant <ghisv...@gmail.com>
To: mo...@debian.org
CC: python-modules-t...@lists.alioth.debian.org

Ciao Sandro,

I recently got involved with the packaging of the HDF compass [1], a
viewer for HDF5 written in Python and using pydap as an install
dependency.

The version of pydap currently packaged is too old to work with the
compass, first because version 3.x apparently changed the module API
from using `import dap` to `import pydap`.

I saw the following bug report [2] requesting an update of the package,
but it was not acted upon or acknowledged. I am thereby contacting you
to know whether the package was still actively maintained on your end.

If you have lost interest in maintaining this package, myself and the
Debian Science Team would be interested in taking over, since both
hdf-compass and pydap are science related.

Otherwise, please allow me to request an update to this package so I
can carry on with my packaging work on hdf-compass.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812434
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788508

Many thanks,
Ghis

Fwd: Maintenance of pydap

2016-01-28 Thread Ghislain Vaillant 

Forwarding to d-python, as it seems like a more appropriate place to
discuss this matter.

 Forwarded Message 
Subject: Maintenance of pydap
Date: Mon, 25 Jan 2016 08:00:32 +
From: Ghislain Vaillant <ghisv...@gmail.com>
To: mo...@debian.org
CC: python-modules-t...@lists.alioth.debian.org

Ciao Sandro,

I recently got involved with the packaging of the HDF compass [1], a
viewer for HDF5 written in Python and using pydap as an install
dependency.

The version of pydap currently packaged is too old to work with the
compass, first because version 3.x apparently changed the module API
from using `import dap` to `import pydap`.

I saw the following bug report [2] requesting an update of the package,
but it was not acted upon or acknowledged. I am thereby contacting you
to know whether the package was still actively maintained on your end.

If you have lost interest in maintaining this package, myself and the
Debian Science Team would be interested in taking over, since both
hdf-compass and pydap are science related.

Otherwise, please allow me to request an update to this package so I
can carry on with my packaging work on hdf-compass.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812434
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788508

Many thanks,
Ghis

Re: Maintenance of pydap

2016-01-28 Thread Sandro Tosi 
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 <ghisv...@gmail.com> wrote:
> Forwarding to d-python, as it seems like a more appropriate place to
> discuss this matter.
>
>
>  Forwarded Message 
> Subject: Maintenance of pydap
> Date: Mon, 25 Jan 2016 08:00:32 +
> From: Ghislain Vaillant <ghisv...@gmail.com>
> To: mo...@debian.org
> CC: python-modules-t...@lists.alioth.debian.org
>
> Ciao Sandro,
>
> I recently got involved with the packaging of the HDF compass [1], a
> viewer for HDF5 written in Python and using pydap as an install
> dependency.
>
> The version of pydap currently packaged is too old to work with the
> compass, first because version 3.x apparently changed the module API
> from using `import dap` to `import pydap`.
>
> I saw the following bug report [2] requesting an update of the package,
> but it was not acted upon or acknowledged. I am thereby contacting you
> to know whether the package was still actively maintained on your end.
>
> If you have lost interest in maintaining this package, myself and the
> Debian Science Team would be interested in taking over, since both
> hdf-compass and pydap are science related.
>
> Otherwise, please allow me to request an update to this package so I
> can carry on with my packaging work on hdf-compass.
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812434
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788508
>
> Many thanks,
> Ghis



-- 
Sandro "morph" Tosi
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Re: Maintenance of pydap

2016-01-28 Thread Ghislain Vaillant 
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://github.com/robertodealmeida/pydap
[2] https://github.com/robertodealmeida/pydap/issues/7

Since dap 2.x is no longer actively maintained, then the question is 
whether to introduce a new source package for pydap 3.x or just upgrade 
the current source package to 3.x and take care of the rdep for 
python-mpltoolkits.basemap.


Thoughts?
Ghis


On 28/01/16 09:26, Sandro Tosi wrote:

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 <ghisv...@gmail.com> wrote:

Forwarding to d-python, as it seems like a more appropriate place to
discuss this matter.


 Forwarded Message 
Subject: Maintenance of pydap
Date: Mon, 25 Jan 2016 08:00:32 +
From: Ghislain Vaillant <ghisv...@gmail.com>
To: mo...@debian.org
CC: python-modules-t...@lists.alioth.debian.org

Ciao Sandro,

I recently got involved with the packaging of the HDF compass [1], a
viewer for HDF5 written in Python and using pydap as an install
dependency.

The version of pydap currently packaged is too old to work with the
compass, first because version 3.x apparently changed the module API
from using `import dap` to `import pydap`.

I saw the following bug report [2] requesting an update of the package,
but it was not acted upon or acknowledged. I am thereby contacting you
to know whether the package was still actively maintained on your end.

If you have lost interest in maintaining this package, myself and the
Debian Science Team would be interested in taking over, since both
hdf-compass and pydap are science related.

Otherwise, please allow me to request an update to this package so I
can carry on with my packaging work on hdf-compass.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812434
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788508

Many thanks,
Ghis