My strategy is to trade time-wise, and is there a more convenient way to get the current time of the retest than to extract the time of the retest from getrecords? I found that using the time function in the datetime library is still getting the current time, but not the time of the history.
Inventors quantify - small dreamsWhat's the Python strategy? You can get the current time with _D(). Or you can use time.time (t) to get time.
ooorrrgggReceived, thank you!
Inventors quantify - small dreamsThe problem is simple and straightforward to think about. There are no time-consuming operations in your main while loop, the program is instantly looped hundreds of times, so the time is the same. You add a sleep (1000) to the while loop. In addition, the K-line cycle has nothing to do with this, it is recommended that you first read the FMZ platform tutorial, the post related to the feedback mechanism.
ooorrrggg/upload/asset/1e27de6142d5b1693e939.png /upload/asset/1e232c167e5ca1f082613.png /upload/asset/1e2d19b09d3ede12e71d8.png This is a list of all the different ways Upload/asset is credited in the database. Dr. Dre, you look at my test code, time does show up as past time, but why not push forward as the function calls?