I have tried os.walk in the past and couldn't get it to work reliably,
with hindsight may be due to the same issue
On 17/04/13 21:17, Ziggy wrote:
Mick, are you using os.walk() ? I haven't tried it myself but I
wouldn't be surprised if the bus.0 recursion gave it fits. The
following Python sh
Mick, are you using os.walk() ? I haven't tried it myself but I wouldn't
be surprised if the bus.0 recursion gave it fits. The following Python
should work to circumvent the issue:
|forroot,subFolders,files inos.walk(1wdir):
if'bus.0'insubFolders:
subFolders.remove('bus.0')|
I've use o
Hi Paul,
Thanks for the reply. The reason for all this is I am trying to use my
new Sheepwalk RPI3 adapter, the example I gave was with a USB as that
looked simpler. The RPI3 uses bus.0 to bus.7 for the channels.
Look forward to the next release, if there is anything I can do to help
testi
This looks like a bug. Thanks your for finding it. The level of descending
bus.x directories is specific to your network topology.
In general, however, there is no reason to go into the bus.x directories.
All the information should be present in the root directory. The only
additional information
I am having trouble understanding the file structure, it is not behaving
as I expected.
My structure looks like this in Nautilus -
/var/1-wire/mnt
81.8C7E3000
alarm
bus.0
81.8C7E3000
alarm
bus.0
10.0D54A9010800
81.8C7E30
