3.4rc2 and pip on windows

Terry Reedy tjreedy at udel.edu
Tue Mar 4 06:32:56 CET 2014

On 3/3/2014 2:47 PM, Mark Lawrence wrote:
> On 03/03/2014 00:07, Terry Reedy wrote:
>> On 3/2/2014 6:55 PM, Mark Lawrence wrote:
>>> Trying to install pyttsx, it doesn't strike me as very clever that, as
>>> seen below, you get "Successfully installed pyttsx" despite the syntax
>>> errors and you can't actually do an import.
>>> c:\Users\Mark\CrossCode>c:\Python34\Scripts\pip3.4.exe install pyttsx
>>> Downloading/unpacking pyttsx
>>>    Downloading pyttsx-1.1.tar.gz
>>>    Running setup.py
>>> (path:C:\Users\Mark\AppData\Local\Temp\pip_build_Mark\pyttsx\setup.py)
>>> egg_info for package pyttsx
>>> Installing collected packages: pyttsx
>>>    Running setup.py install for pyttsx
>>>        File "C:\Python34\Lib\site-packages\pyttsx\driver.py", line 105
>>>          except Exception, e
>>>                          ^
>>>      SyntaxError: invalid syntax

This is from setup.py

>>> [other syntax errors snipped]
>>> Successfully installed pyttsx

This is from pip, saying that it successfully downloaded and installed 
the files on your disk, which it did.

>> A bug it seems to me.

After reading the responses on the tracker and here, the bug is in the 
total systen of interaction of multiple parts. It is not a bug for the 
part covered by the tracker.

>>> Cleaning up...
>>> c:\Users\Mark\CrossCode>py -3.4
>>> Python 3.4.0rc2 (v3.4.0rc2:a300712ed38c, Feb 23 2014, 10:49:04) [MSC
>>> v.1600 32 bit (Intel)] on win32
>>> Type "help", "copyright", "credits" or "license" for more information.
>>>  >>> import pyttsx
>>> Traceback (most recent call last):
>>>    File "<stdin>", line 1, in <module>
>>>    File "C:\Python34\lib\site-packages\pyttsx\__init__.py", line 18, in
>>> <module>
>>>      from engine import Engine
>>> I've looked at pyttsx in my 3.3 site-packages and it appears that I've
>>> manually run 2to3.  Is this something that could be done automatically
>>> by pip?  Your thoughts please, ladies and gentlemen.
>> I should hope so.

> FTR I raised this as http://bugs.python.org/issue20846 and it was closed
> 11 minutes after I raised it.  I won't say anything else as I'm
> extremely tired and irritable and might well regret it later.

The issue brought to attention that the parts do not work together 
perfectly yet and stimulated some thought and some clarification on what 
needs to be done. I understand the irritation, but sleeping on it and 
letting it go is a good idea.

Terry Jan Reedy

More information about the Python-list mailing list