Hi Stuart, The dev-version of ARTS has full support of the workspace methods of typhon. In fact, typhon.arts.workspace is simply pyarts.workspace with some small modifications. So things should work as they have with typhon just making that replacement in your imports. If you use other things from typhon, like setting environment data like arts-xml-data paths, I am really not sure how it they work in the future. I hope we can add that to let pyarts handle it automatically itself.
I see no reason why typhon should remove the ARTS interface entirely, but they will likely want to change so the version of pyarts from ARTS replaces the "arts" module when things settle down on the ARTS side. Especially if the two projects start to diverge (e.g., new python features will be added to the ARTS-version, and not to typhon). With hope, --Richard Den tors 9 apr. 2020 kl 14:24 skrev Fox, Stuart <stuart....@metoffice.gov.uk >: > Hi developers, > > > > I’ve just been working on interfacing some Python code with ARTS > (basically using ARTS to provide atmospheric radiances for use with the > SMRT snow surface microwave model). So far my implementation uses the > typhon.arts.workspace functions for the interfacing, but I notice from the > recent history on github that there might be some other ARTS/Python work > going on at the moment? Does this mean that the typhon method will be > deprecated soon? Is there any info/update on what is going on with > ARTS/python interfacing? > > > > Cheers, > > > > Stuart > _______________________________________________ > arts_dev.mi mailing list > arts_dev.mi@lists.uni-hamburg.de > https://mailman.rrz.uni-hamburg.de/mailman/listinfo/arts_dev.mi >
_______________________________________________ arts_dev.mi mailing list arts_dev.mi@lists.uni-hamburg.de https://mailman.rrz.uni-hamburg.de/mailman/listinfo/arts_dev.mi
