[Nexus] Status of Python related issues

[Carlos Pascual]

Our scan recorder is based on the napi, and it is a critical component 
for our sytem. Also some other minor utilities.

I think it would no be too much work for us to migrate these t the tree 
API or even use h5py directly, but I would appreciate if an official 
statement is done ASAP regarding the napi.py in order to allocate time 
for the migration before I find that an update of NeXus breaks our data 
collection.


On Mon 30 November 2015 15:36:39 Osborn, Raymond wrote:
> I see that some, if not all, of the Python issues were raised by me. I
> presume the issue dates are actually the transfer dates and bear no
> relation to the actual issues, which are probably lost in the mists
> of time. I haven’t worked on the Python bindings in the official
> NeXus repository for years, and have no idea of their status and
> don’t really have time to go back over them again.
> 
> Is anyone else using these bindings? They are available in an
> HDF5-only version in the nexusformat Github at
> https://github.com/nexpy/nexusformat. The original napi.py was
> removed there because the tree API doesn’t need it any more, although
> we did discuss briefly at the code-camp telco resurrecting it using
> h5py calls. That could be done within the nexpy Github, if someone
> wants to work on it. I even created a ‘napi’ branch for this purpose
> a couple of weeks ago.
> 
> Ray
> 
> On Nov 30, 2015, at 7:34 AM, Eugen Wintersberger
> <eugen.wintersberger at desy.de<mailto:eugen.wintersberger at desy.de>>
> wrote:
> 
> Hi Stuart,
> 
> On 11/30/15 14:30, Stuart Campbell wrote:
> Hi,
> They only appear to be opened by me as I did the ticket migration. The
> real 'requester' is in the first line of the body.
> Cheers
> Stu\
> 
> Sorry for blaming you being responsible for all the Python related
> tickets ;). Did not recognize the first line with the original issuer.
> 
> regards
>  Eugen
> 
> 
> On 11/30/2015 08:17 AM, Eugen Wintersberger wrote:
> Hi folks,
>   I am currently working on the release for the NAPI Python wrapper.
> As you may have recognized, the Python code has moved to its own
> repository (python-nxs). There are several Python related issues
> concerning the Python bindings listed in NAPIs issues tracker which I
> would like to move to the new python-nxs repository.
> However, I am not sure about the status of theses issues (most of them
> opend by Stuart).
> Can anyone please confirm whether or not these issues are still open
> 
> https://github.com/nexusformat/code/issues/324
> https://github.com/nexusformat/code/issues/322
> https://github.com/nexusformat/code/issues/182
> https://github.com/nexusformat/code/issues/162
> https://github.com/nexusformat/code/issues/156
> 
> If theses issues are still open we should try to fix them in the 4.4.0
> release for the Python bindings.
> 
> regards
>   Eugen
> 
> 
> --
> Ray Osborn, Senior Scientist
> Materials Science Division
> Argonne National Laboratory
> Argonne, IL 60439, USA
> Phone: +1 (630) 252-9011
> Email: ROsborn at anl.gov<mailto:ROsborn at anl.gov>

-- 
+----------------------------------------------------+
 Carlos Pascual Izarra
 Scientific Software Coordinator
 Computing Division
 ALBA Synchrotron  [http://www.albasynchrotron.es]
 Carrer de la Llum 2-26
 E-08290 Cerdanyola del Valles (Barcelona), Spain
 E-mail: cpascual at cells.es
 Phone: +34 93 592 4428
+----------------------------------------------------+