1.6.0 #10

2018-11-27 · 2024-10-08T02:27:13Z

The scheme of reconstructing the return value of the cache function, uses the secondary lock. Solve the lock contention problem when the function is called concurrently with different parameters.
The return value of the method in the cache class supports setting the expiration time.
Add a decorator named count, supports caching the return value of a function by number of calls.
The decorator with cache expiration expires is renamed to ttl.
The cache expiration time parameter can be passed in unit-time (such as "1h40m").
Fix issue: When an exception occurs in the call to the cached object, subsequent successive calls always raise KeyError: '__return__'. 当被缓存的对象调用出现异常后，后续的连续调用始终引发 KeyError: '__return__' #2
Fix issue: Concurrent calls when the return value of the function has not been cached or has expired may repeat the execution of the function. 当函数返回值还未被缓存或已过期时的并发调用可能重复执行函数 #4
The __getattribute__ method is no longer silently overridden, and an exception is thrown directly if it exists.
Internal code adds type annotations, as well as a lot of optimization and refactoring.
Refactor the internal method Time2Second to make it more concise and efficient.
Use time.monotonic() to replace time.time() for cache expiration checks.
Fix the potential errors that may occur in the class cache when running in performance mode.

重构缓存函数返回值的方案，现采用二级锁。解决以不同参数并发调用函数时的锁竞争问题。
缓存类中方法的返回值支持设置过期时间。
新增装饰器 count，支持按调用次数缓存函数的返回值。
带缓存有效期的装饰器 expires 更名为 ttl。
缓存过期时间的参数支持按单位时间（如 "1h40m"）的方式传入。
修复问题：当被缓存的对象调用出现异常后，后续的连续调用始终引发 KeyError: '__return__'。当被缓存的对象调用出现异常后，后续的连续调用始终引发 KeyError: '__return__' #2
修复问题：当函数返回值还未被缓存或已过期时的并发调用可能重复执行函数。当函数返回值还未被缓存或已过期时的并发调用可能重复执行函数 #4
不再静默覆盖 __getattribute__ 方法，如果它存在，将直接抛出异常。
内部代码添加类型注解，以及大量优化和重构。
重构内部方法 Time2Second 使之更简洁和高效。
使用 time.monotonic() 替换 time.time() 进行缓存过期检查。
修复在性能模式下运行时类缓存器可能发生的错误。

1.The scheme of reconstructing the return value of the cache function, uses the secondary lock. Solve the lock contention problem when the function is called concurrently with different parameters. 2.The return value of the method in the cache class supports setting the expiration time. 3.Add a decorator named `count`, supports caching the return value of a function by number of calls. 4.The decorator with cache expiration `expires` is renamed to `ttl`. 5.The cache expiration time parameter can be passed in unit-time (such as "1h40m"). 6.Fix issue: When an exception occurs in the call to the cached object, subsequent successive calls always raise `KeyError: '__return__'`. gqylpy#2 7.Fix issue: Concurrent calls when the return value of the function has not been cached or has expired may repeat the execution of the function. gqylpy#4 8.The `__getattribute__` method is no longer silently overridden, and an exception is thrown directly if it exists. 9.Internal code adds type annotations, as well as a lot of optimization and refactoring. 10.Refactor the internal method `Time2Second` to make it more concise and efficient. 11.Use `time.monotonic()` to replace `time.time()` for cache expiration checks. 12.Fix the potential errors that may occur in the class cache when running in performance mode. 1.重构缓存函数返回值的方案，现采用二级锁。解决以不同参数并发调用函数时的锁竞争问题。 2.缓存类中方法的返回值支持设置过期时间。 3.新增装饰器 `count`，支持按调用次数缓存函数的返回值。 4.带缓存有效期的装饰器 `expires` 更名为 `ttl`。 5.缓存过期时间的参数支持按单位时间（如 "1h40m"）的方式传入。 6.修复问题：当被缓存的对象调用出现异常后，后续的连续调用始终引发 `KeyError: '__return__'`。gqylpy#2 7.修复问题：当函数返回值还未被缓存或已过期时的并发调用可能重复执行函数。gqylpy#4 8.不再静默覆盖 `__getattribute__` 方法，如果它存在，将直接抛出异常。 9.内部代码添加类型注解，以及大量优化和重构。 10.重构内部方法 `Time2Second` 使之更简洁和高效。 11.使用 `time.monotonic()` 替换 `time.time()` 进行缓存过期检查。 12.修复在性能模式下运行时类缓存器可能发生的错误。

2018-11-27 self-assigned this Oct 8, 2024

2018-11-27 merged commit 41e5a1f into gqylpy:v1.0 Oct 8, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

1.6.0 #10

1.6.0 #10

Uh oh!

Uh oh!

Uh oh!

1.6.0 #10

1.6.0 #10

Uh oh!

Conversation

Uh oh!

Uh oh!