ENH: persisting tasks on a per-run basis
まだ誰も着手していません。
評価
調査の方向性
Start with the making tasks persist tutorial and the existing @pytask.mark.persist behavior. Trace how task freshness and database updates are determined, then define the per-run override options and their effects on later executions. Done means the runtime API is documented, preserves existing defaults, and has tests for rerunning, marking updated, and leaving a task stale.
索引モデルが issue の本文から書いたものです。
説明
Is your feature request related to a problem?
I'm taking about https://pytask-dev.readthedocs.io/en/stable/tutorials/making_tasks_persist.html
If I format my tasks.py file or update an unrelated task in there, then pytask will re-run the tasks. But I don't want this. I also don't want this to be a permanent feature of the task, as marked with a decorator.
Describe the solution you'd like
I want to be able to specify on a per-run basis whether or not to re-run a task if the source file changed. Ideally it should be something like
- Keep the @pytask.mark.persist as marking default behavior: If its not present, the default is to re-run on src changes. If it is present, then the default is to NOT re-run on source changes. Therefore, we don't break the old API.
- But, add a flag/API at runtime to override this default: On a per-task level be able to change the behavior. I the options should be "rerun", "don't rerun, and mark as updated", and "don't rerun, but don't mark as updated, so next time you run then the task will still appear stale". Maybe I'm not breaking down these options along the right axes, it could use more work.
API breaking implications
Per above, it shouldn't be breaking
Describe alternatives you've considered
Perhaps this warrants re-thinking the API for determining what is "up to date". Per those docs above:
Internally, the state of the dependencies, the source file, and the products are updated in the database such that the subsequent execution will skip the task successfully.
If we accumulate many more edge cases for when a task is up to date, things are going to get complicated. If there was a more official API when you define a task, eg @pytask.Task(func, ins, outs, *, should_run = None) and you could pass in (really brainstorming here)
- None (keep default behavior)
- True (rerun every time)
- A Callable[[Not sure what the args should be], bool]
- "on_dependency_change"
- "on_source_change"
- An Iterable of any of the above. If any are true, then rerun.
- 主要言語
- Python
- スター
- 146
- フォーク
- 14
- 平均マージ
- 3日 16時間
- マージ済み PR(30日)
- 34
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
pytask-dev/pytask のほかの issue
-
enhancement
難易度 5/5 1週間以上 初心者へのやさしさ 45/100
pytask-dev/pytask#985 ·
-
enhancement
難易度 5/5 1週間以上 初心者へのやさしさ 30/100
pytask-dev/pytask#786 · コメント 2 件 ·
-
bug
難易度 3/5 1〜2日 初心者へのやさしさ 42/100
pytask-dev/pytask#513 · コメント 8 件 ·
-
enhancement
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
pytask-dev/pytask#503 · コメント 1 件 · リアクション 1 件 ·
-
enhancement
難易度 4/5 3〜5日 初心者へのやさしさ 35/100
pytask-dev/pytask#320 · コメント 1 件 ·
pytask-dev/pytask の issue をすべて見る
似ている issue
-
link-check link-check:sphinx-theme
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
qgis/QGIS-Documentation#11275 ·
-
bug priority:normal ready-for-dev
難易度 2/5 1〜3時間 初心者へのやさしさ 88/100
OpenHands/extensions#626 · コメント 1 件 ·
-
難易度 1/5 1時間未満 初心者へのやさしさ 90/100
CSCfi/sd-search-api#39 ·
-
難易度 1/5 1時間未満 初心者へのやさしさ 90/100