2
0
Fork
You've already forked datalad-core
0
Core components of the DataLad framework [public mirror] https://hub.datalad.org/datalad/datalad-core
  • Python 100%
Michael Hanke 0e470040f1
 test: test_datasets[ds3] had incomplete .gitmodules 
It only listed the newly added `subm3`, but was lacking the records
of `subm1` and `subm1`.
This is now fixed, but properly incrementing the file content.
No test required a change in response to this fixture fix.
2026年06月09日 14:42:52 +02:00
.forgejo/workflows rf: switch to Python 3.11 as the minimum supported version 2026年03月19日 18:19:20 +01:00
datalad_core test: test_datasets[ds3] had incomplete .gitmodules 2026年06月09日 14:42:52 +02:00
docs doc: include test utilities and fixtures 2026年06月03日 07:13:38 +02:00
tools/appveyor feat: add dependency on git-annex 2025年06月08日 16:19:14 +02:00
.appveyor.yml ci: test require more space 2025年10月28日 19:46:10 +01:00
.changelog.md.j2 chore: migrate changelog links to hub.datalad.org 2026年05月28日 21:26:16 +02:00
.gitignore chore: dynamic version setup 2024年09月20日 13:46:14 +02:00
.noannex doc: initial commit with basic information 2024年09月20日 09:39:22 +02:00
.readthedocs.yaml chore: let docs use RTD theme, tune doc setup 2024年10月08日 08:16:14 +02:00
CHANGELOG.md chore: migrate changelog links to hub.datalad.org 2026年05月28日 21:26:16 +02:00
conftest.py test: fixture for the datalad hub's test resources 2026年06月09日 14:41:49 +02:00
CONTRIBUTING.md rf: switch to Python 3.11 as the minimum supported version 2026年03月19日 18:19:20 +01:00
LICENSE doc: initial commit with basic information 2024年09月20日 09:39:22 +02:00
pyproject.toml chore: annotate pyproject to avoid missing dependency declarations in the future 2026年06月03日 09:15:11 +02:00
README.md chore: homogenize badges with datasalad, codecov removed, requires GitHub 2026年01月22日 14:50:40 +01:00

datalad-core: core library for the DataLad framework

PyPI version fury.io Documentation Status Hatch project

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.