Should `force_identical_write` be available for `pin_upload`?
Open
Nobody has claimed this yet.
.compatibility
.question
- Dominant language
- Python
- Stars
- 59
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
I don't think this is the behaviour of R pins, but it seems to me it would be helpful to add for the same reasons as for pin_write.
It's possible that the default would be force_identical_write=True rather than False for this function - partly for consistency with R pins, and partly to avoid breaking backward compatibility unnecessarily.
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 at the pin_upload entry point and compare its options and behavior with pin_write, using the issue's reference to R pins as context. Decide whether force_identical_write should be accepted and which default preserves compatibility, then verify the chosen behavior for identical uploads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100