Legacy to versions

未关闭
#175 2 条评论 0 个 reaction 已指派 2 人 在 GitHub 查看

维护者通常 1 天内回复

@felixhekhorn 已经在做这个了。

开始于 2022年12月8日。

评估

这个 Issue 还没有评估数据。

描述

output refactor

At the moment, since we are transitioning, there are a lot of legacy objects:

  • legacy runner
  • legacy runcards
  • legacy output

About the output, there is already an issue discussing the opportunity of versioning it #106
But we need to version all the input and output we use, while the runner is a different story.

So, we need to act in two different ways.
For the IO, we will declare a candidate v1 to the current format, for both inputs (runcards) and output (operator). What is now called legacy will be instead the v0, and all the code dealing with legacy IO will be moved to eko.io.v0.
The only supported actions will be loading and upgrading to v1 format. Everything else will be dropped.
If in future we will come to a v2 version, we will create a eko.io.v1 package, with loaders and upgraders to v2.

The only thing we need to decide is if versioning the input and output together (a single __data_version__, as it is at the moment), or using two separate version numbers.
Only integer versions will be supported, since any compatible change does not require a new version.

About the runner, we will simply reimplement the current one with new elements, and find a better name than legacy (this is already discussed in #138).

主要语言
Python
星标
13
派生
9
平均合并
6 天 16 小时
30 天内合并 PR
3

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

NNPDF/eko 的其他 Issue

查看 NNPDF/eko 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。