Skip to content

Commit a09ef03

Browse files
committed
prepared for release
1 parent 69177e3 commit a09ef03

File tree

4 files changed

+12
-12
lines changed

4 files changed

+12
-12
lines changed

CHANGES.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
Changelog
22
=========
33

4-
0.2.14 (????-??-??)
4+
0.2.14 (2023-07-04)
55
-------------------
66

7-
- extracted arpack_combined.jar, core.jar and mtj.jar from weka.jar to make available under Java 17
7+
- extracted arpack_combined.jar, core.jar and mtj.jar from weka.jar to make them available under Java 17
88

99

1010
0.2.13 (2023-04-26)

doc/source/conf.py

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,9 +53,9 @@
5353
# built documents.
5454
#
5555
# The short X.Y version.
56-
version = '0.2.13'
56+
version = '0.2.14'
5757
# The full version, including alpha/beta/rc tags.
58-
release = '0.2.13'
58+
release = '0.2.14'
5959

6060
# The language for content autogenerated by Sphinx. Refer to documentation
6161
# for a list of supported languages.

doc/source/docker.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ For using the image interactively, you can run the following command:
2020
.. code-block:: bash
2121
2222
docker run -u $(id -u):$(id -g) \
23-
-it fracpete/pww3:0.2.13_cpu
23+
-it fracpete/pww3:0.2.14_cpu
2424
2525
Instead of having to reinstall your packages each time you start up the container,
2626
you can map your local Weka packages into the container as follows:
@@ -29,7 +29,7 @@ you can map your local Weka packages into the container as follows:
2929
3030
docker run -u $(id -u):$(id -g) \
3131
-v $HOME/wekafiles/:/workspace/wekafiles \
32-
-it fracpete/pww3:0.2.13_cpu
32+
-it fracpete/pww3:0.2.14_cpu
3333
3434
3535
GPU
@@ -40,7 +40,7 @@ For using the image interactively, you can run the following command:
4040
.. code-block:: bash
4141
4242
docker run --gpus=all -u $(id -u):$(id -g) \
43-
-it fracpete/pww3:0.2.13_cuda10.2
43+
-it fracpete/pww3:0.2.14_cuda10.2
4444
4545
Instead of having to reinstall your packages each time you start up the container,
4646
you can map your local Weka packages into the container as follows:
@@ -49,7 +49,7 @@ you can map your local Weka packages into the container as follows:
4949
5050
docker run --gpus=all -u $(id -u):$(id -g) \
5151
-v $HOME/wekafiles/:/workspace/wekafiles \
52-
-it fracpete/pww3:0.2.13_cuda10.2
52+
-it fracpete/pww3:0.2.14_cuda10.2
5353
5454
5555
Additional Weka packages
@@ -75,11 +75,11 @@ script:
7575
7676
7777
A minimal ``Dockerfile`` (in the same directory as ``install_packages.py``) then looks
78-
like this (using pww3 0.2.13 for CPU):
78+
like this (using pww3 0.2.14 for CPU):
7979

8080
::
8181

82-
FROM fracpete/pww3:0.2.13_cpu
82+
FROM fracpete/pww3:0.2.14_cpu
8383
COPY install_packages.py /workspace/install_packages.py
8484
RUN python3 /workspace/install_packages.py
8585

setup.py

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212
# along with this program. If not, see <http://www.gnu.org/licenses/>.
1313

1414
# setup.py
15-
# Copyright (C) 2014-2022 Fracpete (pythonwekawrapper at gmail dot com)
15+
# Copyright (C) 2014-2023 Fracpete (pythonwekawrapper at gmail dot com)
1616

1717
from setuptools import setup
1818

@@ -55,7 +55,7 @@ def _read(f):
5555
"weka": ["lib/*.jar"],
5656
},
5757
include_package_data=True,
58-
version="0.2.13",
58+
version="0.2.14",
5959
author='Peter "fracpete" Reutemann',
6060
author_email='[email protected]',
6161
install_requires=[

0 commit comments

Comments
 (0)