BUG: datetime64 hash #19724
BUG: datetime64 hash #19724
Conversation
|
Please link to previous work like PR #14622 and to the issue this is meant to solve #3836. I don't understand this resubmission: have you changed something and why? Is there a reason you didn't simply add your unique contribution to the comments there? It seems this is the third such attempt at resubmitting previous PRs - #19718, #19720, and now this one. None of these PRs have descriptions or hints that that they are resubmissions of previous work. Please refrain from wasting precious reviewer time and CI resources. |
|
Please reopen the PR so I can delete the previous commit and update it with a new one. |
|
I prefer to continue with the older PR. If there are things needed to fix there, you can submit a PR to https://github.com/walshb/numpy/tree/bw-datetime-hash-3836. |
|
I understand this, but I just wanted to clear up a few files in this PR. |
|
It appears that @shubham11941140 is trying to remove the evidence that they attempted to pass off other code as their own. Two things to note:
|
|
I am not able to commit to a closed PR. |
|
Please remove the comments that involve copying as I have mentioned the revival of an old PR. |
Reviving #14622