Django Q Documentation Release 0.5.3
Requirements Configuration name workers recycle timeout compress save_limit sync queue_limit label catch_up redis django_redis cpu_affinity Tasks Async Groups Synchronous testing Connection pooling Reference for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to0 码力 | 46 页 | 474.97 KB | 1 年前3Kotlin 1.9.10 官方文档 中文版
Kotlin 1.2 中会产生警告,而在 Kotlin 1.3中会放弃。 弃用:扩展 Throwable 的泛型类的内部类 继承自 Throwable 的泛型类的内部类可能会在 throw-catch 场景中违反类型安 全性,因此已弃用,在 Kotlin 1.2 中会是警告,而在 Kotlin 1.3中会是错误。 弃用:修改只读属性的幕后字段 通过在自定义 getter 中赋值 field 要启用这个行为,需要依赖项中有 kotlin-stdlib-jdk7 。 JVM 后端 构造函数调用规范化 自 1.0 版起,Kotlin 就已支持带有复杂控制流的表达式,诸如 try-catch 表达式 以及内联函数。根据 Java 虚拟机规范这样的代码是有效的。不幸的是, 当这 样的表达式出现在构造函数调用的参数中时,一些字节码处理工具不能很好地 处理这种代码 。 为了缓解这种 IllegalArgumentException("Invalid color param value") } } try-catch 表达式 fun test() { val result = try { count() } catch (e: ArithmeticException) { throw IllegalStateException(e)0 码力 | 3753 页 | 29.69 MB | 1 年前3Django Q Documentation Release 0.6.4
Requirements Configuration name workers recycle timeout retry compress save_limit sync queue_limit label catch_up redis django_redis disque_nodes disque_auth iron_mq sqs bulk cache cpu_affinity Brokers Redis for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to0 码力 | 53 页 | 512.86 KB | 1 年前3Django Q Documentation Release 0.7.9
Compatibility Configuration name workers recycle timeout retry compress save_limit sync queue_limit label catch_up redis django_redis disque_nodes disque_auth iron_mq sqs orm mongo mongo_db bulk cache cached scheduler for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to0 码力 | 62 页 | 514.67 KB | 1 年前3Django Q Documentation Release 0.7.10
Compatibility Configuration name workers recycle timeout retry compress save_limit sync queue_limit label catch_up redis django_redis disque_nodes disque_auth iron_mq sqs orm mongo mongo_db bulk cache cached scheduler for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to0 码力 | 67 页 | 518.39 KB | 1 年前3Django Q Documentation Release 0.7.11
Compatibility Configuration name workers recycle timeout retry compress save_limit sync queue_limit label catch_up redis django_redis disque_nodes disque_auth iron_mq sqs orm mongo mongo_db bulk cache cached scheduler for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to0 码力 | 72 页 | 526.88 KB | 1 年前3Django Q Documentation Release 0.7.14
Compatibility Configuration name workers recycle timeout retry compress save_limit sync queue_limit label catch_up redis django_redis disque_nodes disque_auth iron_mq sqs orm mongo mongo_db bulk cache cached scheduler for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to0 码力 | 73 页 | 527.40 KB | 1 年前3Django Q Documentation Release 0.7.12
Compatibility Configuration name workers recycle timeout retry compress save_limit sync queue_limit label catch_up redis django_redis disque_nodes disque_auth iron_mq sqs orm mongo mongo_db bulk cache cached scheduler for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to0 码力 | 73 页 | 527.33 KB | 1 年前3Django Q Documentation Release 0.7.18
Compatibility Configuration name workers recycle timeout retry compress save_limit sync queue_limit label catch_up redis django_redis disque_nodes disque_auth iron_mq sqs orm mongo mongo_db broker_class bulk poll for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to0 码力 | 73 页 | 516.84 KB | 1 年前3Django Q Documentation Release 0.7.15
Compatibility Configuration name workers recycle timeout retry compress save_limit sync queue_limit label catch_up redis django_redis disque_nodes disque_auth iron_mq sqs orm mongo mongo_db broker_class bulk poll for the Django Admin page. Defaults to 'Django Q' catch_up The default behavior for schedules that didn’t run while a cluster was down, is to play catch up and execute all the missed time slots until things things are back on schedule. You can override this behavior by setting catch_up to False. This will make those schedules run only once when the cluster starts and normal scheduling resumes. Defaults to0 码力 | 73 页 | 528.16 KB | 1 年前3
共 501 条
- 1
- 2
- 3
- 4
- 5
- 6
- 51