[issue16812] os.symlink can return wrong FileExistsError/WindowsError information

Serhiy Storchaka added the comment: issue13775, issue16074, and issue16812 all are virtually about the same bug. There is no working patch in any issue, but the discussion in issue16074 is longer. -- resolution: -> duplicate stage: -> committed/rejected status: open -> closed superse

[issue16812] os.symlink can return wrong FileExistsError/WindowsError information

Sijin Joseph added the comment: Behavior for symlink is as follows >>> os.symlink('non-existent-name', 'existing-name') Traceback (most recent call last): File "", line 1, in PermissionError: [WinError 5] Access is denied: 'non-existent-name' The error message is misleading, but can be fixed

[issue16812] os.symlink can return wrong FileExistsError/WindowsError information

Sijin Joseph added the comment: This looks to work correctly in default branch, >>> os.link('non-existent-name', 'new-name') Traceback (most recent call last): File "", line 1, in FileNotFoundError: [WinError 2] The system cannot find the file specified: 'non-existent-name' -- nosy:

[issue16812] os.symlink can return wrong FileExistsError/WindowsError information

Andrew added the comment: I tested this on FreeBSD 9.1, and the error message is correct there. -- ___ Python tracker ___ ___ Python-b

[issue16812] os.symlink can return wrong FileExistsError/WindowsError information

Serhiy Storchaka added the comment: See also issue16074. -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailin

[issue16812] os.symlink can return wrong FileExistsError/WindowsError information

New submission from Andrew: When attempting to make a symlink using a name that already exists, a FileExistsError is raised (and rightfully so), but it lists the source name rather than the destination name. However, the existing destination name is what causes the exception to be raised, not