[py-dev] Re: [py-svn] r6948 - in py/dist/py: . path/fspy path/pypath path/test test test/report test/report/text

[Laura Creighton]

In a message of Fri, 15 Oct 2004 11:54:56 +0200, holger krekel writes:

I appreciate that it is a path on a filesystem, but then I think that
all paths are on filesystems.  So that it is on a filesystem is not,
to my mind, the most interesting thing about this, ass opposed to
fsck(1) for instance, which really does want to operate on filesystems
qua filesystems.

Perhaps I am not making sense to you, or perhaps I am not understanding
something about pypath -- or perhaps both, of course.  Why is the 
filesystemness important enough to be worth mentioning?

Laura




>Hi Laura, 
>
>[Laura Creighton Fri, Oct 15, 2004 at 06:11:41AM +0200]
>> fspy looks like filesystem py to me.
>
>That's actually what it is, a filesystem+python path to 
>allow "addresses" of Python objects within a filesystem
>
>The name 'pypath' doesn't really hint at the filesystem-ness
>of this path implementations. 
>
>anyway, at the moment i am just happy i changed the
>implementation and semantics of this little thingie because it
>will play a critical role for further py.test development
>because it allows to simply address python objects across
>process barriers.  For running tests on multiple platforms and
>with multiple python versions having a way of unambigous
>talking about test methods is very important. 
>
>Note though, that for most purposes you don't need to know
>about the existence of py.path.fspy() although i do want to 
>export the object for the first major release's API. 
>
>cheers, 
>
>    holger