Message 310012 - Python tracker

Message310012

Author	barry
Recipients	Alexandru Ardelean, Ray Donnelly, barry, benjamin.peterson, bmwiedemann, brett.cannon, dstufft, eric.araujo, eric.smith, eschwartz, vstinner, yan12125
Date	2018-01-15.19:41:19
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<2D0AB752-CCD9-4AC1-8F48-E2DC3EB81DB8@python.org>
In-reply-to	<1516044695.9.0.467229070634.issue29708@psf.upfronthosting.co.za>

Content
On Jan 15, 2018, at 11:31, Brett Cannon <report@bugs.python.org> wrote: > > 1. SOURCE_DATE_EPOCH acts as an environment variable flag to forcibly generate hash-based .pyc files with the check_source bit set in py_compile and compileall > 2. SOURCE_DATE_EPOCH is used to specifically set the timestamp in .pyc files in py_compile and compileall I’d suggest that if SDE is set to an integer, that is used as the timestamp. If it’s set to a special symbol (e.g. ‘hash’) then the hash is used. I’m not volunteering to write the code though. :)

Content

On Jan 15, 2018, at 11:31, Brett Cannon <report@bugs.python.org> wrote:
> 
> 1. SOURCE_DATE_EPOCH acts as an environment variable flag to forcibly generate hash-based .pyc files with the check_source bit set in py_compile and compileall
> 2. SOURCE_DATE_EPOCH is used to specifically set the timestamp in .pyc files in py_compile and compileall

I’d suggest that if SDE is set to an integer, that is used as the timestamp.  If it’s set to a special symbol (e.g. ‘hash’) then the hash is used.  I’m not volunteering to write the code though. :)

History
Date	User	Action	Args
2018-01-15 19:41:19	barry	set	recipients: + barry, brett.cannon, vstinner, eric.smith, benjamin.peterson, eric.araujo, dstufft, yan12125, bmwiedemann, Alexandru Ardelean, Ray Donnelly, eschwartz
2018-01-15 19:41:19	barry	link	issue29708 messages
2018-01-15 19:41:19	barry	create