per page, with , order by , clip by
Results of 1 - 10 of about 64 for execution (0.010 sec.)
Tasks — Django 6.1 ドキュメント 12549
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Tasks ¶ New in Django 6.0. The Task framework provides the contract and plumbing for background work, not the engine that runs it. The Tasks API def ... ines how work is described, queued, and tracked, but leaves actual execution to external infrastructure. Task definition ¶ The task decorator ¶ task ( * , priority = 0 , queue_name = 'default' , back ... ifying Tasks for usage examples. enqueue ( * args , ** kwargs ) [ソース] ¶ Enqueues the Task to the Task backend for later execution. Arguments are passed to the Task 's function after a round-trip through a json.dumps() / json.loads() cycle. Hence, all a ... Context cannot be modified. task_result ¶ The TaskResult currently being run. attempt [ソース] ¶ The number of the current execution attempts for this Task, starting at 1. Task results ¶ class TaskResultStatus [ソース] ¶ An Enum representing the status of ...
https://man.mtool.work/django/6.1/ref/tasks.html
Tasks — Django 6.1 ドキュメント 12463
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Tasks ¶ New in Django 6.0. The Task framework provides the contract and plumbing for background work, not the engine that runs it. The Tasks API def ... ines how work is described, queued, and tracked, but leaves actual execution to external infrastructure. Task definition ¶ The task decorator ¶ task ( * , priority = 0 , queue_name = 'default' , back ... ifying Tasks for usage examples. enqueue ( * args , ** kwargs ) [ソース] ¶ Enqueues the Task to the Task backend for later execution. Arguments are passed to the Task 's function after a round-trip through a json.dumps() / json.loads() cycle. Hence, all a ... Context cannot be modified. task_result ¶ The TaskResult currently being run. attempt [ソース] ¶ The number of the current execution attempts for this Task, starting at 1. Task results ¶ class TaskResultStatus [ソース] ¶ An Enum representing the status of ...
https://man.mtool.work/django/6.1/ref/tasks.html
Django 1.4.11 リリースノート — Django 6.1 ドキュメント 9605
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.11 リリースノート ¶ April 21, 2014 Django 1.4.11 fixes three security issues in 1.4.10. Additionally, Django's vendored version of six, d ... jango.utils.six , has been upgraded to the latest release (1.6.1). Unexpected code execution using reverse() ¶ Django's URL handling is based on a mapping of regex patterns (representing the URLs) to callable views, ... has import-time side effects, those side effects will occur. Thus it is possible for an attacker to cause unexpected code execution, given the following conditions: One or more views are present which construct a URL based on user input (commonly, a "nex ... f an action). One or more modules are known to an attacker to exist on the server's Python import path, which perform code execution with side effects on importing. To remedy this, reverse() will now only accept and import dotted paths based on the view-c ...
https://man.mtool.work/django/6.1/releases/1.4.11.html
Django 1.5.3 リリースノート — Django 6.1 ドキュメント 9605
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.5.3 リリースノート ¶ September 10, 2013 This is Django 1.5.3, the third release in the Django 1.5 series. It addresses one security issue a ... emplate author to put the ssi file in a user-controlled variable, but it's possible in principle. Mitigating a remote-code execution vulnerability in django.contrib.sessions ¶ django.contrib.sessions currently uses pickle to serialize session data before ... ession storage signs the cookie-stored data to prevent tampering, a SECRET_KEY leak immediately escalates to a remote code execution vulnerability. This attack can be mitigated by serializing session data using JSON rather than pickle . To facilitate this ... e details. 目次 Django 1.5.3 リリースノート Directory traversal vulnerability in ssi template tag Mitigating a remote-code execution vulnerability in django.contrib.sessions 前のトピックへ Django 1.5.4リリースノート 次のトピックへ Django 1.5.2 リリースノー ...
https://man.mtool.work/django/6.1/releases/1.5.3.html
Django 1.6.3 リリースノート — Django 6.1 ドキュメント 9605
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.6.3 リリースノート ¶ April 21, 2014 Django 1.6.3 fixes several bugs in 1.6.2, including three security issues, and makes one backwards-inco ... mpatible change: Unexpected code execution using reverse() ¶ Django's URL handling is based on a mapping of regex patterns (representing the URLs) to callable views, ... has import-time side effects, those side effects will occur. Thus it is possible for an attacker to cause unexpected code execution, given the following conditions: One or more views are present which construct a URL based on user input (commonly, a "nex ... f an action). One or more modules are known to an attacker to exist on the server's Python import path, which perform code execution with side effects on importing. To remedy this, reverse() will now only accept and import dotted paths based on the view-c ...
https://man.mtool.work/django/6.1/releases/1.6.3.html
Django 1.4.11 リリースノート — Django 6.1 ドキュメント 9505
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.11 リリースノート ¶ April 21, 2014 Django 1.4.11 fixes three security issues in 1.4.10. Additionally, Django's vendored version of six, d ... jango.utils.six , has been upgraded to the latest release (1.6.1). Unexpected code execution using reverse() ¶ Django's URL handling is based on a mapping of regex patterns (representing the URLs) to callable views, ... has import-time side effects, those side effects will occur. Thus it is possible for an attacker to cause unexpected code execution, given the following conditions: One or more views are present which construct a URL based on user input (commonly, a "nex ... f an action). One or more modules are known to an attacker to exist on the server's Python import path, which perform code execution with side effects on importing. To remedy this, reverse() will now only accept and import dotted paths based on the view-c ...
https://man.mtool.work/django/6.1/releases/1.4.11.html
Django 1.6.3 リリースノート — Django 6.1 ドキュメント 9505
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.6.3 リリースノート ¶ April 21, 2014 Django 1.6.3 fixes several bugs in 1.6.2, including three security issues, and makes one backwards-inco ... mpatible change: Unexpected code execution using reverse() ¶ Django's URL handling is based on a mapping of regex patterns (representing the URLs) to callable views, ... has import-time side effects, those side effects will occur. Thus it is possible for an attacker to cause unexpected code execution, given the following conditions: One or more views are present which construct a URL based on user input (commonly, a "nex ... f an action). One or more modules are known to an attacker to exist on the server's Python import path, which perform code execution with side effects on importing. To remedy this, reverse() will now only accept and import dotted paths based on the view-c ...
https://man.mtool.work/django/6.1/releases/1.6.3.html
Django 1.5.6 リリースノート — Django 6.1 ドキュメント 9505
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.5.6 リリースノート ¶ April 21, 2014 Django 1.5.6 fixes several bugs in 1.5.5, including three security issues. Unexpected code execution us ... has import-time side effects, those side effects will occur. Thus it is possible for an attacker to cause unexpected code execution, given the following conditions: One or more views are present which construct a URL based on user input (commonly, a "nex ... f an action). One or more modules are known to an attacker to exist on the server's Python import path, which perform code execution with side effects on importing. To remedy this, reverse() will now only accept and import dotted paths based on the view-c ... six, django.utils.six , has been upgraded to the latest release (1.6.1). 目次 Django 1.5.6 リリースノート Unexpected code execution using reverse() Caching of anonymous pages could reveal CSRF token MySQL typecasting バグ修正 前のトピックへ Django 1.5.7 ...
https://man.mtool.work/django/6.1/releases/1.5.6.html
Django 1.5.6 リリースノート — Django 6.1 ドキュメント 9404
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.5.6 リリースノート ¶ April 21, 2014 Django 1.5.6 fixes several bugs in 1.5.5, including three security issues. Unexpected code execution us ... has import-time side effects, those side effects will occur. Thus it is possible for an attacker to cause unexpected code execution, given the following conditions: One or more views are present which construct a URL based on user input (commonly, a "nex ... f an action). One or more modules are known to an attacker to exist on the server's Python import path, which perform code execution with side effects on importing. To remedy this, reverse() will now only accept and import dotted paths based on the view-c ... six, django.utils.six , has been upgraded to the latest release (1.6.1). 目次 Django 1.5.6 リリースノート Unexpected code execution using reverse() Caching of anonymous pages could reveal CSRF token MySQL typecasting バグ修正 前のトピックへ Django 1.5.7 ...
https://man.mtool.work/django/6.1/releases/1.5.6.html
Django's Tasks framework — Django 6.1 ドキュメント 8615
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django's Tasks framework ¶ New in Django 6.0: For older Django versions, the django-tasks backport is available. For a web application, there's ofte ... s framework makes it easy to define and enqueue such work. It does not provide a worker mechanism to run Tasks. The actual execution must be handled by infrastructure outside Django, such as a separate process or service. Given that, a task backend capabl ... he request-response lifecycle. Configuring a Task backend ¶ The Task backend determines how and where Tasks are stored for execution and how they are executed. Different Task backends have different characteristics and configuration options, which may imp ... setting in your settings file. Whilst most applications will only need a single backend, multiple are supported. Immediate execution ¶ This is the default backend if another is not specified in your settings file. The ImmediateBackend runs enqueued Tasks ...
https://man.mtool.work/django/6.1/topics/tasks.html
PREV 1 2 3 4 5 6 7 NEXT