--no-compile option has no effect

[tim-one]

BPO	1290382
Nosy	@tim-one

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2005-09-13.19:20:11.000>
created_at = <Date 2005-09-13.19:03:49.000>
labels = ['invalid', 'library']
title = '--no-compile option has no effect'
updated_at = <Date 2005-09-13.19:20:11.000>
user = 'https://github.com/tim-one'

bugs.python.org fields:

activity = <Date 2005-09-13.19:20:11.000>
actor = 'tim.peters'
assignee = 'none'
closed = True
closed_date = None
closer = None
components = ['Distutils']
creation = <Date 2005-09-13.19:03:49.000>
creator = 'tim.peters'
dependencies = []
files = []
hgrepos = []
issue_num = 1290382
keywords = []
message_count = 2.0
messages = ['26275', '26276']
nosy_count = 1.0
nosy_names = ['tim.peters']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1290382'
versions = []

[tim-one]

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.

[tim-one]

Logged In: YES
user_id=31435

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