I updated the
greader2org script (see previous article for the description of how it can help you to manage Google Reader subscriptions):
- Google password is not stored as a plain text anymore, instead it is saved in GNOME Keyring, KDE Kwallet, or other platform specific password storage.
- manual edits of
feeds.iniare no longer necessary, the script just prompts for the necessary parameters on the first run.
Python 2.6 is required, attempts to run on Python 2.5 will fail
with the import error (underlying keyring library requires
To install (or upgrade), just run:
$ sudo easy_install \ http://mekk.waw.pl/download/python/mekk.feeds-1.2.0-py2.6.egg
(this should trigger
keyring installation). As usual, to avoid
sudo and system directories pollution, you can consider
There is no need to edit
feeds.ini anymore. To change
feeds.txt location, or your Google username, just run:
$ greader2org configure
and respond to the prompts. Example:
$ greader2org configure Feeds file location (or Enter to keep /home/marcin/.feeds/feeds.txt): Your Google account name: Crocodile@gmail.com Your Google password for Crocodile@gmail.com:
Those questions are also asked automatically if necessary (on the first run, or in case of wrong username/password).
Install the new version as described above.
feeds.ini file and remove the password from there,
it is not used anymore. Instead, the script will ask for your
password interactively when run for the first time.
Password saving is implemented using keyring library by Kang Zhang, nice result of recent Google Summer of Code. It should work transparently - interactively prompting for the password on the first run (or in case of login failure), and automatically picking the correct backend.
I tested it only under GNOME, but KDE, Windows and Mac are also claimed to be handled by the library.