Postr 0.3
Postr 0.3 is out. A few typo fixes in my code, and an update to the latest flickrapi.py to fix uploads after the Flickr servers decided to be more pedantic. This was proof that I am the only user of Postr, as it didn't work for a good week or so.
- Update flickrapi.py to version 10
- Fix references to the token
You can follow the development in the Bazaar branch, or get the Postr 0.3 tarball.
Posted by francesco at Sat Dec 16 12:10:47 2006:
.. or the proof that i'm too lazy to report malfunctions. i tried postr 0.2 just a few days ago and when it failed uploading pictures without saying a word i just assumed that it was going to be fixed soon. Sorry for that and many thanks for your efforts, it's a very useful piece of software. By the way, is there a way to use it as a nautilus script?
Posted by sven at Sat Dec 16 13:32:14 2006:
Posted by Ross at Sat Dec 16 13:32:51 2006:
Hehehe, I do have users!
I plan on adding a nautilus extension, so you can add images from the context menu.
Posted by Ross at Sat Dec 16 13:36:32 2006:
I plan on adding a nautilus extension, so you can add images from the context menu.
Sven: I have never used it and hadn't really thought about it, but I guess that would be a logical extension. Patches welcome. :)
Posted by Austin at Sat Dec 16 17:34:01 2006:
I tried to use it about a week ago :)
A couple of errors came up. I'm running Debian unstable (apparently using python 2.4 these days), and the 0.3 tarball.
I had to comment out the first "import gtk" line to get it to not crash ("AssertionError: pygtk.require() must be called before importing gtk")
After that was done, I get the following error when trying to run it: rsp: error 108: Invalid frob
After googling around for that error, it seems that flickr isn't liking your API key, or something. Do I have to get my own key to use postr?
Posted by Ross at Sat Dec 16 17:40:20 2006:
A couple of errors came up. I'm running Debian unstable (apparently using python 2.4 these days), and the 0.3 tarball.
I had to comment out the first "import gtk" line to get it to not crash ("AssertionError: pygtk.require() must be called before importing gtk")
After that was done, I get the following error when trying to run it: rsp: error 108: Invalid frob
After googling around for that error, it seems that flickr isn't liking your API key, or something. Do I have to get my own key to use postr?
I've fixed the "import gtk" error, some people require that and some don't, so I didn't notice that.
I've no idea why you get invalid frob, as I've been uploading with those keys recently. You don't need to use your own keys, the keys are per-app not per-user. Did Postr pop up a web browser to get you to authenticate it? Ah. I bet you don't have a binary called "firefox" any more, as Sid has "iceweasel" instead. That would break it. I shall work up a fix.
Posted by Austin at Mon Dec 18 00:49:09 2006:
I've no idea why you get invalid frob, as I've been uploading with those keys recently. You don't need to use your own keys, the keys are per-app not per-user. Did Postr pop up a web browser to get you to authenticate it? Ah. I bet you don't have a binary called "firefox" any more, as Sid has "iceweasel" instead. That would break it. I shall work up a fix.
Yup, I get a browser window asking for permission, which I have granted. I haven't updated in the last few weeks, so I don't think I have iceweasel yet.
postr seems to bail with the complaint about "invalid frob" just after popping up the browser window.
I'm going to hack around a little & see what I can see. I'll post another comment if I find anything, if not I'll pull the bzr branch (once I figure out how :) and try that.
Posted by Austin at Sat Dec 30 20:51:36 2006:
postr seems to bail with the complaint about "invalid frob" just after popping up the browser window.
I'm going to hack around a little & see what I can see. I'll post another comment if I find anything, if not I'll pull the bzr branch (once I figure out how :) and try that.
Aha. The problem I was having was caused by the call to os.system on line 487 of flickr.api returning immediately. I have my browser set to open a new tab in an existing window, so the program wouldn't wait for the permissions to be granted before continuing. I changed the browser to "links", and that fixed things so that I now have a cached token on disk. The cached token seems to work as desired.
I don't know why that would be a huge problem, given that on the second run of the program flickr should have noticed that the permissions have been granted and allowed it throught, but I don't know anything about the flickr api.
I had to fix things up a little from my previous "fix", and add an "import gtk" line at line 17 of the file postr. I imagine your fix for the import gtk stuff was more elegant than my hack.
So it works for me now. Whee! Hopefully my experience helps you out. If I make any changes I'll send 'em along to you.
Posted by Austin at Sat Dec 30 21:14:43 2006:
I don't know why that would be a huge problem, given that on the second run of the program flickr should have noticed that the permissions have been granted and allowed it throught, but I don't know anything about the flickr api.
I had to fix things up a little from my previous "fix", and add an "import gtk" line at line 17 of the file postr. I imagine your fix for the import gtk stuff was more elegant than my hack.
So it works for me now. Whee! Hopefully my experience helps you out. If I make any changes I'll send 'em along to you.
Last comment for a bit :)
I uploaded one of eight photos. Unfortunately, it segfaulted with no useful information after completing the first image. shrug
I'll probably try again later, but for now, it's back to using the web form for me. Thanks, though, for your effort on this app (and sound juicer, for that matter, I use it all the time).
Posted by Ross at Sat Dec 30 21:32:04 2006:
I uploaded one of eight photos. Unfortunately, it segfaulted with no useful information after completing the first image. shrug
I'll probably try again later, but for now, it's back to using the web form for me. Thanks, though, for your effort on this app (and sound juicer, for that matter, I use it all the time).
