Fwd: [ncl-install] Nio.open_file problem : object.__init__() takes no parameters

Hi Mary,
I started to answer this message, but then I realized how many changes
there have been to PyNIO since the the 1.3.0b1 release. I could tell
him just to change the offending line

  super(_Proxy, self).__init__(obj)
to
super(_Proxy, self).__init__()

as required by Python 2.6 and it will eliminate the particular error
he is getting, but it still would not have a lot of changes that have
happened since then. I am thinking maybe there should be a blanket
notice to users that if they are having problems they can get a new
binary and where to get it. Does this seem at all feasible or should I
just tell that to Sourish? I know it could be a lot of work so maybe
just keeping it limited to individuals is a better idea. I don't want
to cause you extra work especially since it is a particularly hard
period we are going through now. What do you think?

I see that there was another message from him as well that suggests
maybe he got through this issue but found another problem. It is hard
to help him when our version is so different from what he has. I am
not sure what to do.

FYI, I started to compose a message with this introduction:
------
You are right that we do not have a pyngl-install mailing list, so it
is hard to know where to post installation messages that concern
PyNGL/PyNIO particularly. I am not sure if we have established a
policy about this.

Also we apologize that we are late with a new release of PyNGL/PyNIO.
We are making some fairly major changes to NCL, many of which will be
automatically available to the PyNGL/PyNIO community, but we need to
get the next NCL release out the door before we can get to a new
Python tool release.
-----
  -dave

Begin forwarded message:

> From: Sourish Basu <sbasu@physics.cornell.edu>
> Date: February 8, 2010 8:11:00 AM MST
> To: ncl-install@ucar.edu
> Subject: Nio.open_file problem : object.__init__()
> takes no parameters
>
> Hi All,
>
> Recently, I installed NCL and PyNIO on Ubuntu 9.10 (x86_64). The
> install went smoothly, but when I try to actually use Nio to read a
> NetCDF4 file, I get the following error:
>
> [13]: fid = Nio.open_file("SampleNetCDF.nc4",'r')
> ---------------------------------------------------------------------------
> TypeError Traceback (most recent
> call last)
>
> /home/i/ResearchCode/Cost function/<ipython console> in <module>()
>
> /usr/local/lib/python2.6/dist-packages/PyNIO/Nio.pyc in
> open_file(filename, mode, options, history, format)
> 513 file = _Nio.open_file(filename,mode,options,history,format)
> 514
> --> 515 file_proxy = _proxy(file, 'str',
> create_variable=_create_variable)
> 516 setattr(file_proxy.__class__,'set_option',set_option)
> 517 file_proxy.file = file
>
> /usr/local/lib/python2.6/dist-packages/PyNIO/Nio.pyc in _proxy(obj,
> *specials, **regulars)
> 226 _known_proxy_classes[key] = cls
> 227 # instantiate and return the needed proxy
>
> --> 228 instance = cls(obj)
> 229 return instance
> 230
>
> /usr/local/lib/python2.6/dist-packages/PyNIO/Nio.pyc in
> __init__(self, obj)
> 167
> 168 def __init__(self, obj):
> --> 169 super(_Proxy, self).__init__(obj)
> 170 super(_Proxy,self).__setattr__('_obj', obj)
> 171 super(_Proxy,self).__setattr__('attributes',{})
>
> TypeError: object.__init__() takes no parameters
>
> I'm not sure which mailing list would be appropriate to ask for help,
> but I think this is an installation issue. Has anyone seen this
> before?
>
> Thanks,
>
> -Sourish
>
> _______________________________________________
> ncl-install mailing list
> List instructions, subscriber options, unsubscribe:
> http://mailman.ucar.edu/mailman/listinfo/ncl-install
Received on Mon Feb 8 12:34:54 2010