get: `get -o` behavior should be consistent with `import -o`
Open
Nobody has claimed this yet.
p3-nice-to-have
- Dominant language
- Python
- Stars
- 15.9k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
As noted in https://github.com/iterative/dvc.org/pull/1668, get and import behave differently when using -o foo/bar.
import will fail if directory foo/ does not already exist, but get will create the directory.
dvc get should fail instead of using makedirs when foo/ does not exist to behave more consistently with other DVC commands.
Contributor guide
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
Start by comparing the CLI handling for dvc get -o and dvc import -o, focusing on where get creates parent directories. The change is done when get fails if the parent directory does not exist and its behavior matches import; add or update the relevant CLI test if one is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100