fuzzy-theory: Fuzzy Set Theory and Fuzzy Logic Operations in PyTorch :fire:
The fuzzy-theory library provides a PyTorch interface to fuzzy set theory and fuzzy logic
operations. It uses minimal dependencies to implement these features and is designed to be
easy to use and understand. The library is designed to be used in conjunction with PyTorch
and is built on top of PyTorch's tensor operations.
A benefit of using fuzzy-theory is that it allows for the creation of fuzzy sets and fuzzy
logic operations in a way that is compatible with PyTorch's autograd system. This means that
you can use the library to create fuzzy sets and perform fuzzy logic operations in a way that
is differentiable and can be used in neural networks and other machine learning models.
Special features :high_brightness:
- Compatible with TorchScript: Some classes may use
torch.jit.scriptortorch.jit.tracefor production environments. - Differentiable: The library is designed to be used in conjunction with PyTorch and is built on top of PyTorch's tensor operations.
- Minimal dependencies: The library uses minimal dependencies to implement these features.
- Easy to use: The library is designed to be easy to use and understand, with a simple API that is similar to PyTorch's tensor operations.
- Visualization: Formulas are written with
sympyfor LaTeX rendering and plots are stylized withscienceplotsfor publication-ready figures.
Linting :mag:
The src/ and tests/ trees are linted separately, since test code is intentionally held
to different standards than library code (e.g. white-box tests reaching into
private/internal attributes is expected, not a defect).
# lint the library itself (this is what CI runs)
pylint src/fuzzy
# lint the test suite, using its own scoped config (tests/.pylintrc)
pylint --rcfile=tests/.pylintrc tests
The --rcfile=tests/.pylintrc flag is required - pylint's config discovery only searches
upward from the current working directory, so a .pylintrc placed inside tests/ is not
picked up automatically by a bare pylint tests invocation from the repository root.
Metadata
Release files for fuzzy-theory 0.1.0
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 |
|---|---|---|---|---|
| fuzzy_theory-0.1.0.tar.gz | 89.9 kB | Without provenance | Details for fuzzy_theory-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fuzzy_theory-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for fuzzy_theory-0.1.0-py3-none-any.whl |
Total release size: 203.1 kB
Release files / fuzzy_theory-0.1.0.tar.gz
| Download URL | fuzzy_theory-0.1.0.tar.gz |
|---|---|
| Size | 89.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
109ad96b2412ec3322800d9d42208d135379356f4b1f072e5df3b0b4da6af0e4
|
|
BLAKE2b-256 checksum How to use checksums |
f6a26ab72aad4e22a485521a5b40dedbae19879559a4bfa28dc4337191166650
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / fuzzy_theory-0.1.0-py3-none-any.whl
| Download URL | fuzzy_theory-0.1.0-py3-none-any.whl |
|---|---|
| Size | 113.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1f71729f9857cc374c020773387e30d5513ebdee01da5f2b3371292bee9efb59
|
|
BLAKE2b-256 checksum How to use checksums |
87d2ccd91e0468268d6decfd6bf3b9d3f49941a5de832e5178cd1058f0f1cffc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for fuzzy-theory 0.1.0
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.