Re: sconsign database discussion

--===============0160664132861963771==
Content-Type: multipart/alternative; boundary="00000000000024c98905bbfddb65"

--00000000000024c98905bbfddb65
Content-Type: text/plain; charset="UTF-8"

> There's been some discussion of making sconsign be a "real" database,
> not least because the "dump the entire dictionary (pickling as we go) to
> database on exit" behavior is pretty irritating - quite a slow operation
> if you didn't do any work.

Can we start with some digits? Otherwise how do we know that the new
way is actually solving the problem.

--00000000000024c98905bbfddb65
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">&gt; There&#39;s been some discussion of making sconsign b=
e a &quot;real&quot; database, <br>&gt; not least because the &quot;dump th=
e entire dictionary (pickling as we go) to <br>&gt; database on exit&quot; =
behavior is pretty irritating - quite a slow operation <br><div>&gt; if you=
 didn&#39;t do any work.</div><div><br></div><div>Can we start with some di=
gits? Otherwise how do we know that the new</div><div>way is actually solvi=
ng the problem.<br></div></div>

--00000000000024c98905bbfddb65--

--===============0160664132861963771==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Scons-dev mailing list
[email protected]
https://pairlist2.pair.net/mailman/listinfo/scons-dev

--===============0160664132861963771==--