Closed GoogleCodeExporter closed 8 years ago
Could you apply the patch in issue 86, or run the version of googlecl in the
repository? It fixes the AttributeError you see, and you should get a
meaningful error message.
Original comment by tom.h.mi...@gmail.com
on 30 Jun 2010 at 1:26
[deleted comment]
Same issue with WinXP and GoogleCL 0.9.8 : filenames with whitespaces don't
work. The error dump is shown below.
F:\manualbackups\backups\album\ellu>c:\google\googlecl\google picasa create --ti
tle "Elina Collection 3" *.jpg
Loading file *.jpg to album Elina Collection 3
Failed to upload *.jpg. (601: Found <type 'str'>, not path name or object with a
.read() method)
Original comment by ville...@gmail.com
on 5 Jul 2010 at 8:14
villejus, are you using Cygwin or some other shell that will expand the '*'?
The windows command prompt does not usually do so.
Original comment by tom.h.mi...@gmail.com
on 12 Jul 2010 at 9:25
Ugly workaround, if you're using a bash script:
title=$title
google picasa create --title "$title"
for i in *.jpg; do
google picasa post --title "$title" $i
done
Original comment by asourdi...@gmail.com
on 10 Aug 2010 at 3:48
Below is the patch which can potentially fix both cases mentioned in this
issue. At least it worked for me with the following command lines:
1. Issue with find reported by paal.nilsen:
google picasa create --title Test "$(find . -type f -name \*.png)"
2. Issue with expansion of '*' reported by villejus:
google picasa create --title Test '*.png'
I'd appreciate if you try it and report here if it works for you or not.
Ed
Original comment by bart...@gmail.com
on 16 Oct 2010 at 8:38
Attachments:
Thanks for addressing this issue, Ed.
I've committed a patch similar to Ed's that addresses the issue(s). Note that
as mentioned, the correct syntax for the "find" expansion is "$(find /path
-type f -name file*"
Expanding wildcards will work without putting them in quotes for both Unix and
Windows. So for #2, Windows and Unix users have the same command: google picasa
create "My Test Album" *.png
I've attached a patch against 0.9.11 that will fix this, and r489 in the trunk
includes it already.
Original comment by tom.h.mi...@gmail.com
on 30 Oct 2010 at 12:17
Attachments:
Made a mistake in the above patch -- all that will do is print out the
arguments that have been passed to google.py. Not terribly useful. Here's a
fixed patch (and r490 is also fixed)
Original comment by tom.h.mi...@gmail.com
on 31 Oct 2010 at 7:13
Attachments:
Original issue reported on code.google.com by
paal.nil...@gmail.com
on 30 Jun 2010 at 1:05