pytask-dev / pytask-dev/pytask
ENH: a few design ideas
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 146
- Forks
- 14
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 34
Description
Some ideas I wanted to share:
-
Add an
ignoremarker.
Currently we havepersist(run if output is missing) andskip(skip the task and everything downstream). Anignoremarker could skip only the task itself while still allowing downstream tasks to run. This could be useful, for example, when dependencies or products were removed via DVC (or similar tools) and the user wants to ensure the task is not re-run. -
Should the file location be part of the task ID?
At the moment, a task is re-run if the containing file is moved. An alternative design would ignore such changes if the task content itself did not change.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the existing persist and skip marker behavior, then trace how task IDs respond when their containing file moves. Determine the intended semantics and trade-offs for the proposed ignore marker and file-location handling. Done would be an agreed design and documented scope, since the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100