This release is a pre-release and may not be stable for production use.
Currently only as placeholder (because a base package jtypes.jvm is still in development)
jtypes.pyjnius
Dynamic access to Java classes from Python.
Overview
jtypes.pyjnius is a bridge between Python and Java, allowing these to intercommunicate.It is an effort to allow python programs full access to Java class libraries.jtypes.pyjnius is a lightweight Python package, based on the ctypes or cffi library.It is an almost fully compliant implementation of Kivy Team’s PyJNIus package by reimplementing whole its functionality in a clean Python instead of Cython.
About PyJNIus:
Borrowed from the original website:
PyJNIus is a Python library for accessing Java classes.
A minimal PyJNIus example looks something like this:
Quick overview
>>> from jnius import autoclass >>> System = autoclass('java.lang.System') >>> System.out.println('Hello world') Hello world >>> Stack = autoclass('java.util.Stack') >>> stack = Stack() >>> stack.push('hello') >>> stack.push('world') >>> print(stack.pop()) world >>> print(stack.pop()) hello
Requirements
Either the Sun/Oracle JRE/JDK or OpenJDK.
Installation
Prerequisites:
Python 2.7 or higher or 3.4 or higher
2.7 and 3.6 are primary test environments.
For usage with python-for-android:
Install a distribution
pip and setuptools
To install run:
python -m pip install --upgrade jtypes.pyjnius
To ensure everything is running correctly you can run the tests using:
python -m jt.jnius.tests
Development
Visit development page
Installation from sources:
Clone the sources and run:
python -m pip install ./jtypes.pyjnius
or on development mode:
python -m pip install --editable ./jtypes.pyjnius
Prerequisites:
Development is strictly based on tox. To install it run:
python -m pip install tox
License
Copyright (c) 2014-2018 Adam KarpierzLicensed under the MIT LicensePlease refer to the accompanying LICENSE file.
Changelog
1.1.4b4 (2018-11-08)
Synchro with pyjnius master branch.
Update of the required setuptools version.
Minor setup and tests improvements.
1.1.4b0 (2018-10-26)
Synchro with pyjnius master branch.
1.1.2b4 (2018-05-23)
Bug fixes in jnius_config.
Synchro with pyjnius master branch.
1.1.2b3 (2018-05-22)
Update of the required setuptools version.
1.1.2b2 (2018-02-26)
Improvement and simplification of setup and packaging.
1.1.2b1 (2018-01-29)
Development moved to github.
General improvements and update.
1.1.2a0 (2017-04-01)
Development version.
1.1.0b2 (2017-01-21)
Documentation update.
1.1.0b1 (2017-01-01)
First beta release.
1.1.0a1 (2014-11-30)
Initial version.
Metadata
Release files for jtypes.pyjnius 1.1.4b4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| jtypes.pyjnius-1.1.4b4.zip | 70.4 kB | Without provenance | Details |
Release files / jtypes.pyjnius-1.1.4b4.zip
| Download URL | jtypes.pyjnius-1.1.4b4.zip |
|---|---|
| Size | 70.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
00673560577932424b53bb952e598cc881a4f54bab4a5c41a5f5245102f5035a
|
|
BLAKE2b-256 checksum How to use checksums |
0c5fe7ef92517f993bcaebd5ed521a22506d318cce49f41d119d816d4d4ace88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/3.6
|
Security for jtypes.pyjnius 1.1.4b4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.