Mopidy: ImportError: No module named gobject

Created on 24 Aug 2014 · 4Comments · Source: mopidy/mopidy

I have no idea why Mopidy can't install dependencies itself. It is truly annoying and unprofessional if you can not such a featured module out-of-the-box without further hassles. The error happens on Mac and Linux.

suxmac:mopidy ajung$ bin/mopidy 
Traceback (most recent call last):
  File "bin/mopidy", line 9, in <module>
    load_entry_point('Mopidy==0.19.3', 'console_scripts', 'mopidy')()
  File "/private/tmp/mopidy/lib/python2.7/site-packages/pkg_resources.py", line 378, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/private/tmp/mopidy/lib/python2.7/site-packages/pkg_resources.py", line 2566, in load_entry_point
    return ep.load()
  File "/private/tmp/mopidy/lib/python2.7/site-packages/pkg_resources.py", line 2260, in load
    entry = __import__(self.module_name, globals(),globals(), ['__name__'])
  File "/private/tmp/mopidy/lib/python2.7/site-packages/mopidy/__main__.py", line 8, in <module>
    import gobject
ImportError: No module named gobject

C-enhancement

Source

zopyx

👎15

Most helpful comment

"truly annoying and unprofessional" = insulting open source software developers you've never met. :(

bobf on 10 Dec 2015

👍6

All 4 comments

I can appreciate you may be frustrated but insulting people and then asking
for their help doesn't usually work very well.
On 24 Aug 2014 07:30, "Andreas Jung" [email protected] wrote:

I have no idea why Mopidy can't install dependencies itself. It is truly
annoying and unprofessional if you can not such a featured module
out-of-the-box without further hassles. The error happens on Mac and Linux.

suxmac:mopidy ajung$ bin/mopidy
Traceback (most recent call last):
File "bin/mopidy", line 9, in
load_entry_point('Mopidy==0.19.3', 'console_scripts', 'mopidy')()
File "/private/tmp/mopidy/lib/python2.7/site-packages/pkg_resources.py",
line 378, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/private/tmp/mopidy/lib/python2.7/site-packages/pkg_resources.py",
line 2566, in load_entry_point
return ep.load()
File "/private/tmp/mopidy/lib/python2.7/site-packages/pkg_resources.py",
line 2260, in load
entry = _import_(self.module_name, globals(),globals(), ['_name_'])
File "/private/tmp/mopidy/lib/python2.7/site-packages/mopidy/_main_.py",
line 8, in
import gobject
ImportError: No module named gobject

—
Reply to this email directly or view it on GitHub
https://github.com/mopidy/mopidy/issues/836.

kingosticks on 24 Aug 2014

LOL - did you ever try to install your software the official way in the Python world using 'pip'? This is an obvious fail. Don't complain about complains when the most basic installation steps don't work.

zopyx on 24 Aug 2014

👎9

Hi, thanks for following up on the complaint on twitter. Just yelling into the void isn't all that great for getting things fixed.

As for the problem you've run in to are hands are kinda tied. Yes we could add https://pypi.python.org/pypi/PyGObject/ but the rest of our non python dependencies, most notably the python binding for GStreamer are not on pypi. This is why http://docs.mopidy.com/en/latest/installation/#installation (which I hope you've looked at) covers how to install these missing pieces on a number of systems.

We might be able to do some install time checks to warn people trying to go the pip route about missing non-python deps, but not sure how / if that would work yet. If you have any other constructive suggestions on how this can be improved please let us know.