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/0000-0003-0330-9428 Twitter: @khinsen --------------------------------------------------------------------- -- To UNSUBSCRIBE, email to debian-devel-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
