Path: csiph.com!usenet.pasdenom.info!goblin2!goblin.stu.neva.ru!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Sender: Benjamin Schollnick <bschollnick@schollnick.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B5D2DAF0-115E-400C-B631-63085EE805AF"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Python Makefiles... are they possible?
From: Benjamin Schollnick <benjamin@schollnick.net>
In-Reply-To: <511b2a7c$0$11096$c3e8da3@news.astraweb.com>
Date: Wed, 13 Feb 2013 05:45:14 -0500
References: <e8d436e1-f226-4a81-968f-295c51198198@googlegroups.com> <mailman.1731.1360717275.2939.python-list@python.org> <roy-270198.20063512022013@news.panix.com> <511b2a7c$0$11096$c3e8da3@news.astraweb.com>
To: Steven D'Aprano <steve+comp.lang.python@pearwood.info>
Cc: python-list@python.org
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.1742.1360752320.2939.python-list@python.org>
Lines: 68
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:38815


--Apple-Mail=_B5D2DAF0-115E-400C-B631-63085EE805AF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

>> One thing we do in our Makefiles is "find . -name '*.pyc' | xargs =
rm".
>> It avoids all sorts of nasty and hard to track down bugs (consider =
what
>> happens if you move a .py file from one place in your source tree to
>> another and leave the old .pyc behind).
>=20
> How often do you move files around in the source tree? Meanwhile, =
*every*=20
> time you run make, you take a performance hit on every Python module =
in=20
> your project, whether it has moved or not.
>=20
> Seems to me like a fairly heavy-handed response for something quite =
rare,=20
> but I suppose that depends on how often you run make.

If the performance hit doesn't really matter. =20

Then simply walk the build tree, compare time date stamps, anything that =
doesn't match up in the make directory, gets deleted.  Anything that has =
different Date Created / Date Modified time from the build tree match, =
get's deleted.

This way, we are preserving any files that should be identical.  But =
there should be some mechanism documented to forcibly clear the build =
cache.

		- Benjamin


--Apple-Mail=_B5D2DAF0-115E-400C-B631-63085EE805AF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><blockquote type=3D"cite"><blockquote type=3D"cite">One thing we =
do in our Makefiles is "find . -name '*.pyc' | xargs rm".<br>It avoids =
all sorts of nasty and hard to track down bugs (consider what<br>happens =
if you move a .py file from one place in your source tree to<br>another =
and leave the old .pyc behind).<br></blockquote><br>How often do you =
move files around in the source tree? Meanwhile, *every* <br>time you =
run make, you take a performance hit on every Python module in <br>your =
project, whether it has moved or not.<br><br>Seems to me like a fairly =
heavy-handed response for something quite rare, <br>but I suppose that =
depends on how often you run make.<br></blockquote></div><br><div>If the =
performance hit doesn't really matter. =
&nbsp;</div><div><br></div><div>Then simply walk the build tree, compare =
time date stamps, anything that doesn't match up in the make directory, =
gets deleted. &nbsp;Anything that has different Date Created / Date =
Modified time from the build tree match, get's =
deleted.</div><div><br></div><div>This way, we are preserving any files =
that should be identical. &nbsp;But there should be some mechanism =
documented to forcibly clear the build =
cache.</div><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">		</span>- =
Benjamin</div><div><br></div></body></html>=

--Apple-Mail=_B5D2DAF0-115E-400C-B631-63085EE805AF--