You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
shutil.move raises AttributeError if first argument is a pathlib.Path object and destination is a directory #76870
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2019-10-01.02:46:32.949>created_at=<Date2018-01-28.00:01:24.483>labels= ['type-bug', 'library', '3.9']
title='shutil.move raises AttributeError if first argument is a pathlib.Path object and destination is a directory'updated_at=<Date2019-10-01.02:46:32.941>user='https://bugs.python.org/craigh'
shutil.move should certainly accept a path object, as shutil.copy does, though it should be noted that in your example, 'path' could become out of date as it does not refresh the path information. For example, with shutil.move fixed:
test1 is now actually at '/Users/e/Development/OSS/cpython/test2/test1'
For the fix:
I did a bit of digging and the error comes from a helper method _basename that uses rstrip to remove a trailing separator, hence the error as rstrip doesn't exist for a path object (and I don't think it makes sense that it should, though that was one solution). Removing the trailing separator is, however, very important in determining the full destination path.
After trying a few different approaches, I think the simplest way is to cast the src to a string before finding its appropriate basename. I also added some comments to make it more clear why _basename is used over os.path.basename to hopefully save someone else time in the future.
A more robust option would be to explicitly handle Path objects or to handle exceptions for any dst that cannot be cast to a string. However, the current patch fixes the issue without introducing new problems.
craigh commented on Jan 28, 2018
craighmannequin
MannequinAuthor
More actions
In my test, the second call to path.absolute() is just returning the same result as the first call, which is what I would expect (as you say, the path object doesn't update automatically).
However, your output shows it returning '/Users/e/Development/OSS/cpython/test2' instead of the (now broken) path from the first call. Maybe I'm missing something?
New changeset cf57cab by Miss Islington (bot) (Maxwell A McKinnon) in branch 'master': bpo-32689: Updates shutil.move to allow for Path objects to be used as source arg (GH-15326) cf57cab
Activity
craigh commentedon Jan 28, 2018
emilyemorehouse commentedon Jan 28, 2018
Thanks for the bug report!
shutil.move should certainly accept a path object, as shutil.copy does, though it should be noted that in your example, 'path' could become out of date as it does not refresh the path information. For example, with shutil.move fixed:
>>> import os, pathlib, shutil >>> os.mkdir('test1') >>> >>> os.mkdir('test2') >>> path = pathlib.Path('test1') >>> path.absolute() PosixPath('/Users/e/Development/OSS/cpython/test1') >>> shutil.move(path, 'test2') 'test2/test1' >>> path.absolute() PosixPath('/Users/e/Development/OSS/cpython/test2')test1 is now actually at '/Users/e/Development/OSS/cpython/test2/test1'
For the fix:
I did a bit of digging and the error comes from a helper method _basename that uses rstrip to remove a trailing separator, hence the error as rstrip doesn't exist for a path object (and I don't think it makes sense that it should, though that was one solution). Removing the trailing separator is, however, very important in determining the full destination path.
After trying a few different approaches, I think the simplest way is to cast the src to a string before finding its appropriate basename. I also added some comments to make it more clear why _basename is used over os.path.basename to hopefully save someone else time in the future.
A more robust option would be to explicitly handle Path objects or to handle exceptions for any dst that cannot be cast to a string. However, the current patch fixes the issue without introducing new problems.
craigh commentedon Jan 28, 2018
In my test, the second call to path.absolute() is just returning the same result as the first call, which is what I would expect (as you say, the path object doesn't update automatically).
However, your output shows it returning '/Users/e/Development/OSS/cpython/test2' instead of the (now broken) path from the first call. Maybe I'm missing something?
emilyemorehouse commentedon Jan 31, 2018
Ah, you're right. That was a typo when I was redacting my full path. The path object remains unchanged even though the directory has moved.
Should have been:
>>> import os, pathlib, shutil >>> os.mkdir('test1') >>> os.mkdir('test2') >>> path = pathlib.Path('test1') >>> path.absolute() PosixPath('/Users/e/Development/OSS/cpython/test1') >>> shutil.move(path, 'test2') 'test2/test1' >>> path.absolute() PosixPath('/Users/e/Development/OSS/cpython/test1')test1 is now actually at '/Users/e/Development/OSS/cpython/test2/test1'
miss-islington commentedon Oct 1, 2019
New changeset cf57cab by Miss Islington (bot) (Maxwell A McKinnon) in branch 'master':
bpo-32689: Updates shutil.move to allow for Path objects to be used as source arg (GH-15326)
cf57cab
gvanrossum commentedon Oct 1, 2019
3.9 only!