 Celery v5.0.1 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID) – this is the task id. The delay and apply_async methods return an AsyncResult instance, which can @app.task def error_handler(uuid): result = AsyncResult(uuid) exc = result.get(propagate=False) print('Task {0} raised exception: {1!r}\n{2!r}'.format( uuid, exc, result.traceback)) it format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an0 码力 | 2313 页 | 2.13 MB | 1 年前3 Celery v5.0.1 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID) – this is the task id. The delay and apply_async methods return an AsyncResult instance, which can @app.task def error_handler(uuid): result = AsyncResult(uuid) exc = result.get(propagate=False) print('Task {0} raised exception: {1!r}\n{2!r}'.format( uuid, exc, result.traceback)) it format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an0 码力 | 2313 页 | 2.13 MB | 1 年前3
 Celery v5.0.2 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID) – this is the task id. The delay and apply_async methods return an AsyncResult instance, which can @app.task def error_handler(uuid): result = AsyncResult(uuid) exc = result.get(propagate=False) print('Task {0} raised exception: {1!r}\n{2!r}'.format( uuid, exc, result.traceback)) it format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an0 码力 | 2313 页 | 2.14 MB | 1 年前3 Celery v5.0.2 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID) – this is the task id. The delay and apply_async methods return an AsyncResult instance, which can @app.task def error_handler(uuid): result = AsyncResult(uuid) exc = result.get(propagate=False) print('Task {0} raised exception: {1!r}\n{2!r}'.format( uuid, exc, result.traceback)) it format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an0 码力 | 2313 页 | 2.14 MB | 1 年前3
 Celery v5.0.0 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID) – this is the task id. The delay and apply_async methods return an AsyncResult instance, which can @app.task def error_handler(uuid): result = AsyncResult(uuid) exc = result.get(propagate=False) print('Task {0} raised exception: {1!r}\n{2!r}'.format( uuid, exc, result.traceback)) it format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an0 码力 | 2309 页 | 2.13 MB | 1 年前3 Celery v5.0.0 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID) – this is the task id. The delay and apply_async methods return an AsyncResult instance, which can @app.task def error_handler(uuid): result = AsyncResult(uuid) exc = result.get(propagate=False) print('Task {0} raised exception: {1!r}\n{2!r}'.format( uuid, exc, result.traceback)) it format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an0 码力 | 2309 页 | 2.13 MB | 1 年前3
 Celery v5.0.5 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID) – this is the task id. The delay and apply_async methods return an AsyncResult instance, which can format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an track of this for us. task = state.tasks.get(event['uuid']) print('TASK FAILED: %s[%s] %s' % ( task.name, task.uuid, task.info(),)) with app.connection() as connection:0 码力 | 2315 页 | 2.14 MB | 1 年前3 Celery v5.0.5 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID) – this is the task id. The delay and apply_async methods return an AsyncResult instance, which can format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an track of this for us. task = state.tasks.get(event['uuid']) print('TASK FAILED: %s[%s] %s' % ( task.name, task.uuid, task.info(),)) with app.connection() as connection:0 码力 | 2315 页 | 2.14 MB | 1 年前3
 Celery 3.0 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID), this is the task id. The delay and apply_async methods return an AsyncResult instance, that can @app.task def error_handler(uuid): result = AsyncResult(uuid) exc = result.get(propagate=False) print('Task {0} raised exception: {1!r}\n{2!r}'.format( uuid, exc, result.traceback)) it format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an0 码力 | 2110 页 | 2.23 MB | 1 年前3 Celery 3.0 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID), this is the task id. The delay and apply_async methods return an AsyncResult instance, that can @app.task def error_handler(uuid): result = AsyncResult(uuid) exc = result.get(propagate=False) print('Task {0} raised exception: {1!r}\n{2!r}'.format( uuid, exc, result.traceback)) it format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an0 码力 | 2110 页 | 2.23 MB | 1 年前3
 Celery v4.0.0 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID), this is the task id. The delay and apply_async methods return an AsyncResult instance, that can @app.task def error_handler(uuid): result = AsyncResult(uuid) exc = result.get(propagate=False) print('Task {0} raised exception: {1!r}\n{2!r}'.format( uuid, exc, result.traceback)) it format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an0 码力 | 2106 页 | 2.23 MB | 1 年前3 Celery v4.0.0 Documentationcan be found in the Calling User Guide. Every task invocation will be given a unique identifier (an UUID), this is the task id. The delay and apply_async methods return an AsyncResult instance, that can @app.task def error_handler(uuid): result = AsyncResult(uuid) exc = result.get(propagate=False) print('Task {0} raised exception: {1!r}\n{2!r}'.format( uuid, exc, result.traceback)) it format used to serialize the message. The body contains the name of the task to execute, the task id (UUID), the arguments to apply it with and some additional meta-data – like the number of retries or an0 码力 | 2106 页 | 2.23 MB | 1 年前3
 peewee Documentation
Release 3.5.0BlobField blob bytea blob BitField integer bigint bigint BigBitField blob bytea blob UUIDField text uuid varchar(40) BinaryUUIDField blob bytea varbinary(16) DateTimeField datetime timestamp datetime support for custom field types in peewee. In this example we will create a UUID field for postgresql (which has a native UUID column type). To add a custom field type you need to first identify what type only as an example. Let’s start by defining our UUID field: class UUIDField(Field): field_type = 'uuid' We will store the UUIDs in a native UUID column. Since psycopg2 treats the data as a string0 码力 | 347 页 | 380.80 KB | 1 年前3 peewee Documentation
Release 3.5.0BlobField blob bytea blob BitField integer bigint bigint BigBitField blob bytea blob UUIDField text uuid varchar(40) BinaryUUIDField blob bytea varbinary(16) DateTimeField datetime timestamp datetime support for custom field types in peewee. In this example we will create a UUID field for postgresql (which has a native UUID column type). To add a custom field type you need to first identify what type only as an example. Let’s start by defining our UUID field: class UUIDField(Field): field_type = 'uuid' We will store the UUIDs in a native UUID column. Since psycopg2 treats the data as a string0 码力 | 347 页 | 380.80 KB | 1 年前3
 peewee Documentation Release 3.4.0BlobField blob bytea blob BitField integer bigint bigint BigBitField blob bytea blob UUIDField text uuid varchar(40) BinaryUUIDField blob bytea varbinary(16) DateTimeField datetime timestamp datetime support for custom field types in peewee. In this example we will create a UUID field for postgresql (which has a native UUID column type). To add a custom field type you need to first identify what type only as an example. Let’s start by defining our UUID field: class UUIDField(Field): field_type = 'uuid' We will store the UUIDs in a native UUID column. Since psycopg2 treats the data as a string0 码力 | 349 页 | 382.34 KB | 1 年前3 peewee Documentation Release 3.4.0BlobField blob bytea blob BitField integer bigint bigint BigBitField blob bytea blob UUIDField text uuid varchar(40) BinaryUUIDField blob bytea varbinary(16) DateTimeField datetime timestamp datetime support for custom field types in peewee. In this example we will create a UUID field for postgresql (which has a native UUID column type). To add a custom field type you need to first identify what type only as an example. Let’s start by defining our UUID field: class UUIDField(Field): field_type = 'uuid' We will store the UUIDs in a native UUID column. Since psycopg2 treats the data as a string0 码力 | 349 页 | 382.34 KB | 1 年前3
 peewee Documentation
Release 3.5.0BlobField blob bytea blob BitField integer bigint bigint BigBitField blob bytea blob UUIDField text uuid varchar(40) BinaryUUIDField blob bytea varbinary(16) DateTimeField datetime timestamp datetime support for custom field types in peewee. In this example we will create a UUID field for postgresql (which has a native UUID column type). To add a custom field type you need to first identify what type intended only as an example. Let’s start by defining our UUID field: class UUIDField(Field): field_type = 'uuid' We will store the UUIDs in a native UUID column. Since psycopg2 treats the data as a string0 码力 | 282 页 | 1.02 MB | 1 年前3 peewee Documentation
Release 3.5.0BlobField blob bytea blob BitField integer bigint bigint BigBitField blob bytea blob UUIDField text uuid varchar(40) BinaryUUIDField blob bytea varbinary(16) DateTimeField datetime timestamp datetime support for custom field types in peewee. In this example we will create a UUID field for postgresql (which has a native UUID column type). To add a custom field type you need to first identify what type intended only as an example. Let’s start by defining our UUID field: class UUIDField(Field): field_type = 'uuid' We will store the UUIDs in a native UUID column. Since psycopg2 treats the data as a string0 码力 | 282 页 | 1.02 MB | 1 年前3
 peewee Documentation
Release 3.4.0BlobField blob bytea blob BitField integer bigint bigint BigBitField blob bytea blob UUIDField text uuid varchar(40) BinaryUUIDField blob bytea varbinary(16) DateTimeField datetime timestamp datetime support for custom field types in peewee. In this example we will create a UUID field for postgresql (which has a native UUID column type). To add a custom field type you need to first identify what type intended only as an example. Let’s start by defining our UUID field: class UUIDField(Field): field_type = 'uuid' We will store the UUIDs in a native UUID column. Since psycopg2 treats the data as a string0 码力 | 284 页 | 1.03 MB | 1 年前3 peewee Documentation
Release 3.4.0BlobField blob bytea blob BitField integer bigint bigint BigBitField blob bytea blob UUIDField text uuid varchar(40) BinaryUUIDField blob bytea varbinary(16) DateTimeField datetime timestamp datetime support for custom field types in peewee. In this example we will create a UUID field for postgresql (which has a native UUID column type). To add a custom field type you need to first identify what type intended only as an example. Let’s start by defining our UUID field: class UUIDField(Field): field_type = 'uuid' We will store the UUIDs in a native UUID column. Since psycopg2 treats the data as a string0 码力 | 284 页 | 1.03 MB | 1 年前3
共 226 条
- 1
- 2
- 3
- 4
- 5
- 6
- 23














 
 