In our documentation we detail being able to install the `all` extra
as a shorthand for installing all the available extra packages that WA
may require however this was actually implemented as `everything`.
To ensure that a compatible version of devlib is installed on the system
keep track of the version of devlib that is required by WA and provide a
more useful error message if this is not satisfied.
Add a command to create a PostgreSQL database with supplied parameters
which draws its structure from the supplied schema (Version 1.1). This
database is of a format intended to be used with the forthcoming WA
Postgres output processor.
- Update 'setup.py' package name to 'wlauto' as 'wa' is already taken on
PyPi and update documentation accordingly.
- Update old references to Python 2.7
- Add URL for the package pointing to the GitHub repo
- Add -s option to sdist command that strips away the git commit
hash from the generated package version (needed for upload to
PyPI).
Update the documentation and build system for producing documentation for
WA3 with support for automatic building on readthedocs.
Note: This is currently a WIP.
For some reason the automatic install of pandas will fail compilation
due to an issue with numpy. A workaround for this issue is to specify
numpy in `setup_requires` as mentioned in https://github.com/numpy/numpy/issues/2434
Pandas is already widely used in WA and devlib for fast numerical table
manipulation in various instruments and output processors. Up to this
point, it has been an optional dependency.
Over the last couple of years, the package has become very wide spread,
and is available in repos for virtually every major distro. There is now
little reason not to require it as a mandatory dependency.
Changing the way target descriptions work from a static mapping to
something that is dynamically generated and is extensible via plugins.
Also moving core target implementation stuff under "framework".
In the process removed modules and boot_strap.py. Also Renamed extensions Plugins.
Louie is now monkey patched rather than containing a modified version in external
On Unix, pip will change current working directory to whereever it has
extracted the downloaded package. On Mac OSX, it does not appear to do
that. To get around this difference, specify paths in setup.py relative
to the location of setup.py, rather than the current working directory.
