They are real objects, just in a different sense. The easiest way to figure
it out is too look at the dtml that comes in the LocalFS source. For example
to get a listing of LocalFS folder instead of:
objectIds() try fileItems()
--
Andy McKay, Developer.
ActiveState.
- Original Message
On Mon, 11 Dec 2000, Leichtman, David J wrote:
How do you access an individual object in a LocalFS? By that, I mean:
[...]
dtml-var "localfs_object.localfs_subobject.bobobase_modification_time",
you get the error NameError: localfs_subobject
dtml-var
Leichtman, David J writes:
However, if you try to do the same thing with a LocalFS object, i.e.
dtml-var "localfs_object.localfs_subobject.bobobase_modification_time",
you get the error NameError: localfs_subobject
This leads me to believe that LocalFS subobjects are not really objects.
At least the "Local File System" object does not expose
its children via "getattr" (which is required for the
usual "." operator to work) but only via "[...]".
This probably is a bug.
No this is by design, as explained in the how-to. Most operating systems allow
period (.) characters in
