Consider replacing SFTP.rename with SFTP.posix_rename in 3.0 #1016
Milestone
Comments
Pro tip, maybe leave ticket triage for later in the day...clearly not awake enough not to miss stuff. We added So this feels like it should just be a documentation-only "fix" (which was going to be another ticket, but now, no point) to try and help folks like the submitter of #1012 notice quicker that the behavior they are seeking does exist. |
bitprophet
added a commit
that referenced
this issue
Jul 13, 2017
dkhapun
pushed a commit
to cyberx-labs/paramiko
that referenced
this issue
Jun 7, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As per #1012 it's easy for folks caring about the details to get confused by the current, legacy behavior of SFTP file renaming. One way to solve this is for us to declare the old behavior to be bad/incorrect, and to just nuke it in favor of the 'POSIX' style rename in a major release.
I'd still like to know more about the differences & see if there's any info on why the 'non-POSIX' behavior was initially added (my guess is that it's just a naive first implementation, but dunno) but that's mostly a sanity check.
The text was updated successfully, but these errors were encountered: