Missing 'proxy' module

While attempting to run HDFCompass with the last PyPI release (3.2.0) of pydap, I noticed that the proxy module is gone together with ProxyArray class. Can you confirm it? If yes, is BaseType class the ‘natural’ substitute of ProxyArray?

The ProxyArray was imported here: https://github.com/HDFGroup/hdf-compass/blob/develop/hdf_compass/opendap_model/model.py#L19

[laliberte]

@giumas I’ve looked at your code and my opinion is that pydap proxy objects should not be assumed to be part of the public API. The obvious solution would be to rely only on the DatasetType object output from the open_url() function. If the function exits successfully, this object should contain all of the OPeNDAP dataset attributes and properly instantiated data proxy objects.

Moreover, it would seem to me that the easiest fix would be change https://github.com/HDFGroup/hdf-compass/blob/develop/hdf_compass/opendap_model/model.py#L235 to

self._data = new_dset[new_key].data

and line https://github.com/HDFGroup/hdf-compass/blob/develop/hdf_compass/opendap_model/model.py#L214-L215 should probably be removed.

[ax3l]

This is the last backend that is missing to ship the py3 branch in hdf-compass for a new release, afaik: https://github.com/HDFGroup/hdf-compass/issues/186

We are talking about

• this file: https://github.com/HDFGroup/hdf-compass/blob/py3/hdf_compass/opendap_model/model.py

which can be tested as follows when you clone the py3 branch of hdf-compass:

python3 -m unittest hdf_compass.opendap_model.test

Issues are a missing member .setdefault('') which only existed in ArrayProxy and resulting key errors in access to “root” [''].