Mike Orr wrote:
> I'm looking for "we need a method named foo with signature bar that
> does this..." Or "make sure method blah doesn't do this"
> Otherwise I don't know what to do with the information. Can you make
> a use case showing how you'd ideally like to interact with the module
>
On 11/9/06, Talin <[EMAIL PROTECTED]> wrote:
> Mike Orr wrote:
> > On 11/9/06, Talin <[EMAIL PROTECTED]> wrote:
> >> (This is a good reason to have paths represented as strings instead of
> >> as a tuple, since you can't defer interpretation this way with
> >> pre-parsed paths.)
> >
> > Er, is ther
Mike Orr wrote:
> On 11/9/06, Talin <[EMAIL PROTECTED]> wrote:
>> Bill Janssen wrote:
>>> Greg Ewing writes:
If the standard format were designed so as to be
unambiguously distinguishable from all native
formats, ...
>>> All native formats both past and future.
>> That's not difficul
On 11/9/06, Greg Ewing <[EMAIL PROTECTED]> wrote:
> Talin wrote:
> > I use 'posix' paths as my universal format.
>
> That assumes you can always distinguish a posix path from
> some other kind of path. That's not always the case,
> e.g. consider
>
>/hello:wide/world
>
> Is that a posix path or
Talin wrote:
> Bill Janssen wrote:
>
> > All native formats both past and future.
>
> That's not difficult.
>
> I use 'posix' paths as my universal format.
That assumes you can always distinguish a posix path from
some other kind of path. That's not always the case,
e.g. consider
/hello:wid
On 11/9/06, Mike Orr <[EMAIL PROTECTED]> wrote:
> the destination format will at least recognize it as an even if it
> doesn't know what it means.
... recognize it as an absolute path ...
--
Mike Orr <[EMAIL PROTECTED]>
___
Python-3000 mailing list
Py
On 11/9/06, Talin <[EMAIL PROTECTED]> wrote:
> Bill Janssen wrote:
> > Greg Ewing writes:
> >> If the standard format were designed so as to be
> >> unambiguously distinguishable from all native
> >> formats, ...
> >
> > All native formats both past and future.
>
> That's not difficult.
>
> I use '
Ka-Ping,
Thanks for all of your hard work on this. Well done!
Mike
___
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mai
Le jeudi 09 novembre 2006 à 20:45 +, Paul Moore a écrit :
> Again, I don't believe this is possible for all corner cases: what is
> the drive for /my/file on a Windows system?
Why not the current drive?
> If you mandate that all filenames must be relative, you could manage,
> but enforcing t
On 11/9/06, Talin <[EMAIL PROTECTED]> wrote:
> Bill Janssen wrote:
> > Greg Ewing writes:
> >> If the standard format were designed so as to be
> >> unambiguously distinguishable from all native
> >> formats, ...
> >
> > All native formats both past and future.
>
> That's not difficult.
>
> I use '
I've committed PEP 3104 to the SVN repository. It should appear at
http://www.python.org/dev/peps/pep-3104/
shortly. The PEP is updated to add a note on the amount of code
breakage in the standard library that we might expect for some of
the possible keywords we might choose. The updated v
Bill Janssen wrote:
> Greg Ewing writes:
>> If the standard format were designed so as to be
>> unambiguously distinguishable from all native
>> formats, ...
>
> All native formats both past and future.
That's not difficult.
I use 'posix' paths as my universal format. I convert them to native
pa
12 matches
Mail list logo
