%global _empty_manifest_terminate_build 0
Name:		python-django-bootstrap-pagination
Version:	1.7.1
Release:	1
Summary:	Render Django Page objects as Bootstrap 3.x/4.x Pagination compatible HTML
License:	MIT licence, see LICENCE
URL:		https://github.com/jmcclell/django-bootstrap-pagination
Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/4d/af/dbf3ad602a9ab111a7709e4a5a916a7ecac92b37ea28b33ca00104770a93/django-bootstrap-pagination-1.7.1.tar.gz
BuildArch:	noarch


%description
[![PyPi version](https://img.shields.io/pypi/v/django-bootstrap-pagination.svg)](https://pypi.python.org/pypi/django-bootstrap-pagination)
[![PyPi downloads](https://img.shields.io/pypi/dm/django-bootstrap-pagination.svg)](https://pypi.python.org/pypi/django-bootstrap-pagination)
[![Build Status](https://travis-ci.org/jmcclell/django-bootstrap-pagination.png?branch=master)](https://travis-ci.org/jmcclell/django-bootstrap-pagination)


## Django Bootstrap Pagination

*Bootstrap Compatibility*

| Versions         | Bootstrap Versions  | Notes                                                  |
| -----------------| ------------------- | -------------------------------------------------------|
| < 1.1.0          | 2.x                 |                                                        |
| > 1.1.0, < 1.7.0 | 3.x                 |                                                        |
| >= 1.7.0         | 3.x, 4.x            | bootstrap_pager is only compatible with Bootstrap  3.x |


This application serves to make using Twitter's Bootstrap Pagination styles
work seamlessly with Django Page objects. By passing in a Page object and
one or more optional arguments, Bootstrap pagination bars and pagers can
be rendered with very little effort.

Compatible with Django **1.2+**

## Installation

### PIP

This will install the latest stable release from PyPi.

```
    pip install django-bootstrap-pagination
```

### Download

Download the latest stable distribution from:

http://pypi.python.org/pypi/django-bootstrap-pagination

Download the latest development version from:

github @ http://www.github.com/jmcclell/django-bootstrap-pagination

```
    setup.py install
```

## Usage

### Setup

Make sure you include bootstrap_pagination in your installed_apps list in settings.py:

```
    INSTALLED_APPS = (
        'bootstrap_pagination',
    )
```

Additionally, include the following snippet at the top of any template that makes use of
the pagination tags:

```
    {% load bootstrap_pagination %}
```

Finally, make sure that you have the request context processor enabled:

```
    # Django 1.8+
    TEMPLATES = [
        {
            # ...
            'OPTIONS': {
                context_processors': [
                    # ...
                    'django.template.context_processors.request',
                ]
            }
        }
    ]

    # Django < 1.8
    TEMPLATE_CONTEXT_PROCESSORS = {
        "django.core.context_processors.request",
    )
```

# bootstrap_paginate

**All Optional Arguments**

- **range** - Defines the maximum number of page links to show
- **show_prev_next** - Boolean. Defines whether or not to show the Previous and Next
                       links. (Accepts `"true"` or `"false"`)
- **previous_label** - The label to use for the Previous link
- **next_label** - The label to use for the Next link
- **show_first_last** - Boolean. Defines whether or not to show the First and Last links.
                       (Accepts `"true"` or `"false"`)
- **first_label** - The label to use for the First page link
- **last_label** - The label to use for the Last page link
- **show_index_range** - Boolean, defaults to "false". If "true" shows index range of items instead of page numbers in the paginator. For example, if paginator is configured for 50 items per page, show_index_range="true" will display [1-50, 51-100, **101-150**, 151-200, 201-250, etc.] rather than [1, 2, **3**, 4, 5, etc.].
- **url_view_name** - A named URL reference (such as one that might get passed into the URL
                      template tag) to use as the URL template. Must be resolvable by the
                      `reverse()` function. **If this option is not specified, the tag simply
                      uses a relative url such as `?page=1` which is fine in most situations**
- **url_param_name** - Determines the name of the `GET` parameter for the page number. The
                       default is `"page"`. If no **url_view_name** is defined, this string
                       is appended to the url as `?{{url_param_name}}=1`.
- **url_extra_args** - **Only valid when url_view_name is set.** Additional arguments to
                       pass into `reverse()` to resolve the URL.
- **url_extra_kwargs** - **Only valid when `url_view_name` is set.** Additional named
                         arguments to pass into `reverse()` to resolve the URL. Additionally,
                         the template tag will add an extra parameter to this for the
                         page, as it is assumed that if given a url_name, the page will
                         be a named variable in the URL regular expression. In this case,
                         the `url_param_name` continues to be the string used to represent
                         the name. That is, by default, `url_param_name` is equal to `page`
                         and thus it is expected that there is a named `page` argument in the
                         URL referenced by `url_view_name`. This allows us to use pretty
                         pagination URLs such as `/page/1`
- **extra_pagination_classes** - A space separated list of CSS class names that
                             will be added to the top level `<ul>` HTML element.
                             In particular, this can be utilized in Bootstrap 4
                             installations to add the appropriate alignment
                             classes from Flexbox utilities: eg:
                             `justify-content-center`


**Basic Usage**

The following will show a pagination bar with a link to every page, a previous link, and a next link:

```
    {% bootstrap_paginate page_obj %}
```

The following will show a pagination bar with at most 10 page links, a previous link, and a next link:

```
    {% bootstrap_paginate page_obj range=10 %}
```

The following will show a pagination bar with at most 10 page links, a first page link, and a last page link:

```
    {% bootstrap_paginate page_obj range=10 show_prev_next="false" show_first_last="true" %}
```

**Advanced Usage**

Given a url configured such as:

```python
    archive_index_view = ArchiveIndexView.as_view(
        date_field='date',
        paginate_by=10,
        allow_empty=True,
        queryset=MyModel.all(),
        template_name='example/archive.html'
    )

    urlpatterns = patterns(
        'example.views',
        url(r'^$', archive_index_view, name='archive_index'),
        url(r'^page/(?P<page>\d+)/$', archive_index_view,
            name='archive_index_paginated'))
```

We could simply use the basic usage (appending ?page=#) with the *archive_index* URL above,
as the *archive_index_view* class based generic view from django doesn't care how it gets
the page parameter. However, if we want pretty URLs, such as those defined in the
*archive_index_paginated* URL (ie: /page/1), we need to define the URL in our template tag:

```
    {% bootstrap_paginate page_obj url_view_name="archive_index_paginated" %}
```

Because we are using a default page parameter name of "page" and our URL requires no other
parameters, everything works as expected. If our URL required additional parameters, we
would pass them in using the optional arguments **url_extra_args** and **url_extra_kwargs**.
Likewise, if our page parameter had a different name, we would pass in a different
**url_param_name** argument to the template tag.

# bootstrap_pager

A much simpler implementation of the Bootstrap Pagination functionality is the Pager, which
simply provides a Previous and Next link.

**All Optional Arguments**

- **previous_label** - Defines the label for the Previous link
- **next_label** - Defines the label for the Next link
- **previous_title** - Defines the link title for the previous link
- **next_title** - Defines the link title for the next link
- **centered** - Boolean. Defines whether or not the links are centered. Defaults to false.
                 (Accepts "true" or "false")
- **url_view_name** - A named URL reference (such as one that might get passed into the URL
                      template tag) to use as the URL template. Must be resolvable by the
                      `reverse()` function. **If this option is not specified, the tag simply
                      uses a relative url such as `?page=1` which is fine in most situations**
- **url_param_name** - Determines the name of the `GET` parameter for the page number. Th
                       default is `"page"`. If no `url_view_name` is defined, this string
                       is appended to the url as `?{{url_param_name}}=1`.
- **url_extra_args** - **Only valid when `url_view_name` is set.** Additional arguments to
                       pass into `reverse()` to resolve the URL.
- **url_extra_kwargs** - **Only valid when `url_view_name` is set.** Additional named
                         arguments to pass into `reverse()` to resolve the URL. Additionally,
                         the template tag will add an extra parameter to this for the
                         page, as it is assumed that if given a url_name, the page will
                         be a named variable in the URL regular expression. In this case,
                         the `url_param_name` continues to be the string used to represent
                         the name. That is, by default, `url_param_name` is equal to `"page"`
                         and thus it is expected that there is a named `page` argument in the
                         URL referenced by `url_view_name`. This allows us to use pretty
                         pagination URLs such as `/page/1`
- **url_anchor** - The anchor to use in URLs. Defaults to `None`
- **extra_pager_classes** - A space separated list of CSS class names that will be added
                to the top level `<ul>` HTML element. This could be used to, as an
                example, add a class  to prevent the pager from showing up when
                printing.

**Usage**

Usage is basically the same as for bootstrap_paginate. The simplest usage is:

```
    {% bootstrap_pager page_obj %}
```

A somewhat more advanced usage might look like:

```
    {% bootstrap_pager page_obj previous_label="Newer Posts" next_label="Older Posts" url_view_name="post_archive_paginated" %}
```




%package -n python3-django-bootstrap-pagination
Summary:	Render Django Page objects as Bootstrap 3.x/4.x Pagination compatible HTML
Provides:	python-django-bootstrap-pagination
BuildRequires:	python3-devel
BuildRequires:	python3-setuptools
BuildRequires:	python3-pip
%description -n python3-django-bootstrap-pagination
[![PyPi version](https://img.shields.io/pypi/v/django-bootstrap-pagination.svg)](https://pypi.python.org/pypi/django-bootstrap-pagination)
[![PyPi downloads](https://img.shields.io/pypi/dm/django-bootstrap-pagination.svg)](https://pypi.python.org/pypi/django-bootstrap-pagination)
[![Build Status](https://travis-ci.org/jmcclell/django-bootstrap-pagination.png?branch=master)](https://travis-ci.org/jmcclell/django-bootstrap-pagination)


## Django Bootstrap Pagination

*Bootstrap Compatibility*

| Versions         | Bootstrap Versions  | Notes                                                  |
| -----------------| ------------------- | -------------------------------------------------------|
| < 1.1.0          | 2.x                 |                                                        |
| > 1.1.0, < 1.7.0 | 3.x                 |                                                        |
| >= 1.7.0         | 3.x, 4.x            | bootstrap_pager is only compatible with Bootstrap  3.x |


This application serves to make using Twitter's Bootstrap Pagination styles
work seamlessly with Django Page objects. By passing in a Page object and
one or more optional arguments, Bootstrap pagination bars and pagers can
be rendered with very little effort.

Compatible with Django **1.2+**

## Installation

### PIP

This will install the latest stable release from PyPi.

```
    pip install django-bootstrap-pagination
```

### Download

Download the latest stable distribution from:

http://pypi.python.org/pypi/django-bootstrap-pagination

Download the latest development version from:

github @ http://www.github.com/jmcclell/django-bootstrap-pagination

```
    setup.py install
```

## Usage

### Setup

Make sure you include bootstrap_pagination in your installed_apps list in settings.py:

```
    INSTALLED_APPS = (
        'bootstrap_pagination',
    )
```

Additionally, include the following snippet at the top of any template that makes use of
the pagination tags:

```
    {% load bootstrap_pagination %}
```

Finally, make sure that you have the request context processor enabled:

```
    # Django 1.8+
    TEMPLATES = [
        {
            # ...
            'OPTIONS': {
                context_processors': [
                    # ...
                    'django.template.context_processors.request',
                ]
            }
        }
    ]

    # Django < 1.8
    TEMPLATE_CONTEXT_PROCESSORS = {
        "django.core.context_processors.request",
    )
```

# bootstrap_paginate

**All Optional Arguments**

- **range** - Defines the maximum number of page links to show
- **show_prev_next** - Boolean. Defines whether or not to show the Previous and Next
                       links. (Accepts `"true"` or `"false"`)
- **previous_label** - The label to use for the Previous link
- **next_label** - The label to use for the Next link
- **show_first_last** - Boolean. Defines whether or not to show the First and Last links.
                       (Accepts `"true"` or `"false"`)
- **first_label** - The label to use for the First page link
- **last_label** - The label to use for the Last page link
- **show_index_range** - Boolean, defaults to "false". If "true" shows index range of items instead of page numbers in the paginator. For example, if paginator is configured for 50 items per page, show_index_range="true" will display [1-50, 51-100, **101-150**, 151-200, 201-250, etc.] rather than [1, 2, **3**, 4, 5, etc.].
- **url_view_name** - A named URL reference (such as one that might get passed into the URL
                      template tag) to use as the URL template. Must be resolvable by the
                      `reverse()` function. **If this option is not specified, the tag simply
                      uses a relative url such as `?page=1` which is fine in most situations**
- **url_param_name** - Determines the name of the `GET` parameter for the page number. The
                       default is `"page"`. If no **url_view_name** is defined, this string
                       is appended to the url as `?{{url_param_name}}=1`.
- **url_extra_args** - **Only valid when url_view_name is set.** Additional arguments to
                       pass into `reverse()` to resolve the URL.
- **url_extra_kwargs** - **Only valid when `url_view_name` is set.** Additional named
                         arguments to pass into `reverse()` to resolve the URL. Additionally,
                         the template tag will add an extra parameter to this for the
                         page, as it is assumed that if given a url_name, the page will
                         be a named variable in the URL regular expression. In this case,
                         the `url_param_name` continues to be the string used to represent
                         the name. That is, by default, `url_param_name` is equal to `page`
                         and thus it is expected that there is a named `page` argument in the
                         URL referenced by `url_view_name`. This allows us to use pretty
                         pagination URLs such as `/page/1`
- **extra_pagination_classes** - A space separated list of CSS class names that
                             will be added to the top level `<ul>` HTML element.
                             In particular, this can be utilized in Bootstrap 4
                             installations to add the appropriate alignment
                             classes from Flexbox utilities: eg:
                             `justify-content-center`


**Basic Usage**

The following will show a pagination bar with a link to every page, a previous link, and a next link:

```
    {% bootstrap_paginate page_obj %}
```

The following will show a pagination bar with at most 10 page links, a previous link, and a next link:

```
    {% bootstrap_paginate page_obj range=10 %}
```

The following will show a pagination bar with at most 10 page links, a first page link, and a last page link:

```
    {% bootstrap_paginate page_obj range=10 show_prev_next="false" show_first_last="true" %}
```

**Advanced Usage**

Given a url configured such as:

```python
    archive_index_view = ArchiveIndexView.as_view(
        date_field='date',
        paginate_by=10,
        allow_empty=True,
        queryset=MyModel.all(),
        template_name='example/archive.html'
    )

    urlpatterns = patterns(
        'example.views',
        url(r'^$', archive_index_view, name='archive_index'),
        url(r'^page/(?P<page>\d+)/$', archive_index_view,
            name='archive_index_paginated'))
```

We could simply use the basic usage (appending ?page=#) with the *archive_index* URL above,
as the *archive_index_view* class based generic view from django doesn't care how it gets
the page parameter. However, if we want pretty URLs, such as those defined in the
*archive_index_paginated* URL (ie: /page/1), we need to define the URL in our template tag:

```
    {% bootstrap_paginate page_obj url_view_name="archive_index_paginated" %}
```

Because we are using a default page parameter name of "page" and our URL requires no other
parameters, everything works as expected. If our URL required additional parameters, we
would pass them in using the optional arguments **url_extra_args** and **url_extra_kwargs**.
Likewise, if our page parameter had a different name, we would pass in a different
**url_param_name** argument to the template tag.

# bootstrap_pager

A much simpler implementation of the Bootstrap Pagination functionality is the Pager, which
simply provides a Previous and Next link.

**All Optional Arguments**

- **previous_label** - Defines the label for the Previous link
- **next_label** - Defines the label for the Next link
- **previous_title** - Defines the link title for the previous link
- **next_title** - Defines the link title for the next link
- **centered** - Boolean. Defines whether or not the links are centered. Defaults to false.
                 (Accepts "true" or "false")
- **url_view_name** - A named URL reference (such as one that might get passed into the URL
                      template tag) to use as the URL template. Must be resolvable by the
                      `reverse()` function. **If this option is not specified, the tag simply
                      uses a relative url such as `?page=1` which is fine in most situations**
- **url_param_name** - Determines the name of the `GET` parameter for the page number. Th
                       default is `"page"`. If no `url_view_name` is defined, this string
                       is appended to the url as `?{{url_param_name}}=1`.
- **url_extra_args** - **Only valid when `url_view_name` is set.** Additional arguments to
                       pass into `reverse()` to resolve the URL.
- **url_extra_kwargs** - **Only valid when `url_view_name` is set.** Additional named
                         arguments to pass into `reverse()` to resolve the URL. Additionally,
                         the template tag will add an extra parameter to this for the
                         page, as it is assumed that if given a url_name, the page will
                         be a named variable in the URL regular expression. In this case,
                         the `url_param_name` continues to be the string used to represent
                         the name. That is, by default, `url_param_name` is equal to `"page"`
                         and thus it is expected that there is a named `page` argument in the
                         URL referenced by `url_view_name`. This allows us to use pretty
                         pagination URLs such as `/page/1`
- **url_anchor** - The anchor to use in URLs. Defaults to `None`
- **extra_pager_classes** - A space separated list of CSS class names that will be added
                to the top level `<ul>` HTML element. This could be used to, as an
                example, add a class  to prevent the pager from showing up when
                printing.

**Usage**

Usage is basically the same as for bootstrap_paginate. The simplest usage is:

```
    {% bootstrap_pager page_obj %}
```

A somewhat more advanced usage might look like:

```
    {% bootstrap_pager page_obj previous_label="Newer Posts" next_label="Older Posts" url_view_name="post_archive_paginated" %}
```




%package help
Summary:	Development documents and examples for django-bootstrap-pagination
Provides:	python3-django-bootstrap-pagination-doc
%description help
[![PyPi version](https://img.shields.io/pypi/v/django-bootstrap-pagination.svg)](https://pypi.python.org/pypi/django-bootstrap-pagination)
[![PyPi downloads](https://img.shields.io/pypi/dm/django-bootstrap-pagination.svg)](https://pypi.python.org/pypi/django-bootstrap-pagination)
[![Build Status](https://travis-ci.org/jmcclell/django-bootstrap-pagination.png?branch=master)](https://travis-ci.org/jmcclell/django-bootstrap-pagination)


## Django Bootstrap Pagination

*Bootstrap Compatibility*

| Versions         | Bootstrap Versions  | Notes                                                  |
| -----------------| ------------------- | -------------------------------------------------------|
| < 1.1.0          | 2.x                 |                                                        |
| > 1.1.0, < 1.7.0 | 3.x                 |                                                        |
| >= 1.7.0         | 3.x, 4.x            | bootstrap_pager is only compatible with Bootstrap  3.x |


This application serves to make using Twitter's Bootstrap Pagination styles
work seamlessly with Django Page objects. By passing in a Page object and
one or more optional arguments, Bootstrap pagination bars and pagers can
be rendered with very little effort.

Compatible with Django **1.2+**

## Installation

### PIP

This will install the latest stable release from PyPi.

```
    pip install django-bootstrap-pagination
```

### Download

Download the latest stable distribution from:

http://pypi.python.org/pypi/django-bootstrap-pagination

Download the latest development version from:

github @ http://www.github.com/jmcclell/django-bootstrap-pagination

```
    setup.py install
```

## Usage

### Setup

Make sure you include bootstrap_pagination in your installed_apps list in settings.py:

```
    INSTALLED_APPS = (
        'bootstrap_pagination',
    )
```

Additionally, include the following snippet at the top of any template that makes use of
the pagination tags:

```
    {% load bootstrap_pagination %}
```

Finally, make sure that you have the request context processor enabled:

```
    # Django 1.8+
    TEMPLATES = [
        {
            # ...
            'OPTIONS': {
                context_processors': [
                    # ...
                    'django.template.context_processors.request',
                ]
            }
        }
    ]

    # Django < 1.8
    TEMPLATE_CONTEXT_PROCESSORS = {
        "django.core.context_processors.request",
    )
```

# bootstrap_paginate

**All Optional Arguments**

- **range** - Defines the maximum number of page links to show
- **show_prev_next** - Boolean. Defines whether or not to show the Previous and Next
                       links. (Accepts `"true"` or `"false"`)
- **previous_label** - The label to use for the Previous link
- **next_label** - The label to use for the Next link
- **show_first_last** - Boolean. Defines whether or not to show the First and Last links.
                       (Accepts `"true"` or `"false"`)
- **first_label** - The label to use for the First page link
- **last_label** - The label to use for the Last page link
- **show_index_range** - Boolean, defaults to "false". If "true" shows index range of items instead of page numbers in the paginator. For example, if paginator is configured for 50 items per page, show_index_range="true" will display [1-50, 51-100, **101-150**, 151-200, 201-250, etc.] rather than [1, 2, **3**, 4, 5, etc.].
- **url_view_name** - A named URL reference (such as one that might get passed into the URL
                      template tag) to use as the URL template. Must be resolvable by the
                      `reverse()` function. **If this option is not specified, the tag simply
                      uses a relative url such as `?page=1` which is fine in most situations**
- **url_param_name** - Determines the name of the `GET` parameter for the page number. The
                       default is `"page"`. If no **url_view_name** is defined, this string
                       is appended to the url as `?{{url_param_name}}=1`.
- **url_extra_args** - **Only valid when url_view_name is set.** Additional arguments to
                       pass into `reverse()` to resolve the URL.
- **url_extra_kwargs** - **Only valid when `url_view_name` is set.** Additional named
                         arguments to pass into `reverse()` to resolve the URL. Additionally,
                         the template tag will add an extra parameter to this for the
                         page, as it is assumed that if given a url_name, the page will
                         be a named variable in the URL regular expression. In this case,
                         the `url_param_name` continues to be the string used to represent
                         the name. That is, by default, `url_param_name` is equal to `page`
                         and thus it is expected that there is a named `page` argument in the
                         URL referenced by `url_view_name`. This allows us to use pretty
                         pagination URLs such as `/page/1`
- **extra_pagination_classes** - A space separated list of CSS class names that
                             will be added to the top level `<ul>` HTML element.
                             In particular, this can be utilized in Bootstrap 4
                             installations to add the appropriate alignment
                             classes from Flexbox utilities: eg:
                             `justify-content-center`


**Basic Usage**

The following will show a pagination bar with a link to every page, a previous link, and a next link:

```
    {% bootstrap_paginate page_obj %}
```

The following will show a pagination bar with at most 10 page links, a previous link, and a next link:

```
    {% bootstrap_paginate page_obj range=10 %}
```

The following will show a pagination bar with at most 10 page links, a first page link, and a last page link:

```
    {% bootstrap_paginate page_obj range=10 show_prev_next="false" show_first_last="true" %}
```

**Advanced Usage**

Given a url configured such as:

```python
    archive_index_view = ArchiveIndexView.as_view(
        date_field='date',
        paginate_by=10,
        allow_empty=True,
        queryset=MyModel.all(),
        template_name='example/archive.html'
    )

    urlpatterns = patterns(
        'example.views',
        url(r'^$', archive_index_view, name='archive_index'),
        url(r'^page/(?P<page>\d+)/$', archive_index_view,
            name='archive_index_paginated'))
```

We could simply use the basic usage (appending ?page=#) with the *archive_index* URL above,
as the *archive_index_view* class based generic view from django doesn't care how it gets
the page parameter. However, if we want pretty URLs, such as those defined in the
*archive_index_paginated* URL (ie: /page/1), we need to define the URL in our template tag:

```
    {% bootstrap_paginate page_obj url_view_name="archive_index_paginated" %}
```

Because we are using a default page parameter name of "page" and our URL requires no other
parameters, everything works as expected. If our URL required additional parameters, we
would pass them in using the optional arguments **url_extra_args** and **url_extra_kwargs**.
Likewise, if our page parameter had a different name, we would pass in a different
**url_param_name** argument to the template tag.

# bootstrap_pager

A much simpler implementation of the Bootstrap Pagination functionality is the Pager, which
simply provides a Previous and Next link.

**All Optional Arguments**

- **previous_label** - Defines the label for the Previous link
- **next_label** - Defines the label for the Next link
- **previous_title** - Defines the link title for the previous link
- **next_title** - Defines the link title for the next link
- **centered** - Boolean. Defines whether or not the links are centered. Defaults to false.
                 (Accepts "true" or "false")
- **url_view_name** - A named URL reference (such as one that might get passed into the URL
                      template tag) to use as the URL template. Must be resolvable by the
                      `reverse()` function. **If this option is not specified, the tag simply
                      uses a relative url such as `?page=1` which is fine in most situations**
- **url_param_name** - Determines the name of the `GET` parameter for the page number. Th
                       default is `"page"`. If no `url_view_name` is defined, this string
                       is appended to the url as `?{{url_param_name}}=1`.
- **url_extra_args** - **Only valid when `url_view_name` is set.** Additional arguments to
                       pass into `reverse()` to resolve the URL.
- **url_extra_kwargs** - **Only valid when `url_view_name` is set.** Additional named
                         arguments to pass into `reverse()` to resolve the URL. Additionally,
                         the template tag will add an extra parameter to this for the
                         page, as it is assumed that if given a url_name, the page will
                         be a named variable in the URL regular expression. In this case,
                         the `url_param_name` continues to be the string used to represent
                         the name. That is, by default, `url_param_name` is equal to `"page"`
                         and thus it is expected that there is a named `page` argument in the
                         URL referenced by `url_view_name`. This allows us to use pretty
                         pagination URLs such as `/page/1`
- **url_anchor** - The anchor to use in URLs. Defaults to `None`
- **extra_pager_classes** - A space separated list of CSS class names that will be added
                to the top level `<ul>` HTML element. This could be used to, as an
                example, add a class  to prevent the pager from showing up when
                printing.

**Usage**

Usage is basically the same as for bootstrap_paginate. The simplest usage is:

```
    {% bootstrap_pager page_obj %}
```

A somewhat more advanced usage might look like:

```
    {% bootstrap_pager page_obj previous_label="Newer Posts" next_label="Older Posts" url_view_name="post_archive_paginated" %}
```




%prep
%autosetup -n django-bootstrap-pagination-1.7.1

%build
%py3_build

%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
	find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
	find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
	find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
	find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
	find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .

%files -n python3-django-bootstrap-pagination -f filelist.lst
%dir %{python3_sitelib}/*

%files help -f doclist.lst
%{_docdir}/*

%changelog
* Tue Apr 25 2023 Python_Bot <Python_Bot@openeuler.org> - 1.7.1-1
- Package Spec generated