Can we move this method to the end of the class underneath a version check for < 3.14? https://docs.python.org/3/library/pathlib.html#pathlib.Path.move

If you still are encountering static analysis errors at that point then let's just ignore them with comments.

I was torn on this, but if we agree to ignore the static analysis with comments that is fine with me.

Well it works now.

Unresolving this temporarily: could you please check if the behavior of the standard library function is the same (I think it is) and if so move the definition here under an if statement so that it isn't defined on 3.14+?

It is not the same logic. In 3.14, the logic is actually

def move(self, target):
        """
        Recursively move this file or directory tree to the given destination.
        """
        # Use os.replace() if the target is os.PathLike and on the same FS.
        try:
            target = self.with_segments(target)
        except TypeError:
            pass
        else:
            ensure_different_files(self, target)
            try:
                os.replace(self, target)
            except OSError as err:
                if err.errno != EXDEV:
                    raise
            else:
                return target.joinpath()  # Empty join to ensure fresh metadata.
        # Fall back to copy+delete.
        target = self.copy(target, follow_symlinks=False, preserve_metadata=True)
        self._delete()
        return target

And it definitely handles things differently.

I'm okay with switching to the new version and updating logic/tests accordingly. My preference is to always rely on built-in functionality. If this is a bit much of a lift feel free to simply rename this method to something else, that should be quick.

Unresolving this temporarily: could you please check if the behavior of the standard library function is the same (I think it is) and if so move the definition here under an if statement so that it isn't defined on 3.14+?

I'm okay with switching to the new version and updating logic/tests accordingly. My preference is to always rely on built-in functionality. If this is a bit much of a lift feel free to simply rename this method to something else, that should be quick.