Python Makefiles... are they possible?

Roy Smith roy at
Thu Feb 14 04:02:33 CET 2013

In article <511c501d$0$6512$c3e8da3$5496439d at>,
 Steven D'Aprano <steve+comp.lang.python at> wrote:

> I prefer to keep the .pyc files, and only remove them when necessary, rather
> than to remove them whether it's necessary or not. It's not just because
> I'm an arrogant SOB who expects my team of developers to know at least more
> than me, therefore if I know enough to look for orphaned .pyc files so
> should they. It's because I am a big believer that your development system
> should be as close as possible to the eventual deployment system as is
> practical. Your app will (probably) use .pyc files when it is deployed, so
> you should do the same when developing.

Heh.  Our deployment system rolls out all the source code from scratch 
on every deploy.

> Meanwhile, *every* time you run make, you take a performance hit on
> every Python module in your project, whether it has moved or not.


More information about the Python-list mailing list