[issue32442] Result of pathlib.Path.resolve() with UNC path is not very useful

[Tzu-ping Chung]

Tzu-ping Chung <uranusjr at gmail.com> added the comment:

@Eric

You’re correct, this is not the exact output. I tested the commands with a different path, but didn’t format them correctly when I convert them to use a generic example. Sorry for the confusion.


@Eryk

I found my problem. I was doing some os.rename and shutil stuff that constantly fails when moving and copying things using UNC paths, but works flawlessly when I convert them to use drives. I assumed it’s because the UNC, but after a more involved debugging I find all UNC calls work by themselves, only fail when I combine them. I guess it is due to some strange Windows thing, maybe UNC file stat can’t update fast enough for the next call to get the correct state or something.

The attached recipe worked very well. Thanks for the help!

I’m closing this since the problem is likely not Python-related. Sorry for the disturbance.

----------
resolution:  -> not a bug
stage:  -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue32442>
_______________________________________