locust 2.20.1.dev28__tar.gz → 2.20.2__tar.gz

{locust-2.20.1.dev28 → locust-2.20.2}/.git-blame-ignore-revs

@@ -5,3 +5,9 @@
 6ec972f4dbb880bf0c7a11809e6c1ba194c9784c
 # upgrade code style to use f-strings using flynt
 313b80f27f525441c449593a3aeaf38389f63c13
+# upgrade typing annotations using fix-future-annotations
+b5324820b299b1fe7da0608f0cc8ec47f58b1e40
+# upgrade code style to 3.8 using pyupgrade
+60f3bceacc4ab9567433d40ae3ed280750f55ff1
+# sort imports using ruff
+f99e9df700a8020e4c1967eb42dcb37ddd26e296

{locust-2.20.1.dev28 → locust-2.20.2}/.github/workflows/tests.yml

@@ -16,8 +16,7 @@ jobs:
         include:
           #- {name: Windows, python: '3.9', os: windows-latest, tox: py39}
           #- {name: Mac, python: '3.9', os: macos-latest, tox: py39}
-          - { name: "flake8", python: "3.11", os: ubuntu-latest, tox: "flake8" }
-          - { name: "black", python: "3.11", os: ubuntu-latest, tox: "black" }
+          - { name: "ruff", python: "3.11", os: ubuntu-latest, tox: "ruff" }
           - { name: "mypy", python: "3.10", os: ubuntu-latest, tox: "mypy" }
           # run some integration tests and abort immediately if they fail, for faster feedback
           - { name: "fail_fast_test_main", python: "3.12", os: ubuntu-latest, tox: fail_fast_test_main }
@@ -48,7 +47,7 @@ jobs:
       - run: python -m pip install tox
       - run: python -m tox -e ${{ matrix.tox }}
 
-  lint_typecheck_webui:
+  lint_typecheck_test_webui:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v3

{locust-2.20.1.dev28 → locust-2.20.2}/.gitignore

@@ -27,3 +27,4 @@ __pycache__
 .sass-cache/
 .env
 yarn-error.log
+.venv

locust-2.20.2/.vscode/extensions.json

@@ -0,0 +1,6 @@
+{
+    "recommendations": [
+        "charliermarsh.ruff",
+        "ms-python.mypy-type-checker"
+    ]
+}

{locust-2.20.1.dev28 → locust-2.20.2}/.vscode/settings.json

@@ -36,6 +36,7 @@
     },
     "restructuredtext.confPath": "${workspaceFolder}/docs",
     "[python]": {
-        "editor.defaultFormatter": "ms-python.black-formatter"
+        "editor.formatOnSave": true,
+        "editor.defaultFormatter": "charliermarsh.ruff"
     },
 }

{locust-2.20.1.dev28 → locust-2.20.2}/CHANGELOG.md

@@ -1,6 +1,24 @@
 # Detailed changelog
 The most important changes can also be found in [the documentation](https://docs.locust.io/en/latest/changelog.html).
 
+## [2.20.1](https://github.com/locustio/locust/tree/2.20.1) (2024-01-03)
+
+[Full Changelog](https://github.com/locustio/locust/compare/2.20.0...2.20.1)
+
+**Fixed bugs:**
+
+- Vite-version needs to be updated [\#2528](https://github.com/locustio/locust/issues/2528)
+- Issue of 100% CPU usage when closing WebSocket connections. [\#2516](https://github.com/locustio/locust/issues/2516)
+
+**Merged pull requests:**
+
+- Update Vite to 4.5.1 [\#2530](https://github.com/locustio/locust/pull/2530) ([cyberw](https://github.com/cyberw))
+- Bump vite from 4.4.9 to 4.4.12 in /locust/webui [\#2527](https://github.com/locustio/locust/pull/2527) ([dependabot[bot]](https://github.com/apps/dependabot))
+- update docker actions to get rid of node12 deprecation warnings [\#2524](https://github.com/locustio/locust/pull/2524) ([mgor](https://github.com/mgor))
+- Support IPv6 for zmq connection between master and worker [\#2521](https://github.com/locustio/locust/pull/2521) ([simonwu-sn](https://github.com/simonwu-sn))
+- run\_single\_user improvements [\#2519](https://github.com/locustio/locust/pull/2519) ([cyberw](https://github.com/cyberw))
+- Bump Requests to 2.26.0, remove explicit dependency on charset\_normalizer [\#2518](https://github.com/locustio/locust/pull/2518) ([cyberw](https://github.com/cyberw))
+
 ## [2.20.0](https://github.com/locustio/locust/tree/2.20.0) (2023-12-13)
 
 [Full Changelog](https://github.com/locustio/locust/compare/2.19.1...2.20.0)

{locust-2.20.1.dev28/locust.egg-info → locust-2.20.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: locust
-Version: 2.20.1.dev28
+Version: 2.20.2
 Summary: Developer friendly load testing framework
 License: MIT
 Project-URL: Homepage, https://locust.io/
@@ -36,7 +36,7 @@ Requires-Dist: pyzmq>=25.0.0
 Requires-Dist: geventhttpclient>=2.0.11
 Requires-Dist: ConfigArgParse>=1.5.5
 Requires-Dist: psutil>=5.9.1
-Requires-Dist: Flask-BasicAuth>=0.2.0
+Requires-Dist: Flask-Login>=0.6.3
 Requires-Dist: Flask-Cors>=3.0.10
 Requires-Dist: roundrobin>=0.0.2
 Requires-Dist: pywin32; platform_system == "Windows"

{locust-2.20.1.dev28 → locust-2.20.2}/benchmarks/dispatch.py

@@ -5,16 +5,16 @@ for calculating the distribution of users on each workers. This benchmark is to
 by people working on Locust's development.
 """
 
+from locust import User
+from locust.dispatch import UsersDispatcher
+from locust.runners import WorkerNode
+
 import itertools
 import statistics
 import time
 
 from prettytable import PrettyTable
 
-from locust import User
-from locust.dispatch import UsersDispatcher
-from locust.runners import WorkerNode
-
 
 class User1(User):
     weight = 5
@@ -632,8 +632,8 @@ if __name__ == "__main__":
         print()
         print(table)
 
-        with open(f"results-dispatch-benchmarks-{int(now)}.txt", "wt") as file:
+        with open(f"results-dispatch-benchmarks-{int(now)}.txt", "w") as file:
             file.write(table.get_string())
 
-        with open(f"results-dispatch-benchmarks-{int(now)}.json", "wt") as file:
+        with open(f"results-dispatch-benchmarks-{int(now)}.json", "w") as file:
             file.write(table.get_json_string())

{locust-2.20.1.dev28 → locust-2.20.2}/docs/changelog.rst

@@ -4,6 +4,13 @@ Changelog Highlights
 
 For full details of the Locust changelog, please see https://github.com/locustio/locust/blob/master/CHANGELOG.md
 
+2.20.1
+======
+* run_single_user improvements https://github.com/locustio/locust/pull/2519
+* Support IPv6 for zmq connection between master and worker https://github.com/locustio/locust/pull/2521
+* Modern UI: Update Vite to 4.5.1 https://github.com/locustio/locust/pull/2530
+* Other tiny fixes
+
 2.20.0
 ======
 * Add event.measure context manager for simpler firing of request event (experimental) https://github.com/locustio/locust/pull/2511

{locust-2.20.1.dev28 → locust-2.20.2}/docs/conf.py

@@ -7,11 +7,12 @@
 # All configuration values have a default value; values that are commented out
 # serve to show the default value.
 
+from locust.argument_parser import get_empty_argument_parser, setup_parser_arguments
+
 import os
 import subprocess
-import sphinx_rtd_theme
 
-from locust.argument_parser import get_empty_argument_parser, setup_parser_arguments
+import sphinx_rtd_theme
 
 
 # Run command `locust --help` and store output in cli-help-output.txt which is included in the docs

{locust-2.20.1.dev28 → locust-2.20.2}/docs/configuration.rst

@@ -164,6 +164,44 @@ The Web UI will display:
 
 |
 
+With the new ``--modern-ui``, the class picker will addtionally allow for configuring any settings for each selected user.
+This includes selecting tasks, configuring the weight or fixed count, and configuring the host.
+
+It is even possible to add custom arguments that you wish to be configurable for each user. Simply add a ``json`` classethod
+to your user:
+
+.. code-block:: python
+    class Example(HttpUser):
+        @task
+        def example_task(self):
+            self.client.get(f"/example/{self.some_custom_arg}")
+
+        @classmethod
+        def json(self):
+            return {
+                "host": self.host,
+                "some_custom_arg": "example"
+            }
+
+Configuration for the User classes
+==================================
+
+You can configure any settings you may wish for each user on the command line, the same as you may in the modern UI.
+Using the ``--config-users`` argument, you may pass a JSON string or file with your user configuration. To configure
+multiple users you pass multiple arguments to ``--config-users`` or use a JSON Array.
+
+Each user settings object must contain a key ``user_class_name``. This key corresponds to the class that you wish
+to configure.
+
+Example:
+
+.. code-block:: console
+
+    $ locust --config-users '{"user_class_name": "Example", "fixed_count": 1}'
+    $ locust --config-users '[{"user_class_name": "Example", "fixed_count": 1}, {"user_class_name": "ExampleTwo", "fixed_count": 2}]'
+    $ locust --config-users '{"user_class_name": "Example", "fixed_count": 1}' '{"user_class_name": "ExampleTwo", "fixed_count": 2}'
+    $ locust --config-users config_users.json
+
 Custom arguments
 ================
 
@@ -199,8 +237,11 @@ The list of statistics parameters that can be modified is:
 | CURRENT_RESPONSE_TIME_PERCENTILE_WINDOW   | Window size/resolution - in seconds - when calculating the current response          |
 |                                           | time percentile                                                                      |
 +-------------------------------------------+--------------------------------------------------------------------------------------+
-| PERCENTILES_TO_REPORT                     | The list of response time percentiles to be calculated & reported                    |
+| PERCENTILES_TO_REPORT                     | List of response time percentiles to be calculated & reported                        |
++-------------------------------------------+--------------------------------------------------------------------------------------+
+| PERCENTILES_TO_CHART                      | List of response time percentiles in the screen of chart for Web UI                  |
 +-------------------------------------------+--------------------------------------------------------------------------------------+
-| PERCENTILES_TO_CHART                      | The list of response time percentiles for response time chart                        |
+| PERCENTILES_TO_STATISTICS                 | List of response time percentiles in the screen of statistics for Web UI             |
+|                                           | This parameter supports only modern UI                                               |
 +-------------------------------------------+--------------------------------------------------------------------------------------+
 

{locust-2.20.1.dev28 → locust-2.20.2}/docs/developing-locust.rst

@@ -31,11 +31,11 @@ We use `tox <https://tox.readthedocs.io/en/stable/>`_ to automate tests across m
 
     $ pip3 install tox
     $ tox
-    py37 create: /home/myuser/git/locust/.tox/py37
-    py37 installdeps: mock, retry, pyquery, cryptography
     ...
-    Successfully installed ConfigArgParse-1.5.3 Flask-BasicAuth-0.2.0 Flask-Cors-3.0.10 Jinja2-3.1.2 MarkupSafe-2.1.1 Six-1.16.0 Werkzeug-2.2.2 brotli-1.0.9 click-8.1.3 flask-2.2.2 gevent-22.10.1 geventhttpclient-2.0.8 greenlet-1.1.3.post0 itsdangerous-2.1.2 locust-2.12.2 msgpack-1.0.4 psutil-5.9.2 pyzmq-24.0.1 roundrobin-0.0.4 typing-extensions-4.4.0 zope.event-4.5.0 zope.interface-5.5.0
-    py37 run-test: commands[1] | python3 -m coverage run -m unittest discover
+    py38: install_deps> python -I -m pip install cryptography mock pyquery retry
+    py38: commands[0]> python3 -m pip install .
+    ...
+    py38: commands[1]> python3 -m unittest discover
     ...
 
 To only run a specific suite or specific test you can call `pytest <https://docs.pytest.org/>`_ directly:
@@ -44,38 +44,28 @@ To only run a specific suite or specific test you can call `pytest <https://docs
 
     $ pytest locust/test/test_main.py::DistributedIntegrationTests::test_distributed_tags
 
-Format code
-===========
+Formatting and linting
+======================
 
-Locust follows the `black <https://github.com/psf/black>`_ formatting standard, and the build will fail if code does not adhere to it. If you run vscode it will automatically run every time you save a file, but if your editor doesn't support it you can run it manually:
+Locust uses `ruff <https://github.com/astral-sh/ruff/>`_ for formatting and linting. The build will fail if code does not adhere to it. If you run vscode it will automatically run every time you save a file, but if your editor doesn't support it you can run it manually:
 
 .. code-block:: console
 
-    $ pip3 install black
-    $ python -m black <file_to_be_formatted>
+    $ pip3 install ruff
+    $ python -m ruff --fix <file_or_folder_to_be_formatted>
+    $ python -m ruff format <file_or_folder_to_be_formatted>
 
 You can validate the whole project using tox:
 
 .. code-block:: console
 
-    $ tox -e black
-    black installed: black==22.8.0,click==8.1.3,mypy-extensions==0.4.3,pathspec==0.10.1,platformdirs==2.5.2,tomli==2.0.1,typing_extensions==4.4.0
-    black run-test-pre: PYTHONHASHSEED='3136620079'
-    black run-test: commands[0] | black --check .
-    All done! ✨ 🍰 ✨
-    99 files would be left unchanged.
-
-Linting
-=======
-
-Our code is checked using `flake8 <https://flake8.pycqa.org/en/latest/flake8>`_:
-
-.. code-block:: console
-
-    $ tox -e flake8
-    flake8 installed: flake8==5.0.4,mccabe==0.7.0,pycodestyle==2.9.1,pyflakes==2.5.0
-    flake8 run-test-pre: PYTHONHASHSEED='1517754253'
-    flake8 run-test: commands[0] | flake8 . --count --show-source --statistics
+    $ tox -e ruff
+    ruff: install_deps> python -I -m pip install ruff==0.1.13
+    ruff: commands[0]> ruff check .
+    ruff: commands[1]> ruff format --check
+    104 files already formatted
+      ruff: OK (1.41=setup[1.39]+cmd[0.01,0.01] seconds)
+      congratulations :) (1.47 seconds)
 
 Build documentation
 ===================

{locust-2.20.1.dev28 → locust-2.20.2}/docs/extending-locust.rst

@@ -128,6 +128,29 @@ source code.
 
 
 
+Adding Authentication to the Web UI
+===================================
+
+Locust uses `Flask-Login <https://pypi.org/project/Flask-Login/>`_ to handle authentication. The ``login_manager`` is
+exposed on ``environment.web_ui.app``, allowing the flexibility for you to implement any kind of auth that you would like!
+
+To use username / password authentication, simply provide a ``username_password_callback`` to the ``environment.web_ui.auth_args``.
+You are responsible for defining the route for the callback and implementing the authentication.
+
+Authentication providers can additionally be configured to allow authentication from 3rd parties such as GitHub or an SSO.
+Simply provide a list of desired ``auth_providers``. You may specify the ``label`` and ``icon`` for display on the button.
+The ``callback_url`` will be the url that the button directs to. You will be responsible for defining the callback route as
+well as the authentication with the 3rd party.
+
+Whether you are using username / password authentication, an auth provider, or both, a ``user_loader`` needs to be proivded
+to the ``login_manager``. The ``user_loader`` should return ``None`` to deny authentication or return a User object when
+authentication to the app should be granted.
+
+A full example can be seen `in the auth example <https://github.com/locustio/locust/tree/master/examples/web_ui_auth.py>`_.
+
+
+
+
 Run a background greenlet
 =========================
 

{locust-2.20.1.dev28 → locust-2.20.2}/docs/requirements.txt

@@ -1,6 +1,6 @@
 sphinx==4.3.2
 sphinx-rtd-theme==0.5.2
-readthedocs-sphinx-search==0.1.2
+readthedocs-sphinx-search==0.3.2
 Sphinx-Substitution-Extensions==2020.9.30.0
 Pygments==2.16.1
 alabaster==0.7.13

{locust-2.20.1.dev28 → locust-2.20.2}/docs/running-distributed.rst

@@ -4,29 +4,24 @@
 Distributed load generation
 ===========================
 
-A single process running Locust can simulate a reasonably high throughput. For a simple test plan it should be able to make many hundreds of requests per second, thousands if you use :ref:`FastHttpUser <increase-performance>`.
+A single process running Locust can simulate a reasonably high throughput. For a simple test plan and small payloads it can make more than a thousand requests per second, possibly over ten thousand if you use :ref:`FastHttpUser <increase-performance>`.
 
-But if your test plan is complex or you want to run even more load, you'll need to scale out to multiple processes, maybe even multiple machines. Because Python cannot fully utilize more than one core per process (see `GIL <https://realpython.com/python-gil/>`_), you may need to run **one worker instance per processor core** in order to have access to all your computing power.
+But if your test plan is complex or you want to run even more load, you'll need to scale out to multiple processes, maybe even multiple machines. Fortunately, Locust supports distributed runs out of the box.
 
-To do this, you start one instance of Locust in master mode using the ``--master`` flag and multiple worker instances using the ``--worker`` flag. If the workers are not on the same machine as the master you use ``--master-host`` to point them to the IP/hostname of the machine running the master.
+To do this, you start one instance of Locust with the ``--master`` flag and one or more using the ``--worker`` flag. The master instance runs Locust's web interface, and tells the workers when to spawn/stop Users. The worker instances run your Users and send statistics back to the master. The master instance doesn't run any Users itself.
 
-To make this easier, you can use the ``--processes`` flag to launch multiple instances. By default it will launch a master process and the specified number of worker processes. Used in combination with ``--worker`` it will only launch the workers.
+To simplify startup, you can use the ``--processes`` flag. It will launch a master process and the specified number of worker processes. It can also be used in combination with ``--worker``, then it will only launch workers. This feature relies on `fork() <https://linux.die.net/man/3/fork>`_ so it doesn't work on Windows.
 
 .. note::
-    ``--processes`` was introduced in Locust 2.19 and is somewhat experimental. Child processes are launched using fork, which is not available in Windows.
-
-The master instance runs Locust's web interface, and tells the workers when to spawn/stop Users. The worker instances run your Users and send statistics back to the master. The master instance doesn't run any Users itself.
-
-Both the master and worker machines must have a copy of the locustfile when running Locust distributed.
+    Because Python cannot fully utilize more than one core per process (see `GIL <https://realpython.com/python-gil/>`_), you need to run one worker instance per processor core in order to have access to all your computing power.
 
 .. note::
-    There is almost no limit to how many *Users* you can run per worker. Locust/gevent can run thousands or even tens of thousands of Users per process just fine, as long as their total request rate (RPS) is not too high.
+    There is almost no limit to how many Users you can run per worker. Locust/gevent can run thousands or even tens of thousands of Users per process just fine, as long as their total request rate (RPS) is not too high.
 
-.. note::
-    If Locust is getting close to running out of CPU resources, it will log a warning. If there is no warning, you can be pretty sure your test is not limited by load generator CPU.
+    If Locust *is* getting close to running out of CPU resources, it will log a warning. If there is no warning but you are still unable to generate the expected load, then the problem must be `something else <https://github.com/locustio/locust/wiki/FAQ#increase-my-request-raterps>`_.
 
-Example 1: Everything on one machine
-====================================
+Single machine
+==============
 
 It is really simple to launch a master and 4 worker processes::
 
@@ -36,21 +31,34 @@ You can even auto-detect the number of cores in your machine and launch one work
 
     locust --processes -1
 
-Example 2: Multiple machines
-============================
+Multiple machines
+=================
 
 Start locust in master mode on one machine::
 
     locust -f my_locustfile.py --master
 
-And then on each worker machine::
+And then on each worker machine (make sure they also have a copy of the locustfile):
+
+.. code-block:: bash
 
     locust -f my_locustfile.py --worker --master-host <your master's address> --processes 4
 
-Note that both master and worker nodes need access to the locustfile, it is not sent from master to worker automatically. But you can use `locust-swarm <https://github.com/SvenskaSpel/locust-swarm>`_ to automate that.
+Multiple machines, using locust-swarm
+=====================================
+
+Both worker and master need access to the locustfile, and when you make changes to it you'll need to restart all Locust processes. `locust-swarm <https://github.com/SvenskaSpel/locust-swarm>`_ automates this for you. It also solves the issue of firewall/network access from workers to master using SSH tunnels (this is often a problem if the master is running on your workstation and workers are running in some datacenter).
+
+.. code-block:: bash
+
+    pip install locust-swarm
+
+    swarm -f my_locustfile.py --loadgen-list worker-server1,worker-server2 <any other regular locust parameters>
+
+See `locust-swarm <https://github.com/SvenskaSpel/locust-swarm>`_ for more details.
 
-Options
-=======
+Options for distributed load generation
+=======================================
 
 ``--master-host <hostname or ip>``
 ----------------------------------
@@ -85,7 +93,7 @@ Communicating across nodes
 =============================================
 
 When running Locust in distributed mode, you may want to communicate between master and worker nodes in 
-order to coordinate data. This can be easily accomplished with custom messages using the built in messaging hooks:
+order to coordinate the test. This can be easily accomplished with custom messages using the built in messaging hooks:
 
 .. code-block:: python
 

{locust-2.20.1.dev28 → locust-2.20.2}/docs/what-is-locust.rst

@@ -52,9 +52,7 @@ load against a dynamic website where most pages had different content for differ
 verbose configuration files to declare the tests. In Locust we took a different approach. Instead of configuration formats or UIs 
 you'd get a python framework that would let you define the behaviour of your users using Python code. 
 
-`Locust <https://en.wikipedia.org/wiki/Locust>`_ takes its name from the grasshopper species, known for their swarming behaviour. 
-
-Previous versions of Locust used terminology borrowed from nature (swarming, hatching, attacking etc), but now employs more industry standard naming.
+Locust takes its name from the `grasshopper species <https://en.wikipedia.org/wiki/Locust>`_, known for their swarming behaviour. 
 
 :ref:`history`
 

{locust-2.20.1.dev28 → locust-2.20.2}/examples/add_command_line_argument.py

@@ -1,4 +1,4 @@
-from locust import HttpUser, task, events
+from locust import HttpUser, events, task
 
 
 @events.init_command_line_parser.add_listener

{locust-2.20.1.dev28 → locust-2.20.2}/examples/basic.py

@@ -1,4 +1,4 @@
-from locust import HttpUser, TaskSet, task, between
+from locust import HttpUser, TaskSet, between, task
 
 
 def index(l):

{locust-2.20.1.dev28 → locust-2.20.2}/examples/browse_docs_sequence_test.py

@@ -1,8 +1,10 @@
 # This locust test script example will simulate a user
 # browsing the Locust documentation on https://docs.locust.io/
 
+from locust import HttpUser, SequentialTaskSet, between, task
+
 import random
-from locust import HttpUser, SequentialTaskSet, task, between
+
 from pyquery import PyQuery
 
 

{locust-2.20.1.dev28 → locust-2.20.2}/examples/browse_docs_test.py

@@ -1,8 +1,10 @@
 # This locust test script example will simulate a user
 # browsing the Locust documentation on https://docs.locust.io/
 
+from locust import HttpUser, TaskSet, between, task
+
 import random
-from locust import HttpUser, TaskSet, task, between
+
 from pyquery import PyQuery
 
 

{locust-2.20.1.dev28 → locust-2.20.2}/examples/custom_messages.py

@@ -1,4 +1,4 @@
-from locust import HttpUser, task, events, between
+from locust import HttpUser, between, events, task
 from locust.runners import MasterRunner, WorkerRunner
 
 usernames = []

{locust-2.20.1.dev28 → locust-2.20.2}/examples/custom_shape/double_wave.py

@@ -1,6 +1,6 @@
+from locust import HttpUser, LoadTestShape, TaskSet, constant, task
+
 import math
-from locust import HttpUser, TaskSet, task, constant
-from locust import LoadTestShape
 
 
 class UserTasks(TaskSet):

{locust-2.20.1.dev28 → locust-2.20.2}/examples/custom_shape/stages.py

@@ -1,5 +1,4 @@
-from locust import HttpUser, TaskSet, task, constant
-from locust import LoadTestShape
+from locust import HttpUser, LoadTestShape, TaskSet, constant, task
 
 
 class UserTasks(TaskSet):

{locust-2.20.1.dev28 → locust-2.20.2}/examples/custom_shape/staging_user_classes.py

@@ -1,5 +1,4 @@
-from locust import HttpUser, TaskSet, task, constant
-from locust import LoadTestShape
+from locust import HttpUser, LoadTestShape, TaskSet, constant, task
 
 
 class UserTasks(TaskSet):

{locust-2.20.1.dev28 → locust-2.20.2}/examples/custom_shape/step_load.py

@@ -1,6 +1,6 @@
+from locust import HttpUser, LoadTestShape, TaskSet, constant, task
+
 import math
-from locust import HttpUser, TaskSet, task, constant
-from locust import LoadTestShape
 
 
 class UserTasks(TaskSet):

{locust-2.20.1.dev28 → locust-2.20.2}/examples/custom_shape/wait_user_count.py

@@ -1,10 +1,9 @@
-from collections import namedtuple
+from locust import HttpUser, LoadTestShape, TaskSet, constant, task
+
 import math
-import time
 import random
-
-from locust import HttpUser, TaskSet, task, constant
-from locust import LoadTestShape
+import time
+from collections import namedtuple
 
 
 class UserTasks(TaskSet):

{locust-2.20.1.dev28 → locust-2.20.2}/examples/custom_wait_function.py

@@ -1,4 +1,5 @@
 from locust import HttpUser, TaskSet, task
+
 import random
 
 

{locust-2.20.1.dev28 → locust-2.20.2}/examples/custom_xmlrpc_client/xmlrpc_locustfile.py

@@ -1,8 +1,8 @@
-import time
-from xmlrpc.client import ServerProxy, Fault
-
 from locust import User, task
 
+import time
+from xmlrpc.client import Fault, ServerProxy
+
 
 class XmlRpcClient(ServerProxy):
     """

{locust-2.20.1.dev28 → locust-2.20.2}/examples/debugging.py

@@ -1,4 +1,4 @@
-from locust import HttpUser, task, run_single_user
+from locust import HttpUser, run_single_user, task
 
 
 class QuickstartUser(HttpUser):

{locust-2.20.1.dev28 → locust-2.20.2}/examples/debugging_advanced.py

@@ -1,4 +1,4 @@
-from locust import HttpUser, task, run_single_user
+from locust import HttpUser, run_single_user, task
 from locust.exception import StopUser
 
 

{locust-2.20.1.dev28 → locust-2.20.2}/examples/dynamic_user_credentials.py

@@ -1,6 +1,6 @@
 # locustfile.py
 
-from locust import HttpUser, TaskSet, task, between
+from locust import HttpUser, TaskSet, between, task
 
 USER_CREDENTIALS = [
     ("user1", "password"),

{locust-2.20.1.dev28 → locust-2.20.2}/examples/events.py

@@ -3,8 +3,7 @@ This is an example of a locustfile that uses Locust's built in event hooks to
 track the sum of the content-length header in all successful HTTP responses
 """
 
-from locust import HttpUser, TaskSet, task, web, between
-from locust import events
+from locust import HttpUser, TaskSet, between, events, task, web
 
 
 class MyTaskSet(TaskSet):

{locust-2.20.1.dev28 → locust-2.20.2}/examples/extend_modern_web_ui.py

@@ -4,12 +4,14 @@ UI extension hooks to track the sum of the content-length header in all
 successful HTTP responses and display them in the web UI.
 """
 
-import os
+from locust import HttpUser, TaskSet, between, events, task, web
+
 import json
-from time import time
+import os
 from html import escape
-from locust import HttpUser, TaskSet, task, web, between, events
-from flask import Blueprint, render_template, jsonify, make_response, request
+from time import time
+
+from flask import Blueprint, jsonify, make_response, render_template, request
 
 
 class MyTaskSet(TaskSet):

{locust-2.20.1.dev28 → locust-2.20.2}/examples/extend_web_ui/extend.py

@@ -4,11 +4,13 @@ UI extension hooks to track the sum of the content-length header in all
 successful HTTP responses and display them in the web UI.
 """
 
+from locust import HttpUser, TaskSet, between, events, task, web
+
 import os
-from time import time
 from html import escape
-from locust import HttpUser, TaskSet, task, web, between, events
-from flask import Blueprint, render_template, jsonify, make_response
+from time import time
+
+from flask import Blueprint, jsonify, make_response, render_template
 
 
 class MyTaskSet(TaskSet):