datalad/datasalad

Issues

• Move `UnsetValue` to a `consts` (or similar) module

  #53 opened a month ago
  0

• Adopt `Settings.get()` implementation from `datalad-core`'s `ConfigManager.get()`

  #52 opened a month ago
  0

• tag got removed

  #45 opened 2 months ago
  4

• Test breaks on windows when upgrading Python 3.9->3.12

  #44 opened 2 months ago
  1

• Adopt `decode_bytes` test and fix from datalad-next

  #38 opened 4 months ago
  0

• `decode_bytes()` improper error handling

  #35 opened 4 months ago
  5

• `test_returncode_available_from_generator_with_exception` unreliable on windows

  #32 opened 4 months ago
  2

• Import candidate: `datalad-next.itertools`

  #25 opened 5 months ago
  0

• coverage: Can't combine line data with arc data

  #24 opened 5 months ago
  1

• Import candidate: `CommandError`

  #16 opened 5 months ago
  0

• Add type-annotation check workflow

  #12 opened 5 months ago
  0

• Decide SemVer vs CalVer

  #11 opened 5 months ago
  1

• Consider adopting conventional commit messages

  #10 opened 5 months ago
  6

• Import candidate: `iter_subproc`

  #9 opened 5 months ago
  0

• Add scriv setup

  #8 opened 5 months ago
  1

• Import candidate: special remote tooling

  #7 opened 6 months ago
  3

• Policy Q: Adopt a linter/formatter?

  #2 opened 6 months ago
  0