From 9b7dec6326536d2cb4314ec18c5933d26b490efc Mon Sep 17 00:00:00 2001 From: David Rafferty Date: Mon, 25 Mar 2019 13:55:31 +0100 Subject: [PATCH] Prepare for release --- README.rst | 10 +++++----- bdsf/_version.py | 4 +++- doc/source/conf.py | 9 ++++++--- doc/source/whats_new.rst | 3 ++- 4 files changed, 16 insertions(+), 10 deletions(-) diff --git a/README.rst b/README.rst index 4fd941a..4d551d1 100644 --- a/README.rst +++ b/README.rst @@ -16,7 +16,7 @@ The documentation is currently hosted at http://www.astron.nl/citt/pybdsf Installation ------------ Installation is done through ``pip``, e.g. ``pip install .`` if you cloned the repository -or ``pip install https://github.com/lofar-astron/PyBDSF/archive/v1.8.15.tar.gz`` to install the latest release. +or ``pip install https://github.com/lofar-astron/PyBDSF/archive/v1.9.0.tar.gz`` to install the latest release. External requirements include the ubuntu packages (or similar packages in another Linux distribution): @@ -24,13 +24,13 @@ External requirements include the ubuntu packages (or similar packages in anothe * ``libboost-python-dev`` * ``libboost-numpy-dev`` (Only if boost > 1.63) * ``python-setuptools``. - + Also, a working ``numpy`` installation is required. At runtime, you will need ``scipy`` and either ``pyfits`` and ``pywcs`` or ``python-casacore`` or ``astropy``. -If you install as a user not using conda, use ``pip install --user``. -Make sure to use similar versions for gcc, g++ and gfortran -(use update-alternatives if multiple versions of gcc/g++/gfortran are present on the system). +If you install as a user not using conda, use ``pip install --user``. +Make sure to use similar versions for gcc, g++ and gfortran +(use update-alternatives if multiple versions of gcc/g++/gfortran are present on the system). In this case, the script ``pybdsf`` is installed in ``~/.local/bin``, so you might want to add that to your ``$PATH``. Installation on MacOS / OSX is more involved, you will need the packages mentioned above, for example installed with Homebrew. diff --git a/bdsf/_version.py b/bdsf/_version.py index 8e43f71..cd56a00 100644 --- a/bdsf/_version.py +++ b/bdsf/_version.py @@ -4,7 +4,7 @@ """ # Version number -__version__ = '1.9.0rc' +__version__ = '1.9.0' # Changelog @@ -12,6 +12,8 @@ def changelog(): """ PyBDSF Changelog. ----------------------------------------------------------------------- + 2019/04/25 - Version 1.9.0 + 2018/10/18 - Add support for Python 3 2018/10/18 - Fix various minor bugs diff --git a/doc/source/conf.py b/doc/source/conf.py index f8162f1..bc7a6e6 100644 --- a/doc/source/conf.py +++ b/doc/source/conf.py @@ -25,7 +25,10 @@ # Add any Sphinx extension module names here, as strings. They can be extensions # coming with Sphinx (named 'sphinx.ext.*') or your custom ones. -extensions = ['sphinx.ext.pngmath'] +extensions = [ + 'sphinx.ext.autodoc', + 'sphinx.ext.mathjax', +] # Add any paths that contain templates here, relative to this directory. templates_path = ['_templates'] @@ -41,7 +44,7 @@ # General information about the project. project = u'PyBDSF' -copyright = u'2018, David Rafferty and Niruj Mohan' +copyright = u'2019, David Rafferty and Niruj Mohan' # The version info for the project you're documenting, acts as replacement for # |version| and |release|, also used in various other places throughout the @@ -50,7 +53,7 @@ # The short X.Y version. version = '1.9' # The full version, including alpha/beta/rc tags. -release = '1.9.0rc' +release = '1.9.0' # The language for content autogenerated by Sphinx. Refer to documentation # for a list of supported languages. diff --git a/doc/source/whats_new.rst b/doc/source/whats_new.rst index c87e900..413ffa9 100644 --- a/doc/source/whats_new.rst +++ b/doc/source/whats_new.rst @@ -3,7 +3,8 @@ ********** What's New ********** -Version 1.9.0 (): + +Version 1.9.0 (2019/04/25)): * Add support for Python 3