===========
.. image:: https://pypip.in/v/leap.common/badge.png
:target: https://crate.io/packages/leap.common
A collection of shared utils used by the several python LEAP subprojects.
* leap.common.cert
* leap.common.checks
* leap.common.config
* leap.common.events
* leap.common.files
* leap.common.testing
Library dependencies
--------------------
* ``protobuf-compiler``
* ``libssl-dev``
Python dependencies
-------------------
* See ``pkg/requirements.pip``
0.3.5 Nov 1:
o Move get_email_charset to this module.
0.3.4 Oct 4:
o Add cert bundle including ca-cert certificate. Closes #3850.
0.3.3 Sep 20:
o Fix events server exception raising when port is occupied by some
other process. Closes #3515.
0.3.2 Sep 06:
o Use dirspec instead of plain xdg. Closes #3574.
o Correct use of CallbackAlreadyRegistered exception.
0.3.1 Aug 23:
o Add libssl-dev requirement for pyOpenSSL.
o Make the server ping call be async inside events'
ensure_server. Fixes #3355.
o Requirements in setup are taken from requirements.pip
o Updated requirements.
o Add IMAP_UNREAD_MAIL event.
o Add events for SMTP relay signaling. Closes #3464.
o Add events for imap and keymanager notifications. Closes: #3480
o Add versioneer to handle versioning.
0.3.0 Aug 9:
o OSX: Fix problem with path prefix not returning the correct
value. Fixes #3273.
o Check if schema exists before load a config. Related to #3310.
o Handle schemas and api versions in base class. Related to #3310.
0.2.7 Jul 26:
o Refactor events so components are now called clients. Closes #3246
o Add leap_check helper method, to use whenever leap_assert does not
apply. Related to #3007.
0.2.6 Jul 12:
o Improve leap_assert so that it only prints the traceback from the
leap_assert call up. Closes #2895
o Add OSX temp directories to the basetests class.
0.2.5 Jun 28:
o Bugfix: use the provider's default language as default
string. Also take care (and note) a possible case with a
problematic provider misconfiguration. Closes #3029.
o Add data files to setup and manifest (certificates for tests)
o Allow absolute paths in baseconfig.load
o Fix deprecation warnings
o Fix attempt to fetch private keys from server.
o Fix missing imports
o Add possibility of unregistering callbacks for a signal.
o Add a mechanism for events signaling between components.
o Prioritize the path_extension in the which method so it finds our
bundled app before the system one, if any.
o Move the Key Manager to leap client repository.
o Move symmetric encryption code to leap.soledad.
o Refactor opengpg utility functions implementation so it uses a
context manager.
o Add OpenPGP sign/verify
o Add RAISE_WINDOW event
o Add AES-256 (CTR mode) encrypting/decrypting functions using
PyCrypto.
Metadata
Release files for leap.common 0.3.5-1-g754f89f
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 | Actions |
|---|---|---|---|---|
| leap.common-0.3.5-1-g754f89f.tar.gz | 171.7 kB | Without provenance | Details for leap.common-0.3.5-1-g754f89f.tar.gz |
Release files / leap.common-0.3.5-1-g754f89f.tar.gz
| Download URL | leap.common-0.3.5-1-g754f89f.tar.gz |
|---|---|
| Size | 171.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
01de08961c00ad0e941b7e8fbd54a5fededc8e024d489a3e0b31e5b76e4749de
|
|
BLAKE2b-256 checksum How to use checksums |
5636441dfbf112892939550f383bd7641b75075e5a24e89bc46bd93b46e162c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for leap.common 0.3.5-1-g754f89f
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.