Windows vs. LINUX about audfprint HOT 5 OPEN

audfprint.py
DECIDED to use '--list' mode in which case windows file paths are supported.

from audfprint.

audfprint_match.py
***** TMP\AUDFPRINT-MASTER\AUDFPRINT-MASTER\audfprint_match.py
13: # for checking phys mem size
14: import resource
15: # for localtest and illustrate
***** LIB\AUDFPRINT\AUDFPRINT_MATCH.PY
13: # for checking phys mem size
14: #import resource
15: # for localtest and illustrate

***** TMP\AUDFPRINT-MASTER\AUDFPRINT-MASTER\audfprint_match.py
22: """ log info with stats """
23: print time.ctime(),
24: "physmem=", resource.getrusage(resource.RUSAGE_SELF).ru_maxrss,
25: "utime=", resource.getrusage(resource.RUSAGE_SELF).ru_utime,
26: message
27:
***** LIB\AUDFPRINT\AUDFPRINT_MATCH.PY
22: """ log info with stats """
23: print time.ctime(), message
24: #print time.ctime(),
25: # "physmem=", resource.getrusage(resource.RUSAGE_SELF).ru_maxrss,
26: # "utime=", resource.getrusage(resource.RUSAGE_SELF).ru_utime,
27: # message
28

from audfprint.

I actually do most development on MacOS, but that is much closer to Linux than Windows. I intend it to work unchanged on Linux, but I don't have access to a Windows machine. If there were simple way to support Windows without much noise, I'd be happy to accept a pull request.

from audfprint.

Understand. Since there are only a few changes and they are captured in this issue note, at the moment it is probably more valuable to spend your energy other topics. If I had the time, a PR that would support Windows and LINUX would be the way to go.

from audfprint.

#33

from audfprint.