datalad-core: core library for the DataLad framework
Developing with datalad_core
API stability is important, just as adequate semantic versioning, and informative changelogs.
Public vs internal API
Anything that can be imported directly from any of the sub-packages in
datalad_core is considered to be part of the public API. Changes to this API
determine the versioning, and development is done with the aim to keep this API
as stable as possible. This includes signatures and return value behavior.
As an example: from datalad_core.abc import xyz imports a part of the public
API, but from datalad_core.abc.def import xyz does not.
Use of the internal API
Developers can obviously use parts of the non-public API. However, this should only be done with the understanding that these components may change from one release to another, with no guarantee of transition periods, deprecation warnings, etc.
Developers are advised to never reuse any components with names starting with
_ (underscore). Their use should be limited to their individual subpackage.
Contributing
Contributions to this library are welcome! Please see the contributing guidelines for details on scope and style of potential contributions.
1 maintainer
Metadata
1 maintainer
Release files for datalad-core 0.3.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 |
|---|---|---|---|---|
| datalad_core-0.3.0.tar.gz | 108.9 kB | Without provenance | Details for datalad_core-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| datalad_core-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for datalad_core-0.3.0-py3-none-any.whl |
Total release size: 240.0 kB
Release files / datalad_core-0.3.0.tar.gz
| Download URL | datalad_core-0.3.0.tar.gz |
|---|---|
| Size | 108.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3a3721cce5b8cb8f516e6ca8ad03a444f2db5d4be628a95d82bdea8d716db639
|
|
BLAKE2b-256 checksum How to use checksums |
f2cce67d5dbce2924184bb680e97f8270328b462c6dc41859969c325fc9f70df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Hatch/1.17.0 {"ci":null,"cpu":"x86_64","distro":{"id":"forky","libc":{"lib":"glibc","version":"2.42"},"name":"Debian GNU/Linux","version":"n/a"},"implementation":{"name":"CPython","version":"3.12.11"},"installer":{"name":"hatch","version":"1.17.0"},"openssl_version":"OpenSSL 3.0.16 11 Feb 2025","python":"3.12.11","system":{"name":"Linux","release":"7.1.3+deb14-amd64"}} HTTPX2/2.3.0
|
Release files / datalad_core-0.3.0-py3-none-any.whl
| Download URL | datalad_core-0.3.0-py3-none-any.whl |
|---|---|
| Size | 131.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ddf377c1e568314336221782c5a59273bb0f91f8cf85b24542c62750622e807e
|
|
BLAKE2b-256 checksum How to use checksums |
6d94b7123440be1490730cbef0b2e01b9d47c6d4a1b206c87289a1ca9a6cdebb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Hatch/1.17.0 {"ci":null,"cpu":"x86_64","distro":{"id":"forky","libc":{"lib":"glibc","version":"2.42"},"name":"Debian GNU/Linux","version":"n/a"},"implementation":{"name":"CPython","version":"3.12.11"},"installer":{"name":"hatch","version":"1.17.0"},"openssl_version":"OpenSSL 3.0.16 11 Feb 2025","python":"3.12.11","system":{"name":"Linux","release":"7.1.3+deb14-amd64"}} HTTPX2/2.3.0
|
Security for datalad-core 0.3.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.
