Salvador E. Tropea

You must capture all the messages, try using `2>` instead of `>` (to capture stderr, not stdout)

Hi @craigarno ! The implemented API is Octopart, looks like they moved to Nexar, which used a very different access mechanism. I don't think a Nexar ID can be used...

They don't mention API v4. So I guess it still work, but they won't give you a new key for it. I don't have time to implement a new API...

Thanks @craigarno a note: now KiCost not only supports alternatives to KitSpace, but also caches the results from it. So I hope KitSpace will become less busy as people starts...

Hi! udiskie is really nice @coldfix thanks! I'm also missing MTP support, I know nothing about D-Bus, but if I start dbus-monitor and plug my cellphone I see: ``` signal...

Oh, BTW, here is an example using dbus-python: ``` from gi.repository import GLib import dbus import dbus.mainloop.glib import re def mountDetected(sender, mount_id, data): name=data[1] uri=data[5] device=data[10]['unix-device'] if uri[:6] == 'mtp://':...

> Looks like it's gvfs. It's not _that_ basic, but one could give it a try as optional dependency. (Actually I think udiskie probably better fits the niche of users...

> but I'm actually not even sure whether this will mount an actual fuse filesystem or make the device just visible within some gvfs scope. When I used gnome-shell something...

Ok, this is really low level, at least for Python ;-) ``` import pyudev mounted = {} def log_event(action, device): if action == 'add' and device.get('ID_MTP_DEVICE'): # remove, bind, unbind...

> Nice! You seem to know more about this than me :) A pyudev based solution might also be a good option. :-) (Google "knows" more than us ;-) >...