On Thu, 2012-05-17 at 11:13 +1000, Chris Angelico wrote:
> On Thu, May 17, 2012 at 9:01 AM, Ethan Furman wrote:
> > A record is an interesting critter -- it is given life either from the user
> > or from the disk-bound data; its fields can then change, but those changes
> > are not reflected on
Chris Angelico wrote:
On Thu, May 17, 2012 at 9:01 AM, Ethan Furman wrote:
A record is an interesting critter -- it is given life either from the user
or from the disk-bound data; its fields can then change, but those changes
are not reflected on disk until .write_record() is called; I do thi
On 17 May 2012 11:13, Chris Angelico wrote:
> On Thu, May 17, 2012 at 9:01 AM, Ethan Furman wrote:
> > A record is an interesting critter -- it is given life either from the
> user
> > or from the disk-bound data; its fields can then change, but those
> changes
> > are not reflected on disk unt
On Thu, May 17, 2012 at 9:01 AM, Ethan Furman wrote:
> A record is an interesting critter -- it is given life either from the user
> or from the disk-bound data; its fields can then change, but those changes
> are not reflected on disk until .write_record() is called; I do this
> because I am fr
Tim Delaney wrote:
On 17 May 2012 07:33, Ethan Furman wrote:
Just hit a snag:
In cPython the deterministic garbage collection allows me a
particular optimization when retrieving records from a dbf file --
namely, by using weakrefs I can tell if the record is still in
memory and active, and if s
Ian Kelly wrote:
On Wed, May 16, 2012 at 3:33 PM, Ethan Furman wrote:
Just hit a snag:
In cPython the deterministic garbage collection allows me a particular
optimization when retrieving records from a dbf file -- namely, by using
weakrefs I can tell if the record is still in memory and active
On 17 May 2012 07:33, Ethan Furman wrote:
> Just hit a snag:
>
> In cPython the deterministic garbage collection allows me a particular
> optimization when retrieving records from a dbf file -- namely, by using
> weakrefs I can tell if the record is still in memory and active, and if so
> not hit
On Wed, May 16, 2012 at 3:33 PM, Ethan Furman wrote:
> Just hit a snag:
>
> In cPython the deterministic garbage collection allows me a particular
> optimization when retrieving records from a dbf file -- namely, by using
> weakrefs I can tell if the record is still in memory and active, and if so
