This is (another) hotfix for CNApy, this time for a jpype problem that caused a Java Virtual Machine (JVM) error after installation.
Installation Options
There are 4 alternative ways to install CNApy:
- The easiest way for any user to install CNApy is by downloading its installer, which is provided for Windows, Linux and MacOS, see Using CNApy installer for more.
- If you already have installed Python 3.10 (no other version) on your system, you can install CNApy simply through
pip install cnapy
in your console. Afterwards, you can start CNApy's GUI by running eithercnapy
or, if this doesn't work,python -m cnapy
where "python" must call your Python 3.10 installation. - If you already use conda or mamba (for mamba, just change the "conda" command to "mamba"), you can create a CNApy environment named
cnapy-1.2.2
as follows: 1) Runconda create --name cnapy-1.2.2 python=3.10 pip openjdk -c conda-forge
, 2) runconda activate cnapy-1.2.2
, 3) runpip install cnapy
. Then, you can start CNApy in the cnapy-1.2.2 conda environment by running eithercnapy
or, if this doesn't work,python -m cnapy
. Note that the cnapy conda package is currently not being updated due to licensing uncertainties. - If you want to develop CNApy, follow the instruction for the cloning and setup of the CNApy repository using git and conda or mamba in section Setup the CNApy development environment.
What's Changed
- Correct license in toml by @Paulocracy in #530
- Version 124 by @Paulocracy in #531
Full Changelog: v1.2.3...v1.2.4