Aahz pythoncraft.com> writes:
>
> On Fri, Mar 13, 2009, Antoine Pitrou wrote:
> > R. David Murray bitdance.com> writes:
> >>
> >> You will note that what
> >> I suggested was that applications that _use the sync feature_ make
> >> it user controllable.
> >
> > I'm sorry, but if it has nothing
On Fri, Mar 13, 2009, Antoine Pitrou wrote:
> R. David Murray bitdance.com> writes:
>>
>> You will note that what
>> I suggested was that applications that _use the sync feature_ make
>> it user controllable.
>
> I'm sorry, but if it has nothing to do with Python itself, perhaps we
> could stop
On Fri, 13 Mar 2009 at 12:27, Antoine Pitrou wrote:
R. David Murray bitdance.com> writes:
You will note that what
I suggested was that applications that _use the sync feature_ make
it user controllable.
I'm sorry, but if it has nothing to do with Python itself, perhaps we could stop
this sub
R. David Murray bitdance.com> writes:
>
> You will note that what
> I suggested was that applications that _use the sync feature_ make
> it user controllable.
I'm sorry, but if it has nothing to do with Python itself, perhaps we could stop
this subthread (or move it to another ML)? There are eno
On Fri, 13 Mar 2009 at 14:27, Steven D'Aprano wrote:
On Fri, 13 Mar 2009 01:02:26 pm R. David Murray wrote:
On Fri, 13 Mar 2009 at 00:35, Antoine Pitrou wrote:
R. David Murray bitdance.com> writes:
Seriously, though, the point is that IMO an application should not
be calling fsync unless it p
Steven D'Aprano wrote:
On Fri, 13 Mar 2009 01:02:26 pm R. David Murray wrote:
On Fri, 13 Mar 2009 at 00:35, Antoine Pitrou wrote:
R. David Murray bitdance.com> writes:
Seriously, though, the point is that IMO an application should not
be calling fsync unless it provides a way for that behavio
On Fri, 13 Mar 2009 01:02:26 pm R. David Murray wrote:
> On Fri, 13 Mar 2009 at 00:35, Antoine Pitrou wrote:
> > R. David Murray bitdance.com> writes:
> >> Seriously, though, the point is that IMO an application should not
> >> be calling fsync unless it provides a way for that behavior to be
> >>
On Fri, 13 Mar 2009 at 00:35, Antoine Pitrou wrote:
R. David Murray bitdance.com> writes:
Seriously, though, the point is that IMO an application should not be
calling fsync unless it provides a way for that behavior to be controlled
by the user.
But whether an application does it or not is
On 13Mar2009 00:35, Antoine Pitrou wrote:
| R. David Murray bitdance.com> writes:
| > Seriously, though, the point is that IMO an application should not be
| > calling fsync unless it provides a way for that behavior to be controlled
| > by the user.
|
| But whether an application does it or not
R. David Murray bitdance.com> writes:
>
> Seriously, though, the point is that IMO an application should not be
> calling fsync unless it provides a way for that behavior to be controlled
> by the user.
But whether an application does it or not is none of Python's business, is it?
What is the di
On Thu, 12 Mar 2009 at 22:57, "Martin v. L?wis" wrote:
Cameron Simpson wrote:
On 12Mar2009 22:09, Martin v. L?wis wrote:
| > Let me try some examples.
| > Suppose I'm running my applications on a laptop and I don't want the
| > disk to be spinning continually while I work. I'm willing to take
Cameron Simpson wrote:
> On 12Mar2009 22:09, Martin v. L?wis wrote:
> | > Let me try some examples.
> | > Suppose I'm running my applications on a laptop and I don't want the
> | > disk to be spinning continually while I work. I'm willing to take the
> | > risk of data loss in order to extend my
On 12Mar2009 22:09, Martin v. L?wis wrote:
| > Let me try some examples.
| > Suppose I'm running my applications on a laptop and I don't want the
| > disk to be spinning continually while I work. I'm willing to take the
| > risk of data loss in order to extend my battery life.
|
| So when you se
13 matches
Mail list logo
