Refactor `eko.io.runcards.Legacy`

Open
#473 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reading the remaining discussion in issue #175 and pull request #417, then inspect eko.io.runcards.Legacy to see what compatibility work remains. The issue proposes renaming or moving it and deciding how long to maintain it, but gives no acceptance criteria; clarify the intended scope and compatibility policy before implementation.

Written by the indexing model from the issue text.

Description

output refactor

Left over from https://github.com/NNPDF/eko/pull/417

then continuing from https://github.com/NNPDF/eko/issues/175:

  • we still have eko.io.runcards.Legacy: 1. we should rename that to NnpdfDb or similar (and maybe move it?) and 2. I guess we need to maintain that also midterm (or even forever)
Dominant language
Python
Stars
13
Forks
9
Avg merge
6d 16h
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NNPDF/eko

All issues in NNPDF/eko

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.