semvec/pypi-packages huggingface dataset:
django-keyset-pagination-plus 0.9.10
Keyset Pagination (seek method) for django.
Requires Python: >=2.7

# Keyset Pagination for Django.

Django pagination uses the LIMIT/OFFSET method. This is fine for smaller offsets, but once you start getting beyond a few pages, it can perform really badly. This is because the database needs to fetch all of the previous rows, even though it discards them.

Using Keyset Pagination allows for better performing "next page" fetches, at the cost of not being able to randomly fetch a page. That is, if you know the last element from page N-1, then you may fetch page N, but otherwise you really can't.

Keyset Pagination, sometimes called the Seek Method, has been documented by [Markus Winand](https://use-the-index-luke.com/sql/partial-results/fetch-next-page) and [Joe Nelson](https://www.citusdata.com/blog/2016/03/30/five-ways-to-paginate/). If you are not familiar with the concept, I strongly suggest you read the articles above.

In order to use the paginator within this package, you will probably also need to use the provided View mixin: this changes the way a queryset is paginated to enable non-integer "page numbers".

    class List(PaginationMixin, ListView):
        paginator_class = KeysetPaginator
        paginate_by = 10
        queryset = MyModel.objects.order_by('-timestamp', 'group')

You won't be able to iterate through page numbers in a template in the same way: you are limited to next and previous pages. Otherwise, you construct them in largely the same way:

    <a href="{% url 'mymodel:list' %}?page={{ page_obj.previous_page_number }}">
      Prev Page
    </a>

    <a href="{% url 'mymodel:list' %}?page={{ page_obj.next_page_number }}">
      Next Page
    </a>

Note that you do not get access to the length of the queryset, nor the number of pages, because these could be expensive queries. You really don't need to know that ;)

However, I like to use GET forms to [enable pagination of filtered results](https://schinckel.net/2014/08/17/leveraging-html-and-django-forms%3A-pagination-of-filtered-results/):

    <button form="target-form"
            name="page"
            value="{{ page_obj.previous_page_number }}"
            type="submit">
      &larr; Prev Page
    </button>

    <button form="target-form"
            name="page"
            value="{{ page_obj.next_page_number }}"
            type="submit">
      Next Page &rarr;
    <button>


See https://schinckel.net/2018/11/23/keyset-pagination-in-django/ for more details about how this package works.
kaiju-automator-lib 1.10.3.dev1
kaiju-automator-lib
Requires Python: >=3.7
Keywords: kaiju_automator_lib

# kaiju-automator-lib

This library is used as the python interface between client software and kaiju-mqtt-py, to make requests of the automator module on the RAE.

This library is used for a few purposes:

* Get a test plan for a device
* Run a test plan for a device
* Cancel a test plan currently running on a device

## Request data format

Most requests to the automator module require a device identifier. This is one or more of: an ESN, an IP, or an ADB serial number. Examples:

```json
{"device_ip": "192.168.144.10"}
{"device_esn": "RKU..."}
{"device_serial": "..."}
```

There is a newer format that moves this into a "target" object with shorter syntax:
```json
{"target": {"ip": "192.168.144.10"} }
{"target": {"esn": "RKU..."} }
{"target": {"serial": "..."} }
```

These identifiers are typically merged into larger request objects, such as test plan run or test plan cancel requests.

## Test plan response data format

The test plan data format is described generally in client.py. A more general discussion of what decisions can be made from the contents of this object needs to be written.

## Test plan run request data format

The test plan run request data format is also described generally in client.py. It requires only minor modifications to the response from a test plan request. 

## Test result data format

Test plan results are reported as a map describing the results of a test plan run. These formats should be more generally documented in a language-agnostic location, as they apply to all clients of the automator.