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 arises at creation of the list of timers.
For a list of
On 5/5/06, Nick Coghlan [EMAIL PROTECTED] wrote:
Mike Orr wrote:
On 5/4/06, Paul Moore [EMAIL PROTECTED] wrote:
(But all the current proposals seem to build on os.path, so maybe I
should assume otherwise, that os.path will remain indefinitely...)
They build on os.path because that's
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
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 really work
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 of timers.
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 arises at creation
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 iterate over them via 'for
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 have not
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
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.
That
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 by some
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 with
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
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 used by
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 isn't any formal
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 users.
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'))
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:
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
[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 a bunch of those
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 talin at acm.org
Status: Draft
Type: Standards
21 matches
Mail list logo
