This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients db3l, ned.deily, pitrou, ronaldoussoren
Date 2011-03-13.23:00:23
SpamBayes Score 3.3163914e-07
Marked as misclassified No
Message-id <1300057220.3763.14.camel@localhost.localdomain>
In-reply-to <1300055554.12.0.72151606671.issue11487@psf.upfronthosting.co.za>
Content
> I suspect this may be an issue now because the old svn approach was a
> full checkout for each build, whereas the hg approach is to pull to
> the local clone, and then just update the build tree.  So in the svn
> case all the files would have a good shot at the same timestamp,
> whereas with the hg approach the generated files get stale if the
> contents don't change.
> 
> I wonder if just doing a full checkout from the local clone would be
> closer to the old svn behavior in general with respect to timestamps
> and maybe a reasonable policy?

Ok, I've made the change on the DMG builders.
History
Date User Action Args
2011-03-13 23:00:23pitrousetrecipients: + pitrou, db3l, ronaldoussoren, ned.deily
2011-03-13 23:00:23pitroulinkissue11487 messages
2011-03-13 23:00:23pitroucreate