Releases: sassoftware/saspy
V3.1.5
V3.1.4
This release has fixes for the COM access method. The sd2df() method wasn't supporting missing values in data/datetime fields, which then caused other problems. issue 255. Also the sd2df_CSV() method was failing due to a bad Format statement generated in data step code which caused an error. Also some doc changes and eliminating the need to specify class_id.
V3.1.3
This release has minor changes/enhancements. Mostly creating it to get the fix for Issue #254 available in PyPI for customer. It has that fix, and a few doc changes for COM and a couple minor fixes too. A couple new methods: sil() and add_vars(). Cleaned up a traceback that could happen sometimes upon termination. That's about it.
V3.1.2
This release is identical to 3.1.1. I didn't get the new thirdparty jars included in the Pypi 3.1.1 version, so I had to fix that and now pypi has 3.1.2 which included the new jars. So, just creating this to keep the version numbers in sync.
V3.1.1
This release contains additions to the new user contributed COM access method to support prompting for user/password as well as support for have these credentials in the authinfo file; no prompting necessary!
Also new in this release is support for newer versions of Java in the IOM access method. As of Java10, CORBA is no longer provided in the Java installation. saspy now provides 5 thirdparty jars which, when added to the classpath along with the existing IOM client jars, provides the necessary CORBA functionality, allowing the IOM access method to now work with these newer Java releases (9, 10, 11 ...)
V3.1.0
This version has a new access method: COM. This access method was contributed by @hhubbell and is for use on Windows clients to connect via IOM using the com client instead of the Java client. The com IOM client is how SAS Enterprise Guide (EG) connects over IOM. This access method connects to any Remote Workspace server, just like the existing IOM access method does, and it can also connect to a Local Windows SAS install too, also like the Java client version.
V3.0.0
This version has a new access method: HTTP. This access method is for use with a Viya deployment running the Compute Service mico service. The Compute Service launches Compute Servers, which is roughly equivalent to IOM launching Workspace servers. The MVA session (Compute Server) is based upon the SPRE installation of the Viya deployment. That is roughly equivalent to a SAS 9.4 MVA session.
This access method does not connect to SAS 9.4 proper, nor does it connect to CAS in Viya. It still connects to MVA SAS, so all of the methods behave the same as other access methods which are connected to SAS 9.4 MVA sessions.
V2.4.5
This release just has a few updates from PR's and other issues. Just cutting it to clear out everything at master in anticipation for the next wave of features. There are two new access methods coming. An HTTP access method for getting at MVA in a Viya deployment, and a user contributed IOM via COM access method, for Windows, as an alternative the the existing IOM using the Java client. So, getting the existing changes into this release so the new features are not mixed in with these other changes.
V2.4.4
This release has a number of bug fixes for issues about list_tables, file_info, and the utf-8/utf_8 typo in the new encoding mapping table. A couple other fixes for sd2df. There are also documentation changes and enhancements. And, there is new functionality which provides support for running saspy in a Zeppelin Notebook. Zeppelin uses a different way of displaying output than Jupyter (like html) so the existing IPython code in saspy didn't work on Zeppelin. Now, there is a new key in the configuration definition you can set which will allow saspy to work in Zeppelin: ‘display’ : ‘zeppelin’,
V2.4.3
This release addresses a bug that was introduced which unconditionally imported Pandas. saspy isn't dependent on Pandas, though there's a lot of functionality that integrates with it. Still you can install, import and run it w/out Pandas. This version also has some performance enhancements for the new upload/download methods in the IOM interface. Other than those two things, it's the same as 2.4.2.