V2.4.2

This release has a number of bug fixes and doc fixes, but it also has a number of enhancements.
First there are new upload and download methods which allow binary transfer of files from the local (saspy) file system to/from the SAS Server machine's file system. There are also methods for querying the remote file system and navigating it and getting file information.
Another enhancement is to automatically support the encoding setting in the configuration definitions. saspy will now set the encoding value based upon the SAS session encoding and a mapping between those and the Python values. So no more transcoding problem from not having the encoding value correctly match the encoding of the SAS session you are connected to.

V2.4.1

This is another minor release. It has some new Viya ML analytic methods (procs) added. Some various fixes. It has new methods to get filesystem information and file info from the SAS server (user feature requests). New methods to get the list of assigned librefs and for a libref get the list of members (data, view) that can be pulled over into Pandas dataframes. There's also a new autocfg.py batch script (can be run interactively), that can create a functioning sascfg_personal.py file for Local Windows connections (only).

V2.4.0

This is the rewrite of the proc generation code by Jared. It will now be much easier to write new analytic methods. There are new Viya procs included and there will be documentation added to identify how to implement new methods.

V2.3.1

This is like v2.3.0 but with a fix for pr186 to not be dependent on system options for parsing. Issue 190 showed an exposure, so this fixes that. The next version will be 2.4.0, merging in Jared's pr for the proc generation rewrite. Just creating this for the same reason of having a complete version before his, and then a version for those changes to help identify any potential regressions easily,

V2.3.0

This release has a number of enhancements and fixes sine v2.2.9. There are now SAS Automatic Variables available for programmatic determination of code success or failure. The SAS process pid itself is available off the SASsession object for programmatic determination of whether the connection is valid. These help out in batch mode where, especially. There's a new dirlist() method, doc enhancements and a number of other user contributions as well. Also, the next version will have an overhauled rewrite of the proc generation code. So this release is the snapshot before taking all of those changes.

V2.2.9

This release has a few enhancements as well as getting the documentation up to date. There is a fix for supporting Views; SAS memtype of VIEW as opposed to DATA. There was an issue with the exist() function not finding members of type view. There is also a new key in the Configuration Definition for all access methods; autoexec. This is simply a string of SAS code which will be submitted upon establishing the connection. This is simply a convenient way to have code you always want run, done for you so you don't have to submit it yourself every time you make a connection. Pre-assign librefs that you frequently use, or set some other configuration that you don't want to type in every time.
I've also updated the doc with some things that have been missing like information on setting up Grid Option Sets for routing saspy connections to specific queues with SAS Grid Manager.

V2.2.8

The main difference in this release over 2.2.7 is a fix for pre V9.4M3 translated ODS templates. The 2.2.7 release fixes a number of transcoding problems but also exposed another unknown issue. Prior to Maintenance 3 for V9.4, the translated ODS templates were in SAS Session Encoding. But as of M3 (M4, M5), the encoding was changed to be UTF-8. It was UTF-8 only that saspy handled. 2.2.8 has support for both utf-8 translated templates as well as session encoded templates.

V2.2.7

This release has a number of fixes for NLS (National Language Support), which have to do with handling multi-byte encodings in SAS better. There were some bugs which were causing bad characters to come through to Python from SAS. There is also support for more dtypes in data frames when transferring to SAS Data Sets. Missing values to NaN are also better supported when converting between data frames and SAS Data Sets.
Also, the Tabulate support is back in as it now is compatible back to Python 3.3!

V2.2.6

Had to remove Tabulate until I have time to fix the syntax errors for pre python3.5 versions, which I don't have installed at the moment. Caused failures in our internal processes that were dependent on py3.4. Will add it back when it's fixed and will run with previous python3 versions like the rest of saspy.

V2.2.5

This release has a number of fixes and enhancements from 2.2.4. There's a new PROC TABULATE implementation that was contributed. There's the ability to now specify the path to your sascfg_personal.py so it doesn't need to exist in the python search path to be used. Enhanced error messages for IOM connect failures. A fix for the reconnect feature, so when you close the connection on purpose, the workspace server won't wait the time limit before shutting down. And other fixes.