[ python-Bugs-1290382 ] --no-compile option has no effect

SourceForge.net noreply at sourceforge.net
Tue Sep 13 21:20:11 CEST 2005


Bugs item #1290382, was opened at 2005-09-13 15:03
Message generated for change (Comment added) made by tim_one
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1290382&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Distutils
>Group: Not a Bug
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Tim Peters (tim_one)
Assigned to: Nobody/Anonymous (nobody)
Summary: --no-compile option has no effect

Initial Comment:
ZODB ships with a .py file containing a syntax error 
(that's intentional, it's part of a test of the zope.testing 
component).  So, whenever somone does

setup.py install

they see a complaint about this file, like

byte-compiling /home/tim/glom/lib/python2.4/site-
packages/zope/testing/testrunner-
ex/sample2/sampletests_i.py to sampletests_i.pyc
  File "/home/tim/glom/lib/python2.4/site-
packages/zope/testing/testrunner-
ex/sample2/sampletests_i.py", line 15
    importx unittest
                   ^
SyntaxError: invalid syntax


That's fine.  The problem is that doing

setup.py install --no-compile

makes no difference -- it still tries to compile everything 
to .pyc.  True at least in Python 2.3.5 and 2.4.1.

----------------------------------------------------------------------

>Comment By: Tim Peters (tim_one)
Date: 2005-09-13 15:20

Message:
Logged In: YES 
user_id=31435

Closing this as invalid -- it appears to be unique to setup.py 
thingies created by Zope's zpkgtools.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1290382&group_id=5470


More information about the Python-bugs-list mailing list