Documentation: http://docs.enthought.com/apptools
Source Code: http://www.github.com/enthought/apptools
The apptools project includes a set of packages that Enthought has found useful in creating a number of applications. They implement functionality that is commonly needed by many applications
apptools.io: Provides an abstraction for files and folders in a file system.
apptools.logger: Convenience functions for creating logging handlers
apptools.naming: Manages naming contexts, supporting non-string data types and scoped preferences
apptools.persistence: Supports pickling the state of a Python object to a dictionary, which can then be flexibly applied in restoring the state of the object.
apptools.preferences: Manages application preferences.
apptools.selection: Manages the communication between providers and listener of selected items in an application.
apptools.scripting: A framework for automatic recording of Python scripts.
apptools.undo: Supports undoing and scripting application commands.
Prerequisites
All packages in apptools require:
Certain sub-packages within apptools have their own specific dependencies, which are optional for apptools overall.
The apptools.preferences package requires:
The apptools.io.h5 package requires:
The apptools.persistence package requires:
Many of the packages provide optional user interfaces using Pyface and Traitsui. In additon, many of the packages are designed to work with the Envisage plug-in system, althought most can be used independently:
Installation
To install with apptools.preferences dependencies:
$ pip install apptools[preferences]
To install with apptools.io.h5 dependencies:
$ pip install apptools[h5]
To install with apptools.persistence dependencies:
$ pip install apptools[persistence]
To install with additional test dependencies:
$ pip install apptools[test]
4 maintainers
Metadata
4 maintainers
Release files for apptools 5.3.1
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 | |
|---|---|---|---|---|
| apptools-5.3.1.tar.gz | 185.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| apptools-5.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 415.4 kB
Release files / apptools-5.3.1.tar.gz
| Download URL | apptools-5.3.1.tar.gz |
|---|---|
| Size | 185.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7dd8f3a95ca02fc1c03f82cebbe6bed0f74e74fb93e4f66987fa4d8e606ff167
|
|
BLAKE2b-256 checksum How to use checksums |
c7e855a5ab9f2a158d21b93a7dfcedf59935663e519564afcf2852ffa1f5d7da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.17
|
Release files / apptools-5.3.1-py3-none-any.whl
| Download URL | apptools-5.3.1-py3-none-any.whl |
|---|---|
| Size | 230.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
964f594627e634dc673326eb59adfacedb7749a6a3279045b5b949cf4a6d1e4a
|
|
BLAKE2b-256 checksum How to use checksums |
c47c56fcf5f5a81f44cf2caac26b4f4b0b3b89e9d9da5992a5b5fe90ed427c13
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.17
|
Security for apptools 5.3.1
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.
