Incomplete requirements on Mac

[criswell]

This is actually the same error mentioned here
http://stackoverflow.com/questions/12758591/python-text-to-speech-in-macintosh

From that issue, you see the following stack trace:

File "/Users/manabchetia/Documents/Codes/Speech.py", line 2, in <module>
    engine = pyttsx.init()
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pyttsx-1.0.egg/pyttsx/__init__.py", line 39, in init
    eng = Engine(driverName, debug)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pyttsx-1.0.egg/pyttsx/engine.py", line 45, in __init__
    self.proxy = driver.DriverProxy(weakref.proxy(self), driverName, debug)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pyttsx-1.0.egg/pyttsx/driver.py", line 64, in __init__
    self._module = __import__(name, globals(), locals(), [driverName])
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/pyttsx-1.0.egg/pyttsx/drivers/nsss.py", line 18, in <module>
ImportError: No module named Foundation

From some digging, it seems to depending on pyobjc under Mac OS X. However, I make no guarantee that is the only missing dependency...only the one we encountered when we were trying to make it work on Mac.

[parente]

Will doc basic install instructions using pip on current versions of Windows, OSX, and Ubuntu.

[criswell]

Honestly, I use it under Linux, and it was pretty straight forward for Arch, Debian, and Ubuntu.

However, when I was trying to help a friend get it running on OSX it was a royal pain. We eventually figured out that we needed

 --system-site-packages

with virtualenv to get access to Foundation (which is part of OSX base I guess?)

Granted, that may not have been the correct thing to do. So, I'll defer to someone who knows more about OSX than I :-)

EDIT: I should note that this is installing in a virtualenv. Since this package seems to be there by default in OSX, it may not even be a requirement if you install it all site-wide.

[parente]

Given how useful and common virtualenv is these days, I don't mind documenting installs with and without it. The doc is sorely lacking at the moment in both areas.