In article <511c501d$0$6512$c3e8da3$54964...@news.astraweb.com>, Steven D'Aprano <steve+comp.lang.pyt...@pearwood.info> 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. Yup. -- http://mail.python.org/mailman/listinfo/python-list
