My Exes
It's not a package about finding your exes!
Developing a deep learning model usually includes running different experiments and you want to keep track of them. So, you need to log all the parameters and losses, etc and save them somewhere.
This is where MyExes comes in handy! It's a simple package that provides MyEx class which can be used for logging experiments. For each experiments you need to make a yaml file containing the experiment name and its parameters. Then you can make an instance of MyEx with this yaml file as input. You can then use it to log any data you want.
Installation
You can install my exes using pip:
pip install my-exes
1 maintainer
Metadata
1 maintainer
Release files for my-exes 0.1.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| my_exes-0.1.7.tar.gz | 7.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| my_exes-0.1.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.1 kB
Release files / my_exes-0.1.7.tar.gz
| Download URL | my_exes-0.1.7.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a489f034d33b4bcea2404eef7f74625e76e7d0b806cb3fc6ab7aeaf89c64be4e
|
|
BLAKE2b-256 checksum How to use checksums |
0e567404322a85443a88b806ef131ffa1c29c5dbf686477a2fe15bebdaffefe9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency logRelease files / my_exes-0.1.7-py3-none-any.whl
| Download URL | my_exes-0.1.7-py3-none-any.whl |
|---|---|
| Size | 7.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c5dc71e39721306e38ef65ef940e3fce352253e4e0dc267fc1a97edeb8809b9f
|
|
BLAKE2b-256 checksum How to use checksums |
3bd65a10ef4475ebc77b4dc1d9ba23e24ae5494789738502f95ffe1f25ec1c76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 18, 2026.
Transparency log
