From c7532f16e5231f5fd7d4b20f82973c70bd43af36 Mon Sep 17 00:00:00 2001 From: Craig Barratt <19445341+craigbarratt@users.noreply.github.com> Date: Thu, 4 Mar 2021 21:13:16 +1100 Subject: [PATCH] doc updates prior to 1.3.1 release --- docs/conf.py | 2 +- docs/new_features.rst | 30 +++--------------------------- 2 files changed, 4 insertions(+), 28 deletions(-) diff --git a/docs/conf.py b/docs/conf.py index b6dec0a..4a64617 100644 --- a/docs/conf.py +++ b/docs/conf.py @@ -23,7 +23,7 @@ author = 'Craig Barratt' # The full version, including alpha/beta/rc tags -release = '1.3.0' +release = '1.3.1' master_doc = 'index' diff --git a/docs/new_features.rst b/docs/new_features.rst index add15ef..7e5709a 100644 --- a/docs/new_features.rst +++ b/docs/new_features.rst @@ -8,37 +8,13 @@ You can also install the master (head of tree) version from GitHub, either using Because pyscript has quite a few unit tests, generally the master version should work ok. But it's not guaranteed to work at any random time, and newly-added features might change. -.. - This release is 1.3.0, released on February 24, 2021. Here is the `documentation - `__ for this release. - -The latest release is 1.3.0, released on February 24, 2021. Here is the `documentation -`__ for that release. +This release is 1.3.1, released on March 4, 2021. Here is the `documentation +`__ for this release. Over time, the master (head of tree) version in GitHub will include new features and bug fixes. Here is the `latest documentation `__ if you want to see the development version of the documentation. -If you want to see development progress since 1.3.0, see +If you want to see development progress since 1.3.1, see `new features `__ in the latest documentation, or look at the `GitHub repository `__. - -Planned new features post 1.3.0 include: - -- Consider supporting the built-in functions that do I/O, such as ``open``, ``read`` and ``write``, which - are not currently supported to avoid I/O in the main event loop, and also to avoid security issues if people - share pyscripts. The ``print`` function only logs a message, rather than implements the real ``print`` features, - such as specifying an output file handle. Support might be added in the future using an executor job, perhaps - enabled when ``allow_all_imports`` is set. - -The new features since 1.3.0 in master include: - -None yet. - -Breaking changes since 1.3.0 include: - -None yet. - -Bug fixes since 1.3.0 include: - -None yet.