Plug In
plug-in is a library that allows You to manage dependencies across Your project
code. Usage of plug-in in Your apps will result in easy-to-maintain project
structure. It guides You throughout development process by bringing the
plugin architecture into Your application. plug-in implements this architecture
for You, with explicit requirements on Your project structure.
Project status
I am actively developing this project right now. I've implemented the basic functionalities and still working on API. Right now, project is in alpha phase.
Project goals
- Supply SDK for inversion of control
- Familiar for python developers
- Fully typed
- Mix best things from IoC and python code style
- Async support
- Small codebase
Contributing
How to start
...
Commits
All commits should be structured according to Conventional Commits specification.
For answer "Which one commit type should I use?", please refer to below table.
Commit types
| Commit Type | Title | Description |
|---|---|---|
feat |
Features | A new feature |
fix |
Bug Fixes | A bug Fix |
docs |
Documentation | Documentation only changes |
style |
Styles | Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) |
refactor |
Code Refactoring | A code change that neither fixes a bug nor adds a feature |
perf |
Performance Improvements | A code change that improves performance |
test |
Tests | Adding missing tests or correcting existing tests |
build |
Builds | Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) |
ci |
Continuous Integrations | Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs) |
chore |
Chores | Other changes that don't modify src or test files |
revert |
Reverts | Reverts a previous commit |
Source: https://github.com/pvdlg/conventional-changelog-metahub/blob/master/README.md#commit-types
Metadata
Release files for pyplugin-lib 0.2.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 | Actions |
|---|---|---|---|---|
| pyplugin_lib-0.2.1.tar.gz | 23.3 kB | Without provenance | Details for pyplugin_lib-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyplugin_lib-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for pyplugin_lib-0.2.1-py3-none-any.whl |
Total release size: 56.6 kB
Release files / pyplugin_lib-0.2.1.tar.gz
| Download URL | pyplugin_lib-0.2.1.tar.gz |
|---|---|
| Size | 23.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
33f2817f8d62a836cb92e1b2cd9d8749c1a047249f7188b8d08572e9da120c2c
|
|
BLAKE2b-256 checksum How to use checksums |
22e34c35217f53a1cd2a4c5f8d66c884a6c3ebf1e862a276f9cc7dede1f9d29d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.2 CPython/3.10.12 Linux/6.8.0-59-generic
|
Release files / pyplugin_lib-0.2.1-py3-none-any.whl
| Download URL | pyplugin_lib-0.2.1-py3-none-any.whl |
|---|---|
| Size | 33.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f47591677e80d3b3711dc6fc098544377a1681fac9762bc32a6952a4f7521991
|
|
BLAKE2b-256 checksum How to use checksums |
ab669eb7bbcc6276b3812a4a851b0b62508ff879e81fd34e7de974949768c970
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.2 CPython/3.10.12 Linux/6.8.0-59-generic
|
Security for pyplugin-lib 0.2.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.