I've updated PEP 3101 based on the feedback collected so far.
-
PEP: 3101
Title: Advanced String Formatting
Version: $Revision: 45928 $
Last-Modified: $Date: 2006-05-06 18:49:43 -0700 (Sat, 06 May 2006) $
Author: Talin
Status: Draft
Type: Standards
Content-Type: text/plain
Crea
[Josiah Carlson]
> ...
> >>> str < tuple < unicode
> True
>
> And you can actually compare str and unicode, so, if you have a str that
> is greater than the unicode, you run into this issue.
Oh dear -- I didn't realize we still had holes like that:
>>> 'b' < () < u'a' < 'b'
True
We used to have
Edward Loper wrote:
> If one of the path segments contained a path-splitting character,
> should it automatically get quoted?
No, an exception should be raised if you try to construct
a Path object containing such a name. No such object could
exist in the file system, so there's no point in bei
Hello all,
I just wanted to say thanks for your encouraging comments and
participation, and to say that I'm sorry that I haven't replied yet -
unfortunately, I don't have an Internet connection where I stay most
evenings. I now read all your replies, but I want to reply seriously
and the time is g
Apologies for the double post. Had my mail client misconfigured.
___
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.co
On Sat, May 06, 2006 at 12:11:59PM -0400, Edward Loper wrote:
> If one of the path segments contained a path-splitting character,
> should it automatically get quoted? (Is that even possible on all
> platforms?) E.g., what would the following give me on windows?
>
> str(Path('a', 'b\\c'))
On May 6, 2006, at 2:40 AM, Nick Coghlan wrote:
> Remember, the idea with portable path information is to *never*
> store os.sep
> and os.extsep anywhere in the internal data - those should only be
> added when
> needed to produce strings to pass to OS-specific functions or to
> display to us
On 5/6/06, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Greg Ewing wrote:
> > Nick Coghlan wrote:
> >
> >> So I suggest splitting the internal data into 'path elements separated
> >> by os.sep', 'name elements separated by os.extsep'
> >
> > What bothers me about that is that in many systems
> > there
Greg Ewing wrote:
> Nick Coghlan wrote:
>
>> So I suggest splitting the internal data into 'path elements separated
>> by os.sep', 'name elements separated by os.extsep'
>
> What bothers me about that is that in many systems
> there isn't any formal notion of an "extension",
> just a convention
I'm currently revising a proposal for the Google Summer of Code, and it
was suggested that I start a thread here to get input. Apologies for the
length, but I wanted this to more than just a link to my proposal.
The short version of my proposal is: The module would provide a
system by which the ma
Martin v. Löwis wrote:
> Benji York wrote:
>>Subversion 1.3 added a path-based authorization feature to svnserve.
>
> That's what I mean by "does not work fine": I would need to update
> to subversion 1.3.
I noted that in my original message. I thought you meant that it wasn't
possible at all w
Greg Ewing <[EMAIL PROTECTED]> wrote:
>> So I suggest splitting the internal data into 'path elements
>> separated by os.sep', 'name elements separated by os.extsep'
>
> What bothers me about that is that in many systems
> there isn't any formal notion of an "extension",
> just a convention used b
Mike Orr wrote:
> How do you do slicing and joining? If Path subclasses object, it
> could be done there like in the first example. But if Path subclasses
> string,
Er, hang on, I thought the idea was that it wouldn't
subclass either tuple *or* str, but would be a new
class all of its own.
Tha
Nick Coghlan wrote:
> So I suggest splitting the internal data into 'path elements separated
> by os.sep', 'name elements separated by os.extsep'
What bothers me about that is that in many systems
there isn't any formal notion of an "extension",
just a convention used by some applications.
Just
"Vladimir 'Yu' Stepanov" <[EMAIL PROTECTED]> wrote:
> Josiah Carlson wrote:
> > This problem has nothing to do with dictionaries and hashing, it has to
> > do with the fact that there may not be a total ordering on the elements
> > of a sequence.
>
> It is sad. I did not know it. Therefore and ha
"Vladimir 'Yu' Stepanov" <[EMAIL PROTECTED]> wrote:
>
> Martin v. Löwis wrote:
> > Vladimir 'Yu' Stepanov wrote:
> >
> >> Yes. I understood it when resulted a set example.
> >>
> >>> However, as I just said, people usually don't remove items from
> >>> just-sorted lists, they tend to iter
Martin v. Löwis wrote:
> Vladimir 'Yu' Stepanov wrote:
>
>> Yes. I understood it when resulted a set example.
>>
>>> However, as I just said, people usually don't remove items from
>>> just-sorted lists, they tend to iterate over them via 'for i in list:' .
>>>
>>>
>> Such problem
Josiah Carlson wrote:
> "Vladimir 'Yu' Stepanov" <[EMAIL PROTECTED]> wrote:
>> Josiah Carlson wrote:
>>> However, as I just said, people usually don't remove items from
>>> just-sorted lists, they tend to iterate over them via 'for i in list:' .
>>>
>> Such problem arises at creation of the list
"Martin v. Löwis" wrote:
> Tim Peters wrote:
>> Since I hope we see a lot more of these problems in the future, what
>> can be done to ease the pain? I don't know enough about SVN admin to
>> know what might be realistic. Adding a pile of "temporary
>> committers" comes to mind, but wouldn't re
Tim Peters wrote:
> Instead it would make best sense for each
> sprint project to work in its own branch, something SVN makes very
> easy, but only for those who _can_ commit.
There's no way of restricting commit privileges to
a particular branch?
--
Greg
_
Mike Orr wrote:
> There's something that bothers me about putting the path in an
> attribute rather than subclassing tuple.
[...]
> How do you do slicing and joining? If Path subclasses object, it
> could be done there like in the first example. But if Path subclasses
> string, that API is taken:
There's something that bothers me about putting the path in an
attribute rather than subclassing tuple. I prefer it that way but I
don't see how you'd do directory slicing and joining. If the path is
a tuple it's easy:
p = Path("/a/b/c")
p[:-1] # Path("/a/b")
If the directory components
Mike Orr wrote:
> I think you meant to say Perl in that sentence. In Python there
> should be one way to do it, and beautiful is better than ugly. The
> os.path functions are bad enough, but shutil.copy2 is just plain evil.
I agree a decent pathlib may make many of the low-level filesystem
mani
I'm currently revising a proposal for the Google Summer of Code, and it
was suggested that I start a thread here to get input. Apologies for the
length, but I wanted this to more than just a link to my proposal.
The short version of my proposal is: The module would provide a
system by which the at
24 matches
Mail list logo
