Open mstreatfield opened 3 years ago
Oops, that has been fixed in #121 (commit 99c7de7), but not yet released. Could you directly pull current master branch and have a test ?
Okay, I just made a release 1.3.67
, wait a few minutes and you could pip install -U allzpark
!
The PEP-418 suggests using time.perf_counter might be preferable.
Hmmm, the replacment I used was process_time
, looks like using perf_counter
is better indeed.
I pip installed the latest version and it's working perfectly now. Thank you for the quick turnaround, I appreciate it!
My read of the documentation is that perf_counter
will be more accurate for time deltas, although perhaps this isn't needed if what is being measured is application/module load time.
Thanks for confirm !
Regarding perf_counter
, yeah I agree. Didn't think much at the time being, was trying to get pass CI testing and thought it doesn't matter much for our use case.
Anyway, PR is welcome ! (not limited to this issue of course :P)
Hello,
After following the quickstart for bleeding-rez and quickstart for allzpark, I get the following error on OSX when trying to launch
allzpark
for the first time.Python has been installed using brew to replace the system python:
And I'm using the latest version of bleeding-rez:
It looks like
time.clock
was deprecated around Python 3.3 and then removed in 3.8 due to platform-dependent behaviour. Updating to usingtime.time
instead is enough to move past the error and have allzpark start as expected. The PEP-418 suggests usingtime.perf_counter
might be preferable.Sounds like it might be simple to resolve - unfortunately, I'm not able to make a pull request for a fix at the moment.
Mark.