Fighting pydap (3.2)

In the new year, I’m trying to work with the “new” pydap. Unfortunately, it seems to be just a lot of the old code, reorganized, with annoying configuration changes, and a subset of the features of the previous releases! Sounds like a major downgrade to me. Allow me to enumerate my grievances:

• Changes in the server configuration once again. Now rather than serving with paster or whatever, you have to write yet another config file (this time in YAML) and then start up the server with a pydap binary.
• Where are the deps? Most of the dependencies aren't listed in setup.py, so you have to start the server like 8 times, invoking "pip install [package]" between each successive attempt.
• Most of the handlers and responses have not been ported. I need a netcdf4 (or hdf5) handler and wms response and neither of these things are in place yet.
• pydap.handlers.netcdf now only uses pupynere (Rob's home-grown netcdf library which doesn't support netcdf > 3). Not that the old code was great... it tried to import one of three different netcdf libraries and then defined a few contants based on what worked. But... at least you could uninstall pupynere and get a netcdf library that supported netcdf 4.

With these problems, I think that I’m going to have to go back to pydap 3.1… 3.2 just isn’t good enough.