Bug#778417: RE:Bug#778417: ITP: netcdf-python -- python interface to the netCDF4 (network Common Data Form) library

2015-02-24 Thread Konrad Hinsen
On Tue, 24 Feb 2015 06:44:54 + Nick Papior Andersen 
nickpap...@gmail.com wrote:



In my experience many of the features are quite similar.

However, 

netcdf4-python has the advantage of full CDF4 capabilities.
Konrads 

excellent package allows reading a NetCDF4 format in CLASSIC
format, it 

also allows writing the CDF3 and CDF3-64 bit files. But it does
not allow 

writing the full NetCDF4 format (I do not know if he has just
implemented 

it, but last time I checked, 2.9.3, he hadn't).



The netCDF interface in ScientificPython has no support for the 
functionality specific to netCDF4, for two reasons: (1) I don't need it and 
(2) I want to maintain compatibility with netCDF3, which is (or at least 
used to be a while ago) much less problematic to install than netCDF4 with 
its enormous dependency (HDF5).


I cannot dedicate much energy to netCDF support because I am migrating my 
own software to a direct use of HDF5. I continue to support netCDF merely 
for keeping my legacy software usable. I'd be happy to abandon my netCDF 
interface in the long run and use netcdf4-python for my legacy code. 
However, the last time I checked, this didn't look like a viable option.


For the pure Python interface, I could probably replace 
Scientific.IO.NetCDF by a thin wrapper on top of netcdf4-python. But for 
the C interface, I do not see a solution. I have application code (the 
Molecular Modelling Toolkit, http://dirac.cnrs-orleans.fr/MMTK/) that 
accesses a single opened netCDF file both from Python code and from C 
extension modules. To make this work portably, supporting shared libraries 
on all platforms, the C API calls must pass through the C extension module 
that is linked to the netCDF library. Last time I checked, netcdf4-python 
did not support this. Is there perhaps a different solution for this 
scenario?


Konrad.
--
-
Konrad Hinsen
Centre de Biophysique Moléculaire, CNRS Orléans
Synchrotron Soleil - Division Expériences
Saint Aubin - BP 48
91192 Gif sur Yvette Cedex, France
Tel. +33-1 69 35 97 15
E-Mail: research AT khinsen DOT fastmail DOT net
http://dirac.cnrs-orleans.fr/~hinsen/
ORCID: http://orcid.org/-0003-0330-9428
Twitter: @khinsen
-


--
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20253DDA61467849673116D5@Konrad-Hinsens-MacBook-Pro-2.local



Bug#778417: ITP: netcdf-python -- python interface to the netCDF4 (network Common Data Form) library

2015-02-19 Thread Konrad Hinsen
Hi everyone,

PICCA Frederic-Emmanuel writes:
  @Konrad do you think that this netcdf implementation from scientific python 
  could be replace by this
  netcdf4-python implementation ? Should we get rid of your implentation and 
  use this one instead (to be clear)

The main problem with Python-netCDF interfaces is that no two of them
have compatible API even for the most basic operations. Whenever some
Python package depends on netCDF, it depends on one of the various
Python-netCDF interfaces, and wouldn't work with the other ones.

To make it worse, even if your goal is only to provide a single Python
interface for new developments, not caring about compatibility, the
features of the various Python interfaces are sufficiently different
to make a choice very difficult.

The unique feature of my own netCDF interface, and the reason why
I keep maintaining it, is the C-level API for other Python modules.
Each of the other interfaces has such unique features as well.

Konrad.
-- 
-
Konrad Hinsen
Centre de Biophysique Moléculaire, CNRS Orléans
Synchrotron Soleil - Division Expériences
Saint Aubin - BP 48
91192 Gif sur Yvette Cedex, France
Tel. +33-1 69 35 97 15
E-Mail: research AT khinsen DOT fastmail DOT net
http://dirac.cnrs-orleans.fr/~hinsen/
ORCID: http://orcid.org/-0003-0330-9428
Twitter: @khinsen
-


--
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/21734.18557.231820.534...@gargle.gargle.howl