Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #8174
| From | Ghislain Vaillant <ghisvail@gmail.com> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Maintenance of pydap |
| Date | 2016-01-28 11:10 +0100 |
| Message-ID | <qVRGy-1R3-25@gated-at.bofh.it> (permalink) |
| References | <qVR3R-1j6-23@gated-at.bofh.it> <qVR3R-1j6-25@gated-at.bofh.it> <qVR3R-1j6-21@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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 <ghisvail@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 +0000 >> From: Ghislain Vaillant <ghisvail@gmail.com> >> To: morph@debian.org >> CC: python-modules-team@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 > > >
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Maintenance of pydap Sandro Tosi <morph@debian.org> - 2016-01-28 10:30 +0100
Re: Maintenance of pydap Ghislain Vaillant <ghisvail@gmail.com> - 2016-01-28 11:10 +0100
Re: Maintenance of pydap Ghislain Vaillant <ghisvail@gmail.com> - 2016-06-02 17:10 +0200
Re: Maintenance of pydap Sandro Tosi <morph@debian.org> - 2016-06-09 12:30 +0200
csiph-web