Eric Smith wrote:
My only concern with this is a possible performance issue with v6
networks. Would this be implemented such that [-1] doesn't need to
iterate through the (possibly large) address space of a v6 network?
I'm not familiar with v6, but if netmasks work the same
way as they do in
On Sep 18, 2009, at 8:58 PM, Antoine Pitrou wrote:
I'm not sure that's true. Various Unix/Linux man pages are readily
available on the Internet, but they regard specific implementations,
which often depart from the spec in one way or another. POSIX specs
themselves don't seem to be easily reachab
Le Sat, 19 Sep 2009 09:19:53 +0900, Stephen J. Turnbull a écrit :
> Antoine Pitrou writes:
> > James Y Knight fuhm.net> writes:
> > >
> > > Why are you just making things up? There is a *vast* amount of
> > > precedent for how file operations should work. Python should follow
> > > that prec
Antoine Pitrou writes:
> James Y Knight fuhm.net> writes:
> >
> > Why are you just making things up? There is a *vast* amount of
> > precedent for how file operations should work. Python should follow
> > that precedent and do like POSIX unless there's a compelling reason
> > not to.
James Y Knight fuhm.net> writes:
>
> Why are you just making things up? There is a *vast* amount of
> precedent for how file operations should work. Python should follow
> that precedent and do like POSIX unless there's a compelling reason
> not to.
Actually, Python is cross-platform and t
Le Fri, 18 Sep 2009 21:17:29 +0200, Pascal Chambon a écrit :
Hello,
First, thanks for experimenting with this.
(as a sidenote, we lack real-world testing of non-blocking features,
perhaps you want to take a look)
> I'm currently working on a reimplementation of io.FileIO, which would
> allow
James Y Knight wrote:
On Sep 18, 2009, at 3:55 PM, MRAB wrote:
I think that this should be an invariant:
0 <= file pointer <= file size
so the file pointer might sometimes have to be moved.
As for the question of whether 'truncate' should be able to lengthen a
file, the method name sug
On Fri, Sep 18, 2009 at 2:17 PM, Pascal Chambon wrote:
> - it is unclear what truncate() methods do with the file pointer, and even
> if the current implementation simply moves it to the truncation point, it's
> very contrary to the standard way of doing under unix, where the file
> pointer is nor
On Sep 18, 2009, at 3:55 PM, MRAB wrote:
I think that this should be an invariant:
0 <= file pointer <= file size
so the file pointer might sometimes have to be moved.
As for the question of whether 'truncate' should be able to lengthen a
file, the method name suggests no; if the method
Pascal Chambon wrote:
Hello everyone
I'm currently working on a reimplementation of io.FileIO, which would
allow cross-platform file range locking and all kinds of other safety
features ; however I'm slightly stuck due to some specification
fuzziness in the IO docs.
CF http://bugs.python
[Oops! Hit Send to soon]
Pascal Chambon wrote:
Hello everyone
I'm currently working on a reimplementation of io.FileIO, which would
allow cross-platform file range locking and all kinds of other safety
features ; however I'm slightly stuck due to some specification
fuzziness in the IO docs.
Why not propose an update to the existing PEP to clarify the vaguenesses?
On Fri, Sep 18, 2009 at 12:17 PM, Pascal Chambon
wrote:
> Hello everyone
>
> I'm currently working on a reimplementation of io.FileIO, which would allow
> cross-platform file range locking and all kinds of other safety feat
Hello everyone
I'm currently working on a reimplementation of io.FileIO, which would
allow cross-platform file range locking and all kinds of other safety
features ; however I'm slightly stuck due to some specification
fuzziness in the IO docs.
CF http://bugs.python.org/issue6939
The mai
I have updated the OS X buildbot to Snow Leopard.
--
Thomas
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
ACTIVITY SUMMARY (09/11/09 - 09/18/09)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
2396 open (+27) / 16366 closed (+29) / 18762 total (+56)
Open issues with patches: 953
Average
On Thu, 17 Sep 2009 at 20:29, Peter Moody wrote:
On Thu, Sep 17, 2009 at 6:17 PM, Andrew McNamara
wrote:
off to patch the pep and implement some of the non controversial changes.
It might be a good idea to add some use-cases to the PEP.
There are several use-cases in the PEP already.
The p
2009/9/18 R. David Murray :
> On Fri, 18 Sep 2009 at 11:04, Andrew McNamara wrote:
>>
>> [attribution lost; apparently Steven D'Aprano given the CC]
>>>
>>> To a non-specialist, "the network address" is ambiguous. There are many
>>> addresses in a network, and none of them are the entire network. I
Fred Drake wrote:
> On Thu, Sep 17, 2009 at 10:38, Georg Brandl wrote:
>> So the plan would be to consolidate these into another set of rst docs,
>> having them in the repo, editable by every committer, as well as
>> published
>> somewhere on python.org (devdocs.python.org or somesuch).
>
> On Se
18 matches
Mail list logo
