Gilles Peskine c217f48251 Replace the output file atomically ...

When writing the new .data file, first write the new content, then replace
the target. This way, there isn't a temporary state in which the file is
partially written. This temporary state can be misleading if the build is
interrupted. It's annoying if you're watching changes to the output and the
changes appear as emptying the file following by the new version appearing.
Now interrupted builds don't leave a file that appears to be up to date but
isn't, and when watching the output, there's a single transition to the new
version.

Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>

2022-10-04 15:10:00 +02:00

..

asymmetric_key_data.py

Add key material for twisted Edwards curves

2021-03-29 15:08:10 +02:00

build_tree.py

fix build fail

2021-12-10 14:23:37 +08:00

c_build_helper.py

Tweak MSVC detection to work with non-English Visual Studio

2021-06-22 11:26:19 +02:00

crypto_knowledge.py

Add an EC J-PAKE KDF to transform K -> SHA256(K.X) for TLS 1.2

2022-09-14 08:39:26 -04:00

macro_collector.py

Fix invalid argument enumeration when there are >=3 arguments

2022-04-15 11:10:14 +02:00

psa_storage.py

Add warnings to test code and data about storage format stability

2022-06-20 19:10:35 +02:00

test_case.py

Replace the output file atomically

2022-10-04 15:10:00 +02:00

test_generation.py

Use a script specific description in CLI help

2022-09-16 17:03:54 +01:00

typing_util.py

Do not require typing_extensions at runtime

2021-02-17 14:58:29 +01:00