# packages

pkgId: 8d43852944a5940966c75f998f6b741949c27e6f532bbe03b57986070b2ba764
name: WalletWasabi
arch: src
version: 1.1.11.1
epoch: 0
release: 11.fc32
summary: An open-source, non-custodial, privacy-focused Bitcoin wallet
url: https://github.com/zkSNACKs/WalletWasabi
rpm_license: MIT
rpm_group: Applications/Financial
rpm_buildhost: qubes-chroot
location_href: packages/WalletWasabi-1.1.11.1-11.fc32.src.rpm
checksum_type: sha256
description:
  Wasabi is an open-source, non-custodial, privacy-focused Bitcoin wallet for Desktop, that implements trustless CoinJoin.


pkgId: cda66d7ad928d096410abbb296e6d2cde438dc443dbfa5c181903f58698c8897
name: airsonic
arch: noarch
version: 10.6.2
epoch: 0
release: 21.fc32
summary: A music media server
url: https://github.com/airsonic/airsonic
rpm_license: GPLv3
rpm_group: Applications/Multimedia
rpm_buildhost: qubes-chroot
rpm_sourcerpm: airsonic-10.6.2-21.fc32.src.rpm
location_href: packages/airsonic-10.6.2-21.fc32.noarch.rpm
checksum_type: sha256
description:
  Airsonic is a multimedia server that transcodes media and plays it back in a browser or in a mobile device.


pkgId: 3dc64b0d61f7687235c22aa26314307e9720c63e4ea16ea0c107bc841696a165
name: airsonic-advanced
arch: noarch
version: 11.0.0.20210210200712
epoch: 1
release: 13.fc32
summary: A music media server
url: https://github.com/airsonic-advanced/airsonic-advanced
rpm_license: GPLv3
rpm_group: Applications/Multimedia
rpm_buildhost: qubes-chroot
rpm_sourcerpm: airsonic-advanced-11.0.0.20210210200712-13.fc32.src.rpm
location_href: packages/airsonic-advanced-11.0.0.20210210200712-13.fc32.noarch.rpm
checksum_type: sha256
description:
  Airsonic is a multimedia server that transcodes media and plays it back in a browser or in a mobile device.
  Airsonic Advanced is the next generation of Airsonic.


pkgId: 23f4a9345001b2465ce18405fd2552201bc5912dc80daa38dd7cb9e8162c6718
name: alertmanager
arch: src
version: 0.18.0
epoch: 0
release: 1.fc32
summary: Prometheus Alertmanager.
url: https://github.com/prometheus/alertmanager
rpm_license: ASL 2.0
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
location_href: packages/alertmanager-0.18.0-1.fc32.src.rpm
checksum_type: sha256
description:
  The Alertmanager handles alerts sent by client applications such as the
  Prometheus server. It takes care of deduplicating, grouping, and routing them to
  the correct receiver integration such as email, PagerDuty, or OpsGenie. It also
  takes care of silencing and inhibition of alerts.


pkgId: 78caad00c17ca36afcd0ab4b2182ca558f707941a43c28d3f3b638b0beed06c8
name: cec-dbus-bridge
arch: src
version: 0.0.6
epoch: 0
release: 10.fc32
summary: A daemon to expose CEC functionality on the D-Bus session bus
url: https://github.com/Rudd-O/cec-dbus-bridge
rpm_license: GPL
rpm_group: System administration tools
rpm_buildhost: qubes-chroot
location_href: packages/cec-dbus-bridge-0.0.6-10.fc32.src.rpm
checksum_type: sha256
description:
  cec-dbus-bridge allows you to control devices connected via HDMI through
  the CEC functionality exposed over D-Bus by it.


pkgId: 2529dcf53d06e304627e592d7ce8681f207f89ac7b0e22e68e071d3eef607420
name: download-firefox-extension
arch: noarch
version: 0.0.7
epoch: 0
release: 8.fc32
summary: A helper to download Firefox extensions without the browser
url: http://github.com/Rudd-O/download-firefox-extension
rpm_license: GPLv2+
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: download-firefox-extension-0.0.7-8.fc32.src.rpm
location_href: packages/download-firefox-extension-0.0.7-8.fc32.noarch.rpm
checksum_type: sha256
description:
  Download Firefox extension
  ==========================

  This is a small program that, given the URL to a Firefox extension on the
  [Firefox Addons site](https://addons.firefox.org/), will download the extension
  and validate that the downloaded data matches the advertised cryptographic hash.

  Usage:

  ```
  download-firefox-extension https://addons.firefox.org/path/to/extensionpage/
  ```


pkgId: 580e03f14079b3423249fe6ad3410af0d6d5253c2927e5ea2de448417c51b6fb
name: ebpf_exporter
arch: src
version: 1.2.2.3
epoch: 0
release: 17.fc32
summary: Prometheus exporter for custom eBPF metrics
url: https://github.com/Rudd-O/ebpf_exporter
rpm_license: GPLv3+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
location_href: packages/ebpf_exporter-1.2.2.3-17.fc32.src.rpm
checksum_type: sha256
description:
  Prometheus exporter for custom eBPF metrics.

  Motivation of this exporter is to allow you to write eBPF code and export
  metrics that are not otherwise accessible from the Linux kernel.

  eBPF was described by Ingo Molnár as:

      One of the more interesting features in this cycle is the ability
      to attach eBPF programs (user-defined, sandboxed bytecode executed
      by the kernel) to kprobes. This allows user-defined instrumentation
      on a live kernel image that can never crash, hang or interfere with
      the kernel negatively.

  An easy way of thinking about this exporter is bcc tools as prometheus metrics.


pkgId: 3bf442d08ea24f2e1fbedb51413d6e0fef2736dace7d7efe1979718bac778ac2
name: fava
arch: noarch
version: 1.10
epoch: 0
release: 7.fc32
summary: Web interface for the accounting tool Beancount.
url: https://beancount.github.io/fava/
rpm_license: MIT
rpm_vendor: Jakob Schnitzer <mail@jakobschnitzer.de>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: fava-1.10-7.fc32.src.rpm
location_href: packages/fava-1.10-7.fc32.noarch.rpm
checksum_type: sha256
description:
  .. image:: https://badges.gitter.im/beancount/fava.svg
     :alt: Join the chat at https://gitter.im/beancount/fava
     :target: https://gitter.im/beancount/fava
  .. image:: https://img.shields.io/pypi/l/fava.svg
     :target: https://pypi.python.org/pypi/fava
  .. image:: https://img.shields.io/pypi/v/fava.svg
     :target: https://pypi.python.org/pypi/fava
  .. image:: https://img.shields.io/travis/beancount/fava.svg
     :target: https://travis-ci.org/beancount/fava?branch=master

  Fava is a web interface for the double-entry bookkeeping software `Beancount
  <http://furius.ca/beancount/>`__ with a focus on features and usability.

  Check out the online `demo <https://fava.pythonanywhere.com>`__ and learn more
  about Fava on the `website <https://beancount.github.io/fava/>`__.

  The `Getting Started
  <https://beancount.github.io/fava/usage.html>`__ guide details the installation
  and how to get started with Beancount.  If you are already familiar with
  Beancount, you can get started with Fava::

      pip3 install fava
      fava ledger.beancount

  and visit the web interface at `http://localhost:5000
  <http://localhost:5000>`__.

  If you want to hack on Fava or run a development version, see the
  `Development <https://beancount.github.io/fava/development.html>`__ page on the
  website for details. Contributions are very welcome!

  .. image:: https://i.imgbox.com/rfb9I7Zw.png
      :alt: Fava Screenshot
      :width: 100%
      :align: center
      :target: https://fava.pythonanywhere.com


pkgId: e13baf7fd77534d01c65df8003ae6c8114e2f7412be9c0eba4ec1da16e19c185
name: git-remote-qubes
arch: noarch
version: 0.0.11
epoch: 0
release: 1.fc32
summary: Inter-VM git push and pull for Qubes OS AppVMs and StandaloneVMs
url: https://github.com/Rudd-O/git-remote-qubes
rpm_license: GPLv3+
rpm_group: Unspecified
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: git-remote-qubes-0.0.11-1.fc32.src.rpm
location_href: packages/git-remote-qubes-0.0.11-1.fc32.noarch.rpm
checksum_type: sha256
description:
  This package lets you setup Git servers on your Qubes OS VMs.
  You are meant to install this package on TemplateVMs that are the templates
  for AppVMs where you want to either serve git repos from, or push/pull git
  repos from, as well as StandaloneVMs where you wish to do the same things.


pkgId: a5f8f24e0ae38fd274d35ba335fd7d9159981e4cd8d8a9d53d5e4c9ab11f51a6
name: git-remote-qubes-dom0
arch: noarch
version: 0.0.11
epoch: 0
release: 1.fc32
summary: Policy package for Qubes OS dom0s that arbitrates git-remote-qubes
url: https://github.com/Rudd-O/git-remote-qubes
rpm_license: GPLv3+
rpm_group: Unspecified
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: git-remote-qubes-0.0.11-1.fc32.src.rpm
location_href: packages/git-remote-qubes-dom0-0.0.11-1.fc32.noarch.rpm
checksum_type: sha256
description:
  This package contains the Qubes OS execution policy for the git-remote-qubes package.
  You are meant to install this package on the dom0 of the machine where you
  have VMs that have the git-remote-qubes package installed.


pkgId: 4505c5d6cddad8d2f124a1f4b5ef24d3030e9aa571327ad3bd2991d26dc5ea54
name: kodi-wol-starter
arch: noarch
version: 0.0.3
epoch: 0
release: 3.fc32
summary: A demo client for wol-monitor that starts Kodi when a WOL packet is received.
url: https://github.com/Rudd-O/wol-monitor
rpm_license: GPLv2+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
rpm_sourcerpm: wol-monitor-0.0.3-3.fc32.src.rpm
location_href: packages/kodi-wol-starter-0.0.3-3.fc32.noarch.rpm
checksum_type: sha256
description:
  This is a demo client for wol-monitor that starts Kodi (if it is not running)
  when a Wake-on-LAN packet is received.  It is set to autostart in your user
  session when you log into your desktop.


pkgId: e83bf973428ef331a592859f970f061eee47f74bee37d6056adef9a258ac0a36
name: ledger2beancount
arch: src
version: 1.8.0.1
epoch: 0
release: 8.fc32
summary: Ledger to Beancount text-based converter
url: https://github.com/zacchiro/ledger2beancount
rpm_license: GPLv3
rpm_group: Applications/Financial
rpm_buildhost: qubes-chroot
location_href: packages/ledger2beancount-1.8.0.1-8.fc32.src.rpm
checksum_type: sha256
description:
  A script to automatically convert Ledger-based textual ledgers to Beancount ones.

  Conversion is based on (concrete) syntax, so that information that is not meaningful for accounting reasons but still valuable (e.g., comments, formatting, etc.) can be preserved.


pkgId: 3951c2ccc619fb67bb22a9839d6ff99a7d8b6c47d16210f963d6b7c0c4e134b3
name: libnvpair1
arch: x86_64
version: 0.8.0
epoch: 0
release: 0.132.80437a04d.fc32
summary: Solaris name-value library for Linux
url: https://zfsonlinux.org/
rpm_license: CDDL
rpm_group: System Environment/Kernel
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-0.8.0-0.132.80437a04d.fc32.src.rpm
location_href: packages/libnvpair1-0.8.0-0.132.80437a04d.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package contains routines for packing and unpacking name-value
  pairs.  This functionality is used to portably transport data across
  process boundaries, between kernel and user space, and can be used
  to write self describing data structures on disk.


pkgId: 8cbf93007bacdb449f5d8f0192d9ddbcd8ee71d04547366890b2a07b60d79f18
name: libnvpair1-debuginfo
arch: x86_64
version: 0.8.0
epoch: 0
release: 0.132.80437a04d.fc32
summary: Debug information for package libnvpair1
url: https://zfsonlinux.org/
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-0.8.0-0.132.80437a04d.fc32.src.rpm
location_href: packages/libnvpair1-debuginfo-0.8.0-0.132.80437a04d.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package libnvpair1.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: 563669a7d57da9a25b817f893f7fea98ccdc8b31b9af1d8a3bc551de548edd7e
name: libnvpair3-debuginfo
arch: x86_64
version: 2.0.0
epoch: 0
release: 0.142.38686cb9a.fc32
summary: Debug information for package libnvpair3
url: https://github.com/openzfs/zfs
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-2.0.0-0.142.38686cb9a.fc32.src.rpm
location_href: packages/libnvpair3-debuginfo-2.0.0-0.142.38686cb9a.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package libnvpair3.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: 020ae89d1cb717b87761329600572342edfbe6ef462dd317492dde84cacd98d8
name: libuutil1
arch: x86_64
version: 0.8.0
epoch: 0
release: 0.132.80437a04d.fc32
summary: Solaris userland utility library for Linux
url: https://zfsonlinux.org/
rpm_license: CDDL
rpm_group: System Environment/Kernel
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-0.8.0-0.132.80437a04d.fc32.src.rpm
location_href: packages/libuutil1-0.8.0-0.132.80437a04d.fc32.x86_64.rpm
checksum_type: sha256
description:
  This library provides a variety of compatibility functions for ZFS on Linux:
   * libspl: The Solaris Porting Layer userland library, which provides APIs
     that make it possible to run Solaris user code in a Linux environment
     with relatively minimal modification.
   * libavl: The Adelson-Velskii Landis balanced binary tree manipulation
     library.
   * libefi: The Extensible Firmware Interface library for GUID disk
     partitioning.
   * libshare: NFS, SMB, and iSCSI service integration for ZFS.


pkgId: 96eee06029620f0c7946c28e96554d5e1b603592831d9ccce054b3100b9d11c4
name: libuutil1-debuginfo
arch: x86_64
version: 0.8.0
epoch: 0
release: 0.132.80437a04d.fc32
summary: Debug information for package libuutil1
url: https://zfsonlinux.org/
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-0.8.0-0.132.80437a04d.fc32.src.rpm
location_href: packages/libuutil1-debuginfo-0.8.0-0.132.80437a04d.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package libuutil1.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: bcf7b5058672bd92ed1b9f5d4cf4865af6fb7484d7b54038527714222a227e2e
name: libuutil3
arch: x86_64
version: 2.0.0
epoch: 0
release: 0.142.38686cb9a.fc32
summary: Solaris userland utility library for Linux
url: https://github.com/openzfs/zfs
rpm_license: CDDL
rpm_group: System Environment/Kernel
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-2.0.0-0.142.38686cb9a.fc32.src.rpm
location_href: packages/libuutil3-2.0.0-0.142.38686cb9a.fc32.x86_64.rpm
checksum_type: sha256
description:
  This library provides a variety of compatibility functions for OpenZFS:
   * libspl: The Solaris Porting Layer userland library, which provides APIs
     that make it possible to run Solaris user code in a Linux environment
     with relatively minimal modification.
   * libavl: The Adelson-Velskii Landis balanced binary tree manipulation
     library.
   * libefi: The Extensible Firmware Interface library for GUID disk
     partitioning.
   * libshare: NFS, SMB, and iSCSI service integration for ZFS.


pkgId: bfc47767af3699a445c60f4fc7565b85240dadf09390eeb56bc5dcf12b9061eb
name: libuutil3-debuginfo
arch: x86_64
version: 2.0.0
epoch: 0
release: 0.142.38686cb9a.fc32
summary: Debug information for package libuutil3
url: https://github.com/openzfs/zfs
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-2.0.0-0.142.38686cb9a.fc32.src.rpm
location_href: packages/libuutil3-debuginfo-2.0.0-0.142.38686cb9a.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package libuutil3.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: 059690c0298f7afc6122d623489fcba0357a5234508f573aec1cef5e1c945fa9
name: libzfs2-debuginfo
arch: x86_64
version: 0.8.0
epoch: 0
release: 0.132.80437a04d.fc32
summary: Debug information for package libzfs2
url: https://zfsonlinux.org/
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-0.8.0-0.132.80437a04d.fc32.src.rpm
location_href: packages/libzfs2-debuginfo-0.8.0-0.132.80437a04d.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package libzfs2.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: b75b0f8b1428eb23dc9f4b1a85d63499650d575cad946fbfe08208faa5a60204
name: libzfs2-devel
arch: x86_64
version: 0.8.0
epoch: 0
release: 0.132.80437a04d.fc32
summary: Development headers
url: https://zfsonlinux.org/
rpm_license: CDDL
rpm_group: System Environment/Kernel
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-0.8.0-0.132.80437a04d.fc32.src.rpm
location_href: packages/libzfs2-devel-0.8.0-0.132.80437a04d.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package contains the header files needed for building additional
  applications against the ZFS libraries.


pkgId: d5ccb193501e8a03ad9b1d20b2367462e3145dae5d7390ccae04ac7fb7718e09
name: libzfs4-debuginfo
arch: x86_64
version: 2.0.0
epoch: 0
release: 0.142.38686cb9a.fc32
summary: Debug information for package libzfs4
url: https://github.com/openzfs/zfs
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-2.0.0-0.142.38686cb9a.fc32.src.rpm
location_href: packages/libzfs4-debuginfo-2.0.0-0.142.38686cb9a.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package libzfs4.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: 839c45c9f6f47b713a36dc6ba922b208faf4e75506cb4ad2fb8f0ba3fa1876cd
name: libzfs5-debuginfo
arch: x86_64
version: 2.1.99
epoch: 0
release: 0.35.8d2ca3471.fc32
summary: Debug information for package libzfs5
url: https://github.com/openzfs/zfs
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: jenkins-chroot.local
rpm_sourcerpm: zfs-2.1.99-0.35.8d2ca3471.fc32.src.rpm
location_href: packages/libzfs5-debuginfo-2.1.99-0.35.8d2ca3471.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package libzfs5.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: 6c0adfc6b791e9e25b88bbb69bcebcf67e5774603573c45df3b4647118f7ae44
name: libzpool2-debuginfo
arch: x86_64
version: 0.8.0
epoch: 0
release: 0.132.80437a04d.fc32
summary: Debug information for package libzpool2
url: https://zfsonlinux.org/
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-0.8.0-0.132.80437a04d.fc32.src.rpm
location_href: packages/libzpool2-debuginfo-0.8.0-0.132.80437a04d.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package libzpool2.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: 92fcfefdcece55ec4619e6b7ab924510a92cba6d8066ab2564dd3ae8383a4758
name: libzpool4-debuginfo
arch: x86_64
version: 2.0.0
epoch: 0
release: 0.142.38686cb9a.fc32
summary: Debug information for package libzpool4
url: https://github.com/openzfs/zfs
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-2.0.0-0.142.38686cb9a.fc32.src.rpm
location_href: packages/libzpool4-debuginfo-2.0.0-0.142.38686cb9a.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package libzpool4.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: 35149ef30d07b8c15263aa606c63a5c9a6c4b3867f3d950b59f0b09d227569a5
name: libzpool5-debuginfo
arch: x86_64
version: 2.1.99
epoch: 0
release: 0.35.8d2ca3471.fc32
summary: Debug information for package libzpool5
url: https://github.com/openzfs/zfs
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: jenkins-chroot.local
rpm_sourcerpm: zfs-2.1.99-0.35.8d2ca3471.fc32.src.rpm
location_href: packages/libzpool5-debuginfo-2.1.99-0.35.8d2ca3471.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package libzpool5.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: c70f8036a1753d6e1f87d31b20985f4df2c58bca0cb9bae61e020407189c97f3
name: musictoolbox
arch: noarch
version: 0.0.45
epoch: 0
release: 29.fc32
summary: A set of utilities to help you groom your music collection
url: http://github.com/Rudd-O/musictoolbox
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: musictoolbox-0.0.45-29.fc32.src.rpm
location_href: packages/musictoolbox-0.0.45-29.fc32.noarch.rpm
checksum_type: sha256
description:
  Music toolbox
  =============

  This is a small toolbox of utilities written in Python 2 that help users groom their music collection.

  What's in the box
  -----------------

  `syncplaylists` takes a number of file lists / playlists in the command line,
  and a destination directory, then synchronizes all the songs in the playlists
  to the destination directory, with optional modifications to the files and their
  names as they are copied to the destination directory.  `syncplaylists` preserves
  your music collection's directory structure.

  `syncplaylists` requires a simple INI file in your home directory (name it
  `.syncplaylists.ini`) which must say how you want things to be transcoded:
  ::

      
      [transcoding]
      mp3=copy
      m4a=copy
      ogg=copy
      flac=copy
      *=mp3
      opus=copy

  Once you've created the INI file, here's the quickstart version of how you
  actually *use* the tool:

  ```
  [user@laptop ~/Music]$ syncplaylists -vd Playlists/*.m3u /mnt/usbdrive/Music/
  ```

  That will copy all songs listed in all M3U playlists within your
  `~/Music/Playlists` folder directly into `/mnt/usbdrive/Music`, preserving
  the directory structure you have.

  Run `syncplaylists --help` or see `get_parser()` in file `synccli.py` for more
  information.

  `genplaylist` generates playlists.  Run `genplaylist --help` or see
  `get_parser()` in file `genplaylist` for more information.

  Requirements
  ------------

  This is a non-exhaustive list of requirements for most of these utilities to work:

    - python-setuptools
    - ffmpeg
    - python-mutagen
    - mp3gain
    - madplay
    - mplayer
    - mppenc
    - vorbis-tools
    - flac


pkgId: eeb378c1d698f36fbfb2d7f760cbd05d460a3f7cc87728d575c1e057c0c0d7c6
name: needs-restart
arch: noarch
version: 0.0.9
epoch: 0
release: 1.fc32
summary: A program to discover services that need restarting
url: http://github.com/Rudd-O/needs-restart
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: needs-restart-0.0.9-1.fc32.src.rpm
location_href: packages/needs-restart-0.0.9-1.fc32.noarch.rpm
checksum_type: sha256
description:
  The needs-restart program
  =========================

  This is a brief program that helps you detect which services on your
  system need to be restarted after an upgrade or redeploy of your
  software.

  Here is some example output:

      [root@machine root]# needs-restart
      * unit: (no unit)
        * PID: 1
          command: /usr/lib/systemd/systemd --switched-root --system...
          * /usr/lib64/libpcre.so.1.2.5 changed inode from 5305 to 5364
      * unit: systemd-journald.service
        * PID: 257
          command: /usr/lib/systemd/systemd-journald
          * /usr/lib64/libpcre.so.1.2.5 changed inode from 5305 to 5364
      * unit: systemd-udevd.service
        * PID: 281
          command: /usr/lib/systemd/systemd-udevd
          * /usr/lib64/libpcre.so.1.2.5 changed inode from 5305 to 5364
      * unit: auditd.service
        * PID: 318
          command: /sbin/auditd -n
          * /usr/lib64/libpcre.so.1.2.5 changed inode from 5305 to 5364
      * unit: icecast.service
        * PID: 336
          command: /usr/bin/icecast -c /etc/icecast.xml
          * /usr/lib64/libpcre.so.1.2.5 changed inode from 5305 to 5364
          * /usr/lib64/libnss3.so changed inode from 3183 to 4236
          * /usr/lib64/libsmime3.so changed inode from 17534 to 4257
          * /usr/lib64/libssl3.so changed inode from 17535 to 4259
      * unit: systemd-logind.service
        * PID: 340
          command: /usr/lib/systemd/systemd-logind
          * /usr/lib64/libpcre.so.1.2.5 changed inode from 5305 to 5364
      * unit: dbus.service
        * PID: 343
          command: /usr/bin/dbus-daemon --system --address=systemd: ...
          * /usr/lib64/libelf-0.163.so changed inode from 109 to 6302
          * /usr/lib64/libpcre.so.1.2.5 changed inode from 5305 to 5364
          * /usr/lib64/libdw-0.163.so changed inode from 17296 to 17286

  Here is some example output in bare mode (`-b`):

      [root@machine root]# needs-restart -b
      systemd-journald.service
      systemd-udevd.service
      auditd.service
      icecast.service
      systemd-logind.service
      dbus.service

  Features and options
  --------------------

  The online help explains:

      [user@machine needs-restart]$ ./needs-restart --help
      usage: needs-restart [-h] [-b] [-s] [-i PATH_PREFIX]

      Show services in need of restart and processes keeping files open that were
      deleted or updated since they were opened by those processes.

      optional arguments:
        -h, --help      show this help message and exit
        -b              bare form – only list the units that need restarting
        -s              only list system units – ignore user and session ones
        -i PATH_PREFIX  ignore deleted / modified mmap()ed path(s) starting with
                        this prefix; you can specify this parameter multiple times

  Building and installing
  -----------------------

  You can run this program directly from the directory you cloned it into.

  You can also install it as an RPM.  Simply type the following command
  in the directory you cloned it into:

      python setup.py bdist_rpm

  Source RPM and installable architecture-independent RPM will appear in
  `dist/`.  You can install the architecture-independent RPM on your system now.


pkgId: 361388becb10cc02584fe023138123e23a5904aa27c7e476f4807f5eb93244ef
name: node_exporter
arch: aarch64
version: 0.18.1
epoch: 0
release: 29.fc32
summary: Prometheus exporter for machine metrics, written in Go with pluggable metric collectors.
url: https://github.com/prometheus/node_exporter
rpm_license: ASL 2.0
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
rpm_sourcerpm: node_exporter-0.18.1-29.fc32.src.rpm
location_href: packages/node_exporter-0.18.1-29.fc32.aarch64.rpm
checksum_type: sha256
description:
  Prometheus exporter for hardware and OS metrics exposed by *NIX kernels,
  written in Go with pluggable metric collectors.


pkgId: cd1eb81c24cef76855d35b109be0724c20257a61a3010dd5ba418d3ae75793d0
name: organizer
arch: noarch
version: 0.0.12
epoch: 0
release: 1.fc32
summary: A tool to assist in organizing media files
url: http://github.com/Rudd-O/organizer
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: organizer-0.0.12-1.fc32.src.rpm
location_href: packages/organizer-0.0.12-1.fc32.noarch.rpm
checksum_type: sha256
description:
  Organizer
  =========

  The organizer will help you sort your media files in folders easily
  and conveniently.

  With this program installed on your home computer, all you need to do is
  simply start your file manager, select the files to organize with a right
  click, then select Organize media files from the Open with... menu.  You
  can also run the program `organizer` from the command line, specifying
  the paths to the files you want to organize as arguments to the program.

  Optionally, if the program `takeown` is installed, the organizer will
  automatically attempt to take ownership of the files prior to organizing
  them.  This saves you an extra work step.


pkgId: e7df20da6cd3d730301525f824143364c6fa496ffc9ecec888bf850e48aefb49
name: perl-Config-Onion
arch: noarch
version: 1.007
epoch: 0
release: 12.fc32
summary: Layered configuration, because configs are like ogres
url: http://search.cpan.org/dist/Config-Onion/
rpm_license: GPL+ or Artistic
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: perl-Config-Onion-1.007-12.fc32.src.rpm
location_href: packages/perl-Config-Onion-1.007-12.fc32.noarch.rpm
checksum_type: sha256
description:
  All too often, configuration is not a universal or one-time thing, yet
  most configuration-handling treats it as such. Perhaps you can only load
  one config file. If you can load more than one, you often have to load
  all of them at the same time or each is stored completely independently,
  preventing one from being able to override another. Config::Onion
  changes that.


pkgId: dc959c358ed8631c3d386c3f115b0f5c3be7be68d1ab95e09c70271671dae93b
name: perl-Safe-Hole
arch: src
version: 0.14
epoch: 0
release: 15.fc32
summary: Make a hole to the original main compartment in the Safe compartment
url: http://search.cpan.org/dist/Safe-Hole/
rpm_license: GPL+ or Artistic
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
location_href: packages/perl-Safe-Hole-0.14-15.fc32.src.rpm
checksum_type: sha256
description:
  We can call outside defined subroutines from the Safe compartment using
  share(), or can call methods through the object that is copied into the
  Safe compartment using varglob(). But that subroutines or methods are
  executed in the Safe compartment too, so they cannot call another
  subroutines that are dinamically qualified with the package name such as
  class methods nor can they compile code that uses opcodes that are
  forbidden within the compartment.


pkgId: 92ad57cc00ba14cb058f07764fb87a57618a795d62a671201905c4971051ba5b
name: perl-Safe-Hole-debuginfo
arch: x86_64
version: 0.14
epoch: 0
release: 15.fc32
summary: Debug information for package perl-Safe-Hole
url: http://search.cpan.org/dist/Safe-Hole/
rpm_license: GPL+ or Artistic
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: perl-Safe-Hole-0.14-15.fc32.src.rpm
location_href: packages/perl-Safe-Hole-debuginfo-0.14-15.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package perl-Safe-Hole.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: c744a93306e5083c9529a2ef6f4eeb7137e52453cec0af8f37792bf18d2162d0
name: perl-Safe-Hole-debugsource
arch: x86_64
version: 0.14
epoch: 0
release: 15.fc32
summary: Debug sources for package perl-Safe-Hole
url: http://search.cpan.org/dist/Safe-Hole/
rpm_license: GPL+ or Artistic
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: perl-Safe-Hole-0.14-15.fc32.src.rpm
location_href: packages/perl-Safe-Hole-debugsource-0.14-15.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug sources for package perl-Safe-Hole.
  Debug sources are useful when developing applications that use this
  package or when debugging this package.


pkgId: c577f8dac71282fc7a0af93a1b8741667224cc6b94c7899e0de4dd24e6f2cdb6
name: perl-String-Interpolate
arch: noarch
version: 0.32
epoch: 0
release: 30.fc32
summary: Wrapper for builtin the Perl interpolation engine
url: http://search.cpan.org/dist/String-Interpolate/
rpm_license: GPL+ or Artistic
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: perl-String-Interpolate-0.32-30.fc32.src.rpm
location_href: packages/perl-String-Interpolate-0.32-30.fc32.noarch.rpm
checksum_type: sha256
description:
  String::Interpolate provides a neat interface to the solution to that
  perenial Perl problem - how to invoke the Perl string interpolation engine
  on a string contained in a scalar variable.


pkgId: 9a4719f6e57e7df8b77dce7a5e16126edd07453f43b19cf814ffa3a8544f38b5
name: prometheus-qubes-proxy
arch: src
version: 0.0.3.1
epoch: 0
release: 12.fc32
summary: Proxy the outside world into Prometheus exporters running on your Qubes OS VMs
url: https://github.com/Rudd-O/prometheus-qubes-proxy
rpm_license: GPLv3+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
location_href: packages/prometheus-qubes-proxy-0.0.3.1-12.fc32.src.rpm
checksum_type: sha256
description:
  This package lets your Prometheus server contact Prometheus exporters running
  in your Qubes OS VMs.

  Install this package on your VM / VM template in order to allow the outside world
  to contact Prometheus Qubes proxy.  Then install the prometheus-qubes-proxy-service package on
  the VM / VM templates where you'll run the exporter you wish to scrape.


pkgId: 0ecb175950d2d270816bc03c66a6378e17a2897880e88e4d46603ee2fe62295a
name: prometheus-qubes-proxy-dom0
arch: x86_64
version: 0.0.3.1
epoch: 0
release: 12.fc32
summary: This component installs the default-deny proxy policy to dom0.
url: https://github.com/Rudd-O/prometheus-qubes-proxy
rpm_license: GPLv3+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
rpm_sourcerpm: prometheus-qubes-proxy-0.0.3.1-12.fc32.src.rpm
location_href: packages/prometheus-qubes-proxy-dom0-0.0.3.1-12.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package installs the default deny-all policy for ruddo.PrometheusProxy to
  your dom0.

  Install this package on your dom0 and then adjust the policy file to suit your
  specific requirements.


pkgId: 5f8bbaf71d832d711c1d528b9254f5704983c89f52a2c12b341bf549a1785b50
name: prometheus-qubes-proxy-service
arch: x86_64
version: 0.0.3.1
epoch: 0
release: 12.fc32
summary: This component lets the Prometheus Qubes proxy talk to a VM.
url: https://github.com/Rudd-O/prometheus-qubes-proxy
rpm_license: GPLv3+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
rpm_sourcerpm: prometheus-qubes-proxy-0.0.3.1-12.fc32.src.rpm
location_href: packages/prometheus-qubes-proxy-service-0.0.3.1-12.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package installs the necessary component for Prometheus Qubes proxy to talk
  to a Prometheus exporter run in a VM.

  Install this package on your VM / VM template in order to allow Prometheus Qubes
  proxy to talk to any exporters running on said VM / on any VMs derived from that
  VM template.

  Requires: curl
  Requires: bash


pkgId: 6ad6718c3232d26cd11a602335ddc2ca96cc41e167b0eee2ddf61361fa49782f
name: prometheus2
arch: src
version: 2.17.2
epoch: 0
release: 1.fc32
summary: The Prometheus 2.x monitoring system and time series database.
url: https://prometheus.io
rpm_license: ASL 2.0
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
location_href: packages/prometheus2-2.17.2-1.fc32.src.rpm
checksum_type: sha256
description:
  Prometheus is a systems and service monitoring system. It collects metrics from
  configured targets at given intervals, evaluates rule expressions, displays the
  results, and can trigger alerts if some condition is observed to be true.


pkgId: 049671c74028498b73eb303ce376ff28c746b68fb83465102561afa8a9c2f6cc
name: pypipackage-to-srpm
arch: noarch
version: 0.0.23
epoch: 0
release: 29.fc32
summary: Automate the creation of source and binary RPM packages out of source packages downloaded from PyPI
url: http://github.com/Rudd-O/pypipackage-to-srpm
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: pypipackage-to-srpm-0.0.23-29.fc32.src.rpm
location_href: packages/pypipackage-to-srpm-0.0.23-29.fc32.noarch.rpm
checksum_type: sha256
description:
  Formula for turning Python PyPI packages into sane RPMs.



  Your Fedora or CentOS system where you'll run this will need these
  packages installed before using this program:

  * `python-mock`


pkgId: 752fe4713ba9ae5e3e94e6c6af75c31cadecb502806b349e9848b1558c8a104f
name: python2-jsonrpclib-pelix
arch: noarch
version: 0.4.0
epoch: 0
release: 7.fc32
url: http://github.com/tcalmant/jsonrpclib/
rpm_license: Apache License 2.0
rpm_vendor: Thomas Calmant <thomas.calmant+github@gmail.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python2-jsonrpclib-pelix-0.4.0-7.fc32.src.rpm
location_href: packages/python2-jsonrpclib-pelix-0.4.0-7.fc32.noarch.rpm
checksum_type: sha256
summary:
  This project is an implementation of the JSON-RPC v2.0 specification (backwards-compatible) as a client library, for Python 2.7 and Python 3. This version is a fork of jsonrpclib by Josh Marshall, made to be also usable with Pelix/iPOPO remote services.

description:
  [![Latest Version](https://img.shields.io/pypi/v/jsonrpclib-pelix.svg)](https://pypi.python.org/pypi/jsonrpclib-pelix/)
  [![License](https://img.shields.io/pypi/l/jsonrpclib-pelix.svg)](https://pypi.python.org/pypi/jsonrpclib-pelix/)
  [![Travis-CI status](https://travis-ci.org/tcalmant/jsonrpclib.svg?branch=master)](https://travis-ci.org/tcalmant/jsonrpclib)
  [![Coveralls status](https://coveralls.io/repos/tcalmant/jsonrpclib/badge.svg?branch=master)](https://coveralls.io/r/tcalmant/jsonrpclib?branch=master)

  This library is an implementation of the JSON-RPC specification.
  It supports both the original 1.0 specification, as well as the new
  (proposed) 2.0 specification, which includes batch submission, keyword
  arguments, etc.

  This library is licensed under the terms of the
  [Apache Software License 2.0](<http://www.apache.org/licenses/LICENSE-2.0.html>).




  This is a patched version of the original `jsonrpclib` project by Josh Marshall,
  available at
  [joshmarshall/jsonrpclib](<https://github.com/joshmarshall/jsonrpclib>).

  The suffix *-pelix* only indicates that this version works with Pelix
  Remote Services, but it is **not** a Pelix specific implementation.

  * This version adds support for Python 3, staying compatible with Python 2.7.
    The support for Python 2.6 has been dropped, as it was becoming to hard to
    maintain.
  * It is now possible to use the `dispatch_method` argument while extending the
    `SimpleJSONRPCDispatcher`, to use a custom dispatcher.
    This allows to use this package by Pelix Remote Services.
  * It can use thread pools to control the number of threads spawned to handle
    notification requests and clients connections.
  * The modifications added in other forks of this project have been added:
      * From [drdaeman/jsonrpclib](<https://github.com/drdaeman/jsonrpclib>):
        * Improved JSON-RPC 1.0 support
        * Less strict error response handling
      * From [tuomassalo/jsonrpclib](<https://github.com/tuomassalo/jsonrpclib>):
        * In case of a non-predefined error, raise an AppError and give access
          to *error.data*
      * From [dejw/jsonrpclib](<https://github.com/dejw/jsonrpclib>):
        * Custom headers can be sent with request and associated tests
  * Since version 0.4, this package added back the support of Unix sockets.
  * This package cannot be installed with the original `jsonrpclib`, as it uses
    the same name.



  This library implements the JSON-RPC 2.0 proposed specification in pure Python.
  It is designed to be as compatible with the syntax of `xmlrpclib` as possible
  (it extends where possible), so that projects using `xmlrpclib` could easily be
  modified to use JSON and experiment with the differences.

  It is backwards-compatible with the 1.0 specification, and supports all of the
  new proposed features of 2.0, including:

  - Batch submission (via the `MultiCall` class)
  - Keyword arguments
  - Notifications (both in a batch and 'normal')
  - Class translation using the `__jsonclass__` key.

  A `SimpleJSONRPCServer` class has been added. It is intended to emulate the
  `SimpleXMLRPCServer` from the default Python distribution.



  This library supports `cjson` and `simplejson`, and looks for the parsers in
  that order (searching first for `cjson`, then for the *built-in* `json` in 2.7+,
  and then the `simplejson` external library).
  One of these must be installed to use this library, although if you have a
  standard distribution of 2.7+, you should already have one.
  Keep in mind that `cjson` is supposed to be the quickest, I believe, so if you
  are going for full-on optimization you may want to pick it up.



  You can install this from PyPI with one of the following commands (`sudo`
  might be required):

  ```

  pip install jsonrpclib-pelix


  pip install --user jsonrpclib-pelix
  ```

  Alternatively, you can download the source from the GitHub repository at
  [tcalmant/jsonrpclib](http://github.com/tcalmant/jsonrpclib) and manually
  install it with the following commands:

  ```
  git clone git://github.com/tcalmant/jsonrpclib.git
  cd jsonrpclib
  python2 setup.py install
  ```



  This is identical in usage (or should be) to the `SimpleXMLRPCServer` in the
  Python standard library.
  Some of the differences in features are that it obviously supports notification,
  batch calls, class translation (if left on), etc.

  **Note:** The import line is slightly different from the regular
  `SimpleXMLRPCServer`, since the `SimpleJSONRPCServer` is provided by th
  `jsonrpclib` library.

  ```python
  from jsonrpclib.SimpleJSONRPCServer import SimpleJSONRPCServer

  server = SimpleJSONRPCServer(('localhost', 8080))
  server.register_function(pow)
  server.register_function(lambda x,y: x+y, 'add')
  server.register_function(lambda x: x, 'ping')
  server.serve_forever()
  ```

  To start protect the server with SSL, use the following snippet:

  ```python
  from jsonrpclib.SimpleJSONRPCServer import SimpleJSONRPCServer
  import ssl


  server = SimpleJSONRPCServer(('localhost', 8080), bind_and_activate=False)
  server.socket = ssl.wrap_socket(server.socket, certfile='server.pem',
                                  server_side=True)
  server.server_bind()
  server.server_activate()



  server.serve_forever()
  ```



  By default, notification calls are handled in the request handling thread.
  It is possible to use a thread pool to handle them, by giving it to the server
  using the `set_notification_pool()` method:

  ```python
  from jsonrpclib.SimpleJSONRPCServer import SimpleJSONRPCServer
  from jsonrpclib.threadpool import ThreadPool


  pool = ThreadPool(max_threads=10, min_threads=0)


  pool.start()


  server = SimpleJSONRPCServer(('localhost', 8080))
  server.set_notification_pool(pool)


  server.register_function(pow)
  server.register_function(lambda x,y: x+y, 'add')
  server.register_function(lambda x: x, 'ping')

  try:
      server.serve_forever()
  finally:
      
      pool.stop()
      server.set_notification_pool(None)
  ```



  It is also possible to use a thread pool to handle clients requests, using the
  `PooledJSONRPCServer` class.
  By default, this class uses pool of 0 to 30 threads.
  A custom pool can be given with the `thread_pool` parameter of the class
  constructor.

  The notification pool and the request pool are different: by default, a server
  with a request pool doesn't have a notification pool.

  ```python
  from jsonrpclib.SimpleJSONRPCServer import PooledJSONRPCServer
  from jsonrpclib.threadpool import ThreadPool


  nofif_pool = ThreadPool(max_threads=10, min_threads=0)
  request_pool = ThreadPool(max_threads=50, min_threads=10)


  nofif_pool.start()
  request_pool.start()


  server = PooledJSONRPCServer(('localhost', 8080), thread_pool=request_pool)
  server.set_notification_pool(nofif_pool)


  server.register_function(pow)
  server.register_function(lambda x,y: x+y, 'add')
  server.register_function(lambda x: x, 'ping')

  try:
      server.serve_forever()
  finally:
      
      request_pool.stop()
      nofif_pool.stop()
      server.set_notification_pool(None)
  ```



  To start a server listening on a Unix socket, you will have to use the
  following snippet:

  ```python
  from jsonrpclib.SimpleJSONRPCServer import SimpleJSONRPCServer
  import os
  import socket


  socket_name = "/tmp/my_socket.socket"


  if os.path.exists(socket_name):
     os.remove(socket_name)

  try:
     
     
     
     srv = SimpleJSONRPCServer(socket_name, address_family=socket.AF_UNIX)

     
     
     srv.serve_forever()
  except KeyboardInterrupt:
     
     srv.shutdown()
     srv.server_close()
  finally:
     
     os.remove(socket_name)
  ```

  This feature is tested on Linux during Travis-CI builds. It also has
  been tested on Windows Subsystem for Linux (WSL) on Windows 10 1809.

  This feature is not available on "pure" Windows, as it doesn't provide
  the `AF_UNIX` address family.



  This is (obviously) taken from a console session.

  ```python
  >>> import jsonrpclib
  >>> server = jsonrpclib.ServerProxy('http://localhost:8080')
  >>> server.add(5,6)
  11
  >>> server.add(x=5, y=10)
  15
  >>> server._notify.add(5,6)

  >>> batch = jsonrpclib.MultiCall(server)
  >>> batch.add(5, 6)
  >>> batch.ping({'key':'value'})
  >>> batch._notify.add(4, 30)
  >>> results = batch()
  >>> for result in results:
  >>> ... print(result)
  11
  {'key': 'value'}



  >>> server('close')()


  >>> history = jsonrpclib.history.History()
  >>> server = jsonrpclib.ServerProxy('http://localhost:8080', history=history)
  >>> server.add(5,6)
  11
  >>> print(history.request)
  {"id": "f682b956-c8e1-4506-9db4-29fe8bc9fcaa", "jsonrpc": "2.0",
   "method": "add", "params": [5, 6]}
  >>> print(history.response)
  {"id": "f682b956-c8e1-4506-9db4-29fe8bc9fcaa", "jsonrpc": "2.0",
   "result": 11}


  >>> server('close')()
  ```

  If you need 1.0 functionality, there are a bunch of places you can pass
  that in, although the best is just to give a specific configuration to
  `jsonrpclib.ServerProxy`:

  ```python
  >>> import jsonrpclib
  >>> jsonrpclib.config.DEFAULT.version
  2.0
  >>> config = jsonrpclib.config.Config(version=1.0)
  >>> history = jsonrpclib.history.History()
  >>> server = jsonrpclib.ServerProxy('http://localhost:8080', config=config,
                                      history=history)
  >>> server.add(7, 10)
  17
  >>> print(history.request)
  {"id": "827b2923-5b37-49a5-8b36-e73920a16d32",
   "method": "add", "params": [7, 10]}
  >>> print(history.response)
  {"id": "827b2923-5b37-49a5-8b36-e73920a16d32", "error": null, "result": 17}
  >>> server('close')()
  ```

  The equivalent `loads` and `dumps` functions also exist, although with
  minor modifications.
  The `dumps` arguments are almost identical, but it adds three arguments:
  `rpcid` for the `id` key, `version` to specify the JSON-RPC compatibility,
  and `notify` if it's a request that you want to be a notification.

  Additionally, the `loads` method does not return the params and method like
  `xmlrpclib`, but instead
  a.) parses for errors, raising ProtocolErrors, and
  b.) returns the entire structure of the request / response for manual parsing.



  To connect a JSON-RPC server over a Unix socket, you have to use a specific
  protocol: `unix+http`.

  When connecting to a Unix socket in the current working directory, you can use
  the following syntax: `unix+http://my.socket`

  When you need to give an absolute path you must use the path part of the URL,
  the host part will be ignored. For example, you can use this URL to indicate a
  Unix socket in `/var/lib/daemon.socket`: `unix+http://./var/lib/daemon.socket`

  **Note:** Currently, only HTTP is supported over a Unix socket.
  If you want HTTPS support to be implemented, please create an
  [issue on GitHub](https://github.com/tcalmant/jsonrpclib/issues)



  If your remote service requires custom headers in request, you can pass them
  using the `headers` keyword argument, when creating the `ServerProxy`:

  ```python
  >>> import jsonrpclib
  >>> server = jsonrpclib.ServerProxy("http://localhost:8080",
                                      headers={'X-Test' : 'Test'})
  ```

  You can also put additional request headers only for certain method
  invocation:

  ```python
  >>> import jsonrpclib
  >>> server = jsonrpclib.Server("http://localhost:8080")
  >>> with server._additional_headers({'X-Test' : 'Test'}) as test_server:
  ...     test_server.ping(42)
  ...
  >>> # X-Test header will be no longer sent in requests
  ```

  Of course `_additional_headers` contexts can be nested as well.



  The library supports an *"automatic"* class translation process, although it
  is turned off by default.
  This can be devastatingly slow if improperly used, so the following is just a
  short list of things to keep in mind when using it.

  - Keep It (the object) Simple Stupid. (for exceptions, keep reading)
  - Do not require init params (for exceptions, keep reading)
  - Getter properties without setters could be dangerous (read: not tested)

  If any of the above are issues, use the `_serialize` method (see usage below).
  The server and client must **BOTH** have the `use_jsonclass` configuration
  item on and they must both have access to the same libraries used by the
  objects for this to work.

  If you have excessively nested arguments, it would be better to turn off the
  translation and manually invoke it on specific objects using
  `jsonrpclib.jsonclass.dump` / `jsonrpclib.jsonclass.load` (since the
  default behavior recursively goes through attributes and lists/dicts/tuples).

  * Sample file: `test_obj.py`

  ```python


  class TestObj(object):
      foo = 'bar'




  class TestSerial(object):
      foo = 'bar'
      def __init__(self, *args):
          self.args = args
      def _serialize(self):
          return (self.args, {'foo':self.foo,})
  ```

  - Sample usage:

  ```python
  >>> import jsonrpclib
  >>> import test_obj


  >>> history = jsonrpclib.history.History()
  >>> testobj1 = test_obj.TestObj()
  >>> testobj2 = test_obj.TestSerial()
  >>> server = jsonrpclib.Server('http://localhost:8080', history=history)


  >>> ping1 = server.ping(testobj1)
  >>> ping2 = server.ping(testobj2)

  >>> print(history.request)
  {"id": "7805f1f9-9abd-49c6-81dc-dbd47229fe13", "jsonrpc": "2.0",
   "method": "ping", "params": [{"__jsonclass__":
                                 ["test_obj.TestSerial", []], "foo": "bar"}
                               ]}
  >>> print(history.response)
  {"id": "7805f1f9-9abd-49c6-81dc-dbd47229fe13", "jsonrpc": "2.0",
   "result": {"__jsonclass__": ["test_obj.TestSerial", []], "foo": "bar"}}
  ```

  This behavior is turned on by default.
  To deactivate it, just set the `use_jsonclass` member of a server `Config` to
  `False`.
  If you want to use a per-class serialization method, set its name in the
  `serialize_method` member of a server `Config`.
  Finally, if you are using classes that you have defined in the implementation
  (as in, not a separate library), you'll need to add those
  (on **BOTH** the server and the client) using the `config.classes.add()` method.

  Feedback on this "feature" is very, VERY much appreciated.



  Tests are an almost-verbatim drop from the JSON-RPC specification 2.0
  page. They can be run using *unittest* or *nosetest*:

  ```
  python -m unittest discover tests
  python3 -m unittest discover tests
  nosetests tests
  ```



  In my opinion, there are several reasons to choose JSON over XML for RPC:

  * Much simpler to read (I suppose this is opinion, but I know I'm right. :)
  * Size / Bandwidth - Main reason, a JSON object representation is just much
    smaller.
  * Parsing - JSON should be much quicker to parse than XML.
  * Easy class passing with `jsonclass` (when enabled)

  In the interest of being fair, there are also a few reasons to choose XML over
  JSON:

  * Your server doesn't do JSON (rather obvious)
  * Wider XML-RPC support across APIs (can we change this? :))
  * Libraries are more established, *i.e.* more stable (Let's change this too)


pkgId: e547cbc48bef2d183e04018b93e5fde143f7c481e879337d9b5e8bf5ef9baf2b
name: python2-ledger-autosync
arch: noarch
version: 1.0.0
epoch: 0
release: 6.fc32
summary: Automatically sync your bank's data with ledger
url: https://gitlab.com/egh/ledger-autosync
rpm_license: GPLv3
rpm_vendor: Erik Hetzner <egh@e6h.org>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python2-ledger-autosync-1.0.0-6.fc32.src.rpm
location_href: packages/python2-ledger-autosync-1.0.0-6.fc32.noarch.rpm
checksum_type: sha256
description:
  ledger-autosync
  ===============

  ledger-autosync is a program to pull down transactions from your bank
  and create `ledger <http://ledger-cli.org/>`__ transactions for them.
  It is designed to only create transactions that are not already
  present in your ledger files (that is, it will deduplicate
  transactions). This should make it comparable to some of the automated
  synchronization features available in products like GnuCash, Mint,
  etc. In fact, ledger-autosync performs OFX import and synchronization
  better than all the alternatives I have seen.

  News
  ----

  v1.0.0
  ~~~~~~

  Versions of ledger-autosync before 1.0.0 printed the ofxid in a
  slightly incorrect position. This should not effect usage of the
  program, but if you would like to correct the error, see below for
  more details.

  Features
  --------

  -  supports `ledger <http://ledger-cli.org/>`__ 3 and
     `hledger <http://hledger.org/>`__
  -  like ledger, ledger-autosync will never modify your files directly
  -  interactive banking setup via
     `ofxclient <https://github.com/captin411/ofxclient>`__
  -  multiple banks and accounts
  -  support for non-US currencies
  -  support for 401k and investment accounts

     -  tracks investments by share, not dollar value
     -  support for complex transaction types, including transfers, buys,
        sells, etc.

  -  import of downloaded OFX files, for banks not supporting automatic
     download
  -  import of downloaded CSV files from Paypal, Amazon and Mint
  -  any CSV file can be supported via plugins

  Platforms
  ---------

  ledger-autosync is developed on Linux with ledger 3 and python 3; it
  has been tested on Windows (although it will run slower) and should
  run on OS X. It requires ledger 3 or hledger, but it should run faster
  with ledger, because it will not need to start a command to check
  every transaction.


  Quickstart
  ----------

  Installation
  ~~~~~~~~~~~~

  If you are on Debian or Ubuntu, an (older) version of ledger-autosync
  should be available for installation. Try:

  ::

      $ sudo apt-get install ledger-autosync

  If you use pip, you can install the latest released version:

  ::

      $ pip install ledger-autosync

  You can also install from source, if you have downloaded the source:

  ::

      $ python setup.py install

  You may need to install the following libraries (on debian/ubuntu):

  ::

      $ sudo apt-get install libffi-dev libpython-dev libssl-dev libxml2-dev python-pip libxslt-dev

  Running
  ~~~~~~~

  Once you have ledger-autosync installed, you can download an OFX file
  from your bank and run ledger-autosync against it:

  ::

      $ ledger-autosync download.ofx

  This should print a number of transactions to stdout. If you add these
  transactions to your default ledger file (whatever is read when you
  run ``ledger`` without arguments), you should find that if you run
  ledger-autosync again, it should print no transactions. This is
  because of the deduplicating feature: only new transactions will be
  printed for insertion into your ledger files.

  Using the ofx protocol for automatic download
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  ledger-autosync also supports using the OFX protocol to automatically
  connect to banks and download data. You can use the ofxclient program
  (which should have been installed with ledger-autosync) to set up
  banking:

  ::

      $ ofxclient

  When you have added your institution, quit ofxclient.

  (At least one user has reported being signed up for a pay service by
  setting up OFX direct connect. Although this seems unusual, please be
  aware of this.)

  Edit the generated ``~/ofxclient.ini`` file. Change the
  ``description`` field of your accounts to the name used in ledger.
  Optionally, move the ``~/ofxclient.ini`` file to your ``~/.config``
  directory.

  Run:

  ::

      ledger-autosync

  This will download a maximum of 90 days previous activity from your
  accounts. The output will be in ledger format and printed to stdout.
  Add this output to your ledger file. When that is done, you can call:

  ::

      ledger-autosync

  again, and it should print nothing to stdout, because you already have
  those transactions in your ledger.

  How it works
  ------------

  ledger-autosync stores a unique identifier as metadata with each
  transaction. (For OFX files, this is a unique ID provided by your
  institution for each transaction.) When syncing with your bank, it
  will check if the transaction exists by running the ledger or hledger
  command. If the transaction exists, it does nothing. If it does not
  exist, the transaction is printed to stdout.

  ofxid/csvid metadata tag
  ~~~~~~~~~~~~~~~~~~~~~~~~

  ledger-autosync stores a metatag with every posting that it outputs to
  support deduplication. This metadata tag is either ``ofxid`` (for OFX
  imports) or ``csvid`` for CSV imports.

  Pre-1.0.0 versions of ledger-autosync put this metadata tag in a
  slightly incorrect place, associating the metadata tag with the
  transaction itself, and not simply one posting. This should not effect
  the usage of ledger-autosync, but if you would like to correct your
  ledger files, there is a small python script ``fix_ofxid.py`` included
  with ledger-autosync. It can be run as:

  ::

     python fix_ofxid.py <input file>

  and will print a corrected file to stdout.

  Syncing a CSV file
  ------------------

  If you have a CSV file, you may also be able to import it using a
  recent (installed via source) version of ledger-autosync.
  ledger-autosync can currently process CSV files as provided by Paypal,
  Amazon, or Mint. You can process the CSV file as follows:

  ::

      ledger-autosync /path/to/file.csv -a Assets:Paypal

  With Amazon and Paypal CSV files, each row includes a unique
  identifier, so ledger-autosync will be able to deduplicate against any
  previously imported entries in your ledger files.

  With Mint, a unique identifier based on the data in the row is
  generated and stored. If future downloads contain identical rows, they
  will be deduplicated. This method is probably not as robust as a
  method based on unique ids, but Mint does not provide a unique id, and
  it should be better than nothing. It is likely to generate false
  negatives: transactions that seem new, but are in fact old. It will
  not generate false positives: transactions that are not generated
  because they seem old.

  If you are a developer, you should fine it easy enough to add a new
  CSV format to ledger-autosync. See, for example, the ``MintConverter``
  class in the ``ledgerautosync/converter.py`` file in this repository.
  See below for how to add these as plugins.

  Assertions
  ----------

  If you supply the ``--assertions`` flag, ledger-autosync will also
  print out valid ledger assertions based on your bank balances at the
  time of the sync. These otherwise empty transactions tell ledger that
  your balance *should* be something at a given time, and if not, ledger
  will fail with an error.

  401k and investment accounts
  ----------------------------

  If you have a 401k account, ledger-autosync can help you to track the
  state of it. You will need OFX files (or an OFX protocol connection as
  set up by ofxclient) provided by your 401k.

  In general, your 401k account will consist of buy transactions,
  transfers and reinvestments. The type will be printed in the payee
  line after a colon (``:``)

  The buy transactions are your contributions to the 401k. These will be
  printed as follows:

  ::

      2016/01/29 401k: buymf
        Assets:Retirement:401k                                 1.12345 FOOBAR @ $123.123456
        ; ofxid: 1234
        Income:Salary                                            -$138.32

  This means that you bought (contributed) $138.32 worth of FOOBAR (your
  investment fund) at the price of $123.123456. The money to buy the
  investment came from your income. In ledger-autosync, the
  ``Assets:Retirement:401k`` account is the one specified using the
  ``--account`` command line, or configured in your ``ofxclient.ini``.
  The ``Income:Salary`` is specified by the ``--unknown-account``
  option.

  If the transaction is a “transfer” transaction, this usually means
  either a fee or a change in your investment option:

  ::

      2014/06/30 401k: transfer: out
        Assets:Retirement:401k                                -1.61374 FOOBAR @ $123.123456
        ; ofxid: 1234
        Transfer                                                  $198.69

  You will need to examine your statements to determine if this was a
  fee or a real transfer back into your 401k.

  Another type of transaction is a “reinvest” transaction:

  ::

      2014/06/30 401k: reinvest
        Assets:Retirement:401k                                0.060702 FOOBAR @ $123.123456
        ; ofxid: 1234
        Income:Interest                                            -$7.47

  This probably indicates a reinvestment of dividends. ledger-autosync
  will print ``Income:Interest`` as the other account.

  resync
  ------

  By default, ledger-autosync will process transactions backwards, and
  stop when it sees a transaction that is already in ledger. To force it
  to process all transactions up to the ``--max`` days back in time
  (default: 90), use the ``--resync`` option. This can be useful when
  increasing the ``--max`` option. For instance, if you previously
  synchronized 90 days and now want to get 180 days of transactions,
  ledger-autosync would stop before going back to 180 days without the
  ``--resync`` option.

  payee format
  ------------

  By default, ledger-autosync attempts to generate a decent payee line
  (the information that follows the date in a ledger transaction).
  Unfortunately, because of differences in preference and in the format
  of OFX files, it is not always possible to generate the user’s
  preferred payee format. ledger-autosync supports a ``payee-format``
  option that can be used to generate your preferred payee line. This
  option is of the format ``Text {memo}``, where ``memo`` is a
  substitution based on the value of the transaction. Available
  substitutions are ``memo``, ``payee``, ``txntype``, ``account`` and
  ``tferaction``. For example:

  ::

     $ ledger-autosync --payee-format "Memo: {memo}"
     2011/03/31 Memo: DIVIDEND EARNED FOR PERIOD OF 03/01/2011 THROUGH 03/31/2011 ANNUAL PERCENTAGE YIELD EARNED IS 0.05%

  This option is also available for CSV conversion. For CSV files, you
  can substitution any of the values of the rows in the CSV file by
  name. For instance, for Paypal files:

  ::

     $ ledger-autosync --payee-format "{Name} ({To Email Address})" -a Paypal paypal.csv
     2016/06/04 Jane Doe (someone@example.net)

  python bindings
  ---------------

  If the ledger python bindings are available, ledger-autosync can use
  them if you pass in the ``--python`` argument. Note, however, they can
  be buggy, which is why they are disabled by default

  Plugin support
  --------------

  ledger-autosync has support for plugins. By placing python files a
  directory named ``~/.config/ledger-autosync/plugins/`` it should be
  possible to automatically load python files from there. This allows
  you to extend the csv converters with your own code. For example,
  given the input CSV file:

  ::

      "Date","Name","Amount","Balance"
      "11/30/2016","Dividend","$1.06","$1,000“

  The following converter in the file ``~/.config/ledger-autosync/plugins/my.py``:

  ::

      from ledgerautosync.converter import CsvConverter, Posting, Transaction, Amount
      import datetime
      import re

      class SomeConverter(CsvConverter):
          FIELDSET = set(["Date", "Name", Amount", "Balance"])

          def __init__(self, *args, **kwargs):
              super(SomeConverter, self).__init__(*args, **kwargs)

          def convert(self, row):
              md = re.match(r"^(\(?)\$([0-9,\.]+)", row['Amount'])
              amount = md.group(2).replace(",", "")
              if md.group(1) == "(":
                  reverse = True
              else:
                  reverse = False
              if reverse:
                  account = 'expenses'
              else:
                  account = 'income'
              return Transaction(
                  date=datetime.datetime.strptime(row['Date'], "%m/%d/%Y"),
                  payee=row['Name'],
                  postings=[Posting(self.name, Amount(amount, '$', reverse=reverse)),
                            Posting(account, Amount(amount, '$', reverse=not(reverse)))])

  Running ``ledger-autosync file.csv -a assets:bank`` will generate:

  ::

      2016/11/30 Dividend
          assets:bank                                $1.06
          income                                    -$1.06

  For more examples, see
  https://gitlab.com/egh/ledger-autosync/blob/master/ledgerautosync/converter.py#L421

  If you develop a CSV converter that you think will be generally
  useful, please consider submitting a pull request.

  Testing
  -------

  ledger-autosync uses nose for tests. To test, run nosetests in the
  project directory. This will test the ledger, hledger and
  ledger-python interfaces. To test a single interface, use nosetests -a
  hledger. To test the generic code, use nosetests -a generic. To test
  both, use nosetests -a generic -a hledger. For some reason
  nosetests -a '!hledger' will not work.


pkgId: 6176d05df11dc40456cf2b6e2d3e64c5184ddacace925c9e96bd0541aee5e318
name: python2-ofxclient
arch: noarch
version: 2.0.3
epoch: 0
release: 6.fc32
summary: OFX client for dowloading transactions from banks
url: https://github.com/captin411/ofxclient
rpm_license: MIT License
rpm_vendor: David Bartle <captindave@gmail.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python2-ofxclient-2.0.3-6.fc32.src.rpm
location_href: packages/python2-ofxclient-2.0.3-6.fc32.noarch.rpm
checksum_type: sha256
description:
  Overview
  =========

  Simple ofxclient command line utility and OFX client libraries for development.

  Full Documentation
  ==================

  http://captin411.github.com/ofxclient/

  Quick Start
  ===========

  > $ ofxclient --download combined.ofx --open --verbose

  Security Notes
  ==============

  Initial Setup
  -------------

  When using the command line tool, initial account setup uses a third party website.
  The website http://ofxhome.com will be consulted in order to determine information about
  banks.  For example, the API url that your bank wants to use for their OFX communication.

  You will be transmitting the name of your bank to a third party over an insecure channel.

  Your password and username are not transmitted during the "search" phase.

  The username and password will be transmitted to the URL for your bank as provided by
  ofxhome.com.  You will be shown the URL that will be used.  If the URL does not look
  appropriate, or otherwise appears to be tampered with, then do not submit your username
  and password during the setup phase.

  Bank Information Storage
  ------------------------
  A configuration file `$HOME/ofxclient.ini` is used to store the information about the banks
  that you want to download transactions from.

  Your username and password are stored encrypted however your account number, routing number,
  bank name, and account type are not encrypted and are visible to anyone with access to this
  file on your local computer.

  For full details on the config file, see: http://captin411.github.com/ofxclient/


pkgId: 71371ecdd18eaa1164d7c4cd93f37ea124e8d2af31af8dd3c643ff6bb3634482
name: python2-ofxhome
arch: noarch
version: 0.3.3
epoch: 0
release: 7.fc32
summary: ofxhome.com financial institution lookup REST client
url: https://github.com/captin411/ofxhome
rpm_license: MIT License
rpm_vendor: David Bartle <captindave@gmail.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python2-ofxhome-0.3.3-7.fc32.src.rpm
location_href: packages/python2-ofxhome-0.3.3-7.fc32.noarch.rpm
checksum_type: sha256
description:
  ofxhome
  =========

  REST client for the web service provided by ofxhome.com

  ofxhome.com provides a way to discover the Open Financial Exchange (OFX) URL's and financial institution IDs for banks and other financial institutions.

  ofxhome is a sort of "DNS" for financial institution OFX URLs and IDs.

  This client by itself is not all that useful unless you are coupling it with software that needs this lookup capability.

  other modules
  =============

  ofxclient - a python API that downloads transactions from banks

  example
  =======

  ```python
  from ofxhome import OFXHome

  s = OFXHome.search("USAA")
  " 's' contains a list that has entries like so:
  " { name: 'USAA Federal Savings Bank', id: '483' }
  " { name: 'USAA Investment Mgmt Co', id: '665' }
  for item in s:
      print item['id'] _ item['name']
      bank = OFXHome.lookup(item.id)
      print bank.name _ bank.fid _ bank.url _ bank.brokerid # OR
      print bank['name'] _ bank['fid'] _ bank['url'] _ bank['brokerid']
  ```


pkgId: 9e7138f3eecb0b85c1a155a67906ad3aab53260aaa9bd3344b87178927212e6e
name: python2-ofxparse
arch: noarch
version: 0.20
epoch: 0
release: 6.fc32
summary: Tools for working with the OFX (Open Financial Exchange) file format
url: http://sites.google.com/site/ofxparse
rpm_license: MIT License
rpm_vendor: Jerry Seutter <jseutter.ofxparse@gmail.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python2-ofxparse-0.20-6.fc32.src.rpm
location_href: packages/python2-ofxparse-0.20-6.fc32.noarch.rpm
checksum_type: sha256
description:
  ofxparse
  ========

  ofxparse is a parser for Open Financial Exchange (.ofx) format files.  OFX
  files are available from almost any online banking site, so they work well
  if you want to pull together your finances from multiple sources.  Online
  trading accounts also provide account statements in OFX files.

  There are three different types of OFX files, called BankAccount,
  CreditAccount and InvestmentAccount files.  This library has been tested with
  real-world samples of all three types.  If you find a file that does not work
  with this library, please consider contributing the file so ofxparse can be
  improved.  See the Help! section below for directions on how to do this.

  Example Usage
  =============

  Here's a sample program

  .. code:: python

    from ofxparse import OfxParser
    with codecs.open('file.ofx') as fileobj:
        ofx = OfxParser.parse(fileobj)

    

    ofx.account               # An Account object

    
    

    

    account = ofx.occount
    account.account_id        # The account number
    account.number            # The account number (deprecated -- returns account_id)
    account.routing_number    # The bank routing number
    account.branch_id         # Transit ID / branch number
    account.type              # An AccountType object
    account.statement         # A Statement object
    account.institution       # An Institution object

    

    account.brokerid          # Investment broker ID
    account.statement         # An InvestmentStatement object

    

    institution = account.institution
    institution.organization
    institution.fid

    

    statement = account.statement
    statement.start_date          # The start date of the transactions
    statement.end_date            # The end date of the transactions
    statement.balance             # The money in the account as of the statement date
    statement.available_balance   # The money available from the account as of the statement date
    statement.transactions        # A list of Transaction objects

    

    statement = account.statement
    statement.positions           # A list of Position objects
    statement.transactions        # A list of InvestmentTransaction objects

    

    for transaction in statement.transactions:
      transaction.payee
      transaction.type
      transaction.date
      transaction.amount
      transaction.id
      transaction.memo
      transaction.sic
      transaction.mcc
      transaction.checknum

    

    for transaction in statement.transactions:
      transaction.type
      transaction.tradeDate
      transaction.settleDate
      transaction.memo
      transaction.security      # A Security object
      transaction.income_type
      transaction.units
      transaction.unit_price
      transaction.comission
      transaction.fees
      transaction.total
      transaction.tferaction

    

    for position in statement.positions:
      position.security       # A Security object
      position.units
      position.unit_price
      position.market_value

    

    security = transaction.security
    
    security = position.security
    security.uniqueid
    security.name
    security.ticker
    security.memo


  Help!
  =====

  Sample ``.ofx`` and ``.qfx`` files are very useful.  If you want to help us out,
  please edit all identifying information from the file and then email it to
  jseutter dot ofxparse at gmail dot com.

  Development
  ===========

  Prerequisites::
    
    sudo apt-get install python-beautifulsoup python-nose python-coverage-test-runner
    
    pip install BeautifulSoup4 six lxml nose coverage
    
    pip install BeautifulSoup six nose coverage

  The `six` package is required for python 2.X compatibility

  Tests:
  Simply running the ``nosetests`` command should run the tests.

  .. code:: bash

    nosetests

  If you don't have nose installed, the following might also work:

  .. code:: bash

    python -m unittest tests.test_parse

  Test Coverage Report:

  .. code:: bash

    coverage run -m unittest tests.test_parse

    
    coverage report

    
    coverage html
    firefox htmlcov/index.html


  Homepage
  ========
  | Homepage: https://sites.google.com/site/ofxparse
  | Source: https://github.com/jseutter/ofxparse

  License
  =======

  ofxparse is released under an MIT license.  See the LICENSE file for the actual
  license text.  The basic idea is that if you can use Python to do what you are
  doing, you can also use this library.


pkgId: 1055de42864295acb4a8bf481023b9b8f41d37fef9134382c80fec005a2f9272
name: python2-setuptools_scm
arch: noarch
version: 3.2.0
epoch: 0
release: 10.fc32
summary: the blessed package to manage your versions by scm tags
url: https://github.com/pypa/setuptools_scm/
rpm_license: MIT
rpm_vendor: Ronny Pfannschmidt <opensource@ronnypfannschmidt.de>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python2-setuptools_scm-3.2.0-10.fc32.src.rpm
location_href: packages/python2-setuptools_scm-3.2.0-10.fc32.noarch.rpm
checksum_type: sha256
description:
  setuptools_scm
  ===============

  ``setuptools_scm`` handles managing your Python package versions
  in SCM metadata instead of declaring them as the version argument
  or in a SCM managed file.

  It also handles file finders for the supported SCMs.

  .. image:: https://travis-ci.org/pypa/setuptools_scm.svg?branch=master
      :target: https://travis-ci.org/pypa/setuptools_scm

  ``setup.py`` usage
  ------------------

  To use ``setuptools_scm`` just modify your project's ``setup.py`` file
  like this:

  * Add ``setuptools_scm`` to the ``setup_requires`` parameter.
  * Add the ``use_scm_version`` parameter and set it to ``True``.

  For example:

  .. code:: python

      from setuptools import setup
      setup(
          ...,
          use_scm_version=True,
          setup_requires=['setuptools_scm'],
          ...,
      )

  Arguments to ``get_version()`` (see below) may be passed as a dictionary to
  ``use_scm_version``. For example:

  .. code:: python

      from setuptools import setup
      setup(
          ...,
          use_scm_version = {"root": "..", "relative_to": __file__},
          setup_requires=['setuptools_scm'],
          ...,
      )

  Once configured, you can access the version number in your package via
  ``pkg_resources`` (`PEP-0396 <https://www.python.org/dev/peps/pep-0396>`_). For
  example:

  .. code:: python

     from pkg_resources import get_distribution, DistributionNotFound
     try:
         __version__ = get_distribution(__name__).version
     except DistributionNotFound:
         
         pass

  You can also confirm the version number locally via ``setup.py``:

  .. code-block:: shell

      $ python setup.py --version

  .. note::

     If you see unusual version numbers for packages but ``python setup.py
     --version`` reports the expected version number, ensure ``[egg_info]`` is
     not defined in ``setup.cfg``.


  ``setup.cfg``
  -------------

  If using `setuptools 30.3.0
  <https://setuptools.readthedocs.io/en/latest/setuptools.html#configuring-setup-using-setup-cfg-files>`_
  or greater, you can store ``setup_requires`` configuration in ``setup.cfg``.
  However, ``use_scm_version`` must still be placed in ``setup.py``. For example:

  .. code:: python

      
      from setuptools import setup
      setup(
          use_scm_version=True,
      )

  .. code:: ini

      
      [metadata]
      ...

      [options]
      setup_requires =
        setuptools_scm
      ...

  .. important::

      Ensure neither the ``[metadata] version`` option nor the ``[egg_info]``
      section are not defined, as these will interfere with ``setuptools_scm``.

  You may also need to define a ``pyproject.toml`` file (`PEP-0518
  <https://www.python.org/dev/peps/pep-0518>`_) to ensure you have the required
  version of ``setuptools``:

  .. code:: ini

      
      [build-system]
      requires = ["setuptools>=30.3.0", "wheel", "setuptools_scm"]

  For more information, refer to the `setuptools issue #1002
  <https://github.com/pypa/setuptools/issues/1002>`_.


  Programmatic usage
  ------------------

  In order to use ``setuptools_scm`` from code that is one directory deeper
  than the project's root, you can use:

  .. code:: python

      from setuptools_scm import get_version
      version = get_version(root='..', relative_to=__file__)

  See `setup.py Usage`_ above for how to use this within ``setup.py``.


  Usage from Sphinx
  -----------------

  It is discouraged to use ``setuptools_scm`` from Sphinx itself,
  instead use ``pkg_resources`` after editable/real installation:

  .. code:: python

      
      from pkg_resources import get_distribution
      release = get_distribution('myproject').version
      
      version = '.'.join(release.split('.')[:2])

  The underlying reason is, that services like *Read the Docs* sometimes change
  the working directory for good reasons and using the installed metadata
  prevents using needless volatile data there.

  Notable Plugins
  ----------------

  `setuptools_scm_git_archive <https://pypi.python.org/pypi/setuptools_scm_git_archive>`_
      Provides partial support for obtaining versions from git archives that
      belong to tagged versions. The only reason for not including it in
      ``setuptools_scm`` itself is Git/GitHub not supporting sufficient metadata
      for untagged/followup commits, which is preventing a consistent UX.


  Default versioning scheme
  --------------------------

  In the standard configuration ``setuptools_scm`` takes a look at three things:

  1. latest tag (with a version number)
  2. the distance to this tag (e.g. number of revisions since latest tag)
  3. workdir state (e.g. uncommitted changes since latest tag)

  and uses roughly the following logic to render the version:

  no distance and clean:
      ``{tag}``
  distance and clean:
      ``{next_version}.dev{distance}+{scm letter}{revision hash}``
  no distance and not clean:
      ``{tag}+dYYYMMMDD``
  distance and not clean:
      ``{next_version}.dev{distance}+{scm letter}{revision hash}.dYYYMMMDD``

  The next version is calculated by adding ``1`` to the last numeric component of
  the tag.

  For Git projects, the version relies on `git describe <https://git-scm.com/docs/git-describe>`_,
  so you will see an additional ``g`` prepended to the ``{revision hash}``.

  Semantic Versioning (SemVer)
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  Due to the default behavior it's necessary to always include a
  patch version (the ``3`` in ``1.2.3``), or else the automatic guessing
  will increment the wrong part of the SemVer (e.g. tag ``2.0`` results in
  ``2.1.devX`` instead of ``2.0.1.devX``). So please make sure to tag
  accordingly.

  .. note::

      Future versions of ``setuptools_scm`` will switch to `SemVer
      <http://semver.org/>`_ by default hiding the the old behavior as an
      configurable option.


  Builtin mechanisms for obtaining version numbers
  --------------------------------------------------

  1. the SCM itself (git/hg)
  2. ``.hg_archival`` files (mercurial archives)
  3. ``PKG-INFO``

  .. note::

      Git archives are not supported due to Git shortcomings


  Configuration parameters
  ------------------------

  In order to configure the way ``use_scm_version`` works you can provide
  a mapping with options instead of a boolean value.

  The currently supported configuration keys are:

  :root:
      Relative path to cwd, used for finding the SCM root; defaults to ``.``

  :version_scheme:
      Configures how the local version number is constructed; either an
      entrypoint name or a callable.

  :local_scheme:
      Configures how the local component of the version is constructed; either an
      entrypoint name or a callable.

  :write_to:
      A path to a file that gets replaced with a file containing the current
      version. It is ideal for creating a ``version.py`` file within the
      package, typically used to avoid using `pkg_resources.get_distribution`
      (which adds some overhead).

      .. warning::

        Only files with :code:`.py` and :code:`.txt` extensions have builtin
        templates, for other file types it is necessary to provide
        :code:`write_to_template`.

  :write_to_template:
      A newstyle format string that is given the current version as
      the ``version`` keyword argument for formatting.

  :relative_to:
      A file from which the root can be resolved.
      Typically called by a script or module that is not in the root of the
      repository to point ``setuptools_scm`` at the root of the repository by
      supplying ``__file__``.

  :parse:
      A function that will be used instead of the discovered SCM for parsing the
      version.
      Use with caution, this is a function for advanced use, and you should be
      familiar with the ``setuptools_scm`` internals to use it.

  :tag_regex:
      A Python regex string to extract the version part from any SCM tag.
      The regex needs to contain three named groups prefix, version and suffix,
      where ``version`` captures the actual version information.

      Defaults to the value of ``setuptools_scm.config.DEFAULT_TAG_REGEX``
      (see `config.py <src/setuptools_scm/config.py>`_).

  :git_describe_command:
      This command will be used instead the default ``git describe`` command.
      Use with caution, this is a function for advanced use, and you should be
      familiar with the ``setuptools_scm`` internals to use it.

      Defaults to the value set by ``setuptools_scm.git.DEFAULT_DESCRIBE``
      (see `git.py <src/setuptools_scm/git.py>`_).

  To use ``setuptools_scm`` in other Python code you can use the ``get_version``
  function:

  .. code:: python

      from setuptools_scm import get_version
      my_version = get_version()

  It optionally accepts the keys of the ``use_scm_version`` parameter as
  keyword arguments.

  Example configuration in ``setup.py`` format:

  .. code:: python

      from setuptools import setup

      setup(
          use_scm_version={
              'write_to': 'version.txt',
              'tag_regex': r'^(?P<prefix>v)?(?P<version>[^\+]+)(?P<suffix>.*)?$',
          }
      )

  Environment variables
  ---------------------

  :SETUPTOOLS_SCM_PRETEND_VERSION:
      when defined and not empty,
      its used as the primary source for the version number
      in which case it will be a unparsed string

  :SETUPTOOLS_SCM_DEBUG:
      when defined and not empty,
      a lot of debug information will be printed as part of ``setuptools_scm``
      operating

  Extending setuptools_scm
  ------------------------

  ``setuptools_scm`` ships with a few ``setuptools`` entrypoints based hooks to
  extend its default capabilities.

  Adding a new SCM
  ~~~~~~~~~~~~~~~~

  ``setuptools_scm`` provides two entrypoints for adding new SCMs:

  ``setuptools_scm.parse_scm``
      A function used to parse the metadata of the current workdir
      using the name of the control directory/file of your SCM as the
      entrypoint's name. E.g. for the built-in entrypoint for git the
      entrypoint is named ``.git`` and references ``setuptools_scm.git:parse``

    The return value MUST be a ``setuptools.version.ScmVersion`` instance
    created by the function ``setuptools_scm.version:meta``.

  ``setuptools_scm.files_command``
    Either a string containing a shell command that prints all SCM managed
    files in its current working directory or a callable, that given a
    pathname will return that list.

    Also use then name of your SCM control directory as name of the entrypoint.

  Version number construction
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~

  ``setuptools_scm.version_scheme``
      Configures how the version number is constructed given a
      ``setuptools.version.ScmVersion`` instance and should return a string
      representing the version.

      Available implementations:

      :guess-next-dev: automatically guesses the next development version (default)
      :post-release: generates post release versions (adds :code:`postN`)

  ``setuptools_scm.local_scheme``
      Configures how the local part of a version is rendered given a
      ``setuptools.version.ScmVersion`` instance and should return a string
      representing the local version.

      Available implementations:

      :node-and-date: adds the node on dev versions and the date on dirty
                      workdir (default)
      :node-and-timestamp: like ``node-and-date`` but with a timestamp of
                           the form ``{:%Y%m%d%H%M%SOURCE}`` instead
      :dirty-tag: adds ``+dirty`` if the current workdir has changes


  Importing in ``setup.py``
  ~~~~~~~~~~~~~~~~~~~~~~~~~

  To support usage in ``setup.py`` passing a callable into ``use_scm_version``
  is supported.

  Within that callable, ``setuptools_scm`` is available for import.
  The callable must return the configuration.


  .. code:: python

      
      import setuptools

      def myversion():
          from setuptools_scm.version import get_local_dirty_tag
          def clean_scheme(version):
              return get_local_dirty_tag(version) if version.dirty else '+clean'

          return {'local_scheme': clean_scheme}

      setup(
          ...,
          use_scm_version=myversion,
          ...
      )


  Note on testing non-installed versions
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  While the general advice is to test against a installed version,
  some environments require a test prior to install,

  .. code::

    $ python setup.py egg_info
    $ PYTHONPATH=$PWD:$PWD/src pytest



  Code of Conduct
  ---------------

  Everyone interacting in the ``setuptools_scm`` project's codebases, issue
  trackers, chat rooms, and mailing lists is expected to follow the
  `PyPA Code of Conduct`_.

  .. _PyPA Code of Conduct: https://www.pypa.io/en/latest/code-of-conduct/


pkgId: 2fe0e7e02e605c6acc52ba1c10c44d0e84f99cb531ba7f83a2633f87837c11ee
name: python2-yahoo-finance
arch: noarch
version: 1.4.0
epoch: 0
release: 7.fc32
summary: Python module to get stock data from Yahoo! Finance
url: https://github.com/lukaszbanasiak/yahoo-finance
rpm_license: MIT
rpm_vendor: Lukasz Banasiak <lukasz@banasiak.me>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python2-yahoo-finance-1.4.0-7.fc32.src.rpm
location_href: packages/python2-yahoo-finance-1.4.0-7.fc32.noarch.rpm
checksum_type: sha256
description:
  =============
  yahoo-finance
  =============

  Python module to get stock data from Yahoo! Finance

  .. image:: https://travis-ci.org/lukaszbanasiak/yahoo-finance.svg?branch=master
      :target: https://travis-ci.org/lukaszbanasiak/yahoo-finance

  Yahoo! Finance backend is http://datatables.org/. If this service is down or
  has network problems you will receive errors from group YQL*,
  eg. ``YQLQueryError``.

  You can monitor this service via https://www.datatables.org/healthchecker/

  More details https://github.com/lukaszbanasiak/yahoo-finance/issues/44

  Install
  -------

  From PyPI with pip:

  .. code:: bash

      $ pip install yahoo-finance

  From development repo (requires git)

  .. code:: bash

      $ git clone git://github.com/lukaszbanasiak/yahoo-finance.git
      $ cd yahoo-finance
      $ python setup.py install

  Usage examples
  --------------

  Get shares data
  ^^^^^^^^^^^^^^^

  Example: Yahoo! Inc. (``YHOO``)

  .. code:: python

      >>> from yahoo_finance import Share
      >>> yahoo = Share('YHOO')
      >>> print yahoo.get_open()
      '36.60'
      >>> print yahoo.get_price()
      '36.84'
      >>> print yahoo.get_trade_datetime()
      '2014-02-05 20:50:00 UTC+0000'

  Refresh data from market

  .. code:: python

      >>> yahoo.refresh()
      >>> print yahoo.get_price()
      '36.87'
      >>> print yahoo.get_trade_datetime()
      '2014-02-05 21:00:00 UTC+0000'

  Historical data

  .. code:: python

      >>> print yahoo.get_historical('2014-04-25', '2014-04-29')
      [{u'Volume': u'28720000', u'Symbol': u'YHOO', u'Adj_Close': u'35.83', u'High': u'35.89', u'Low': u'34.12', u'Date': u'2014-04-29', u'Close': u'35.83', u'Open': u'34.37'}, {u'Volume': u'30422000', u'Symbol': u'YHOO', u'Adj_Close': u'33.99', u'High': u'35.00', u'Low': u'33.65', u'Date': u'2014-04-28', u'Close': u'33.99', u'Open': u'34.67'}, {u'Volume': u'19391100', u'Symbol': u'YHOO', u'Adj_Close': u'34.48', u'High': u'35.10', u'Low': u'34.29', u'Date': u'2014-04-25', u'Close': u'34.48', u'Open': u'35.03'}]

  More readable output :)

  .. code:: python

      >>> from pprint import pprint
      >>> pprint(yahoo.get_historical('2014-04-25', '2014-04-29'))
      [{u'Adj_Close': u'35.83',
        u'Close': u'35.83',
        u'Date': u'2014-04-29',
        u'High': u'35.89',
        u'Low': u'34.12',
        u'Open': u'34.37',
        u'Symbol': u'YHOO',
        u'Volume': u'28720000'},
       {u'Adj_Close': u'33.99',
        u'Close': u'33.99',
        u'Date': u'2014-04-28',
        u'High': u'35.00',
        u'Low': u'33.65',
        u'Open': u'34.67',
        u'Symbol': u'YHOO',
        u'Volume': u'30422000'},
       {u'Adj_Close': u'34.48',
        u'Close': u'34.48',
        u'Date': u'2014-04-25',
        u'High': u'35.10',
        u'Low': u'34.29',
        u'Open': u'35.03',
        u'Symbol': u'YHOO',
        u'Volume': u'19391100'}]

  Available methods

  - ``get_price()``
  - ``get_change()``
  - ``get_percent_change()``
  - ``get_volume()``
  - ``get_prev_close()``
  - ``get_open()``
  - ``get_avg_daily_volume()``
  - ``get_stock_exchange()``
  - ``get_market_cap()``
  - ``get_book_value()``
  - ``get_ebitda()``
  - ``get_dividend_share()``
  - ``get_dividend_yield()``
  - ``get_earnings_share()``
  - ``get_days_high()``
  - ``get_days_low()``
  - ``get_year_high()``
  - ``get_year_low()``
  - ``get_50day_moving_avg()``
  - ``get_200day_moving_avg()``
  - ``get_price_earnings_ratio()``
  - ``get_price_earnings_growth_ratio()``
  - ``get_price_sales()``
  - ``get_price_book()``
  - ``get_short_ratio()``
  - ``get_trade_datetime()``
  - ``get_historical(start_date, end_date)``
  - ``get_info()``
  - ``get_name()``
  - ``refresh()``
  - ``get_percent_change_from_year_high()``
  - ``get_percent_change_from_year_low()``
  - ``get_change_from_year_low()``
  - ``get_change_from_year_high()``
  - ``get_percent_change_from_200_day_moving_average()``
  - ``get_change_from_200_day_moving_average()``
  - ``get_percent_change_from_50_day_moving_average()``
  - ``get_change_from_50_day_moving_average()``
  - ``get_EPS_estimate_next_quarter()``
  - ``get_EPS_estimate_next_year()``
  - ``get_ex_dividend_date()``
  - ``get_EPS_estimate_current_year()``
  - ``get_price_EPS_estimate_next_year()``
  - ``get_price_EPS_estimate_current_year()``
  - ``get_one_yr_target_price()``
  - ``get_change_percent_change()``
  - ``get_dividend_pay_date()``
  - ``get_currency()``
  - ``get_last_trade_with_time()``
  - ``get_days_range()``
  - ``get_year_range()``



  Get currency data
  ^^^^^^^^^^^^^^^^^

  Example: EUR/PLN (``EURPLN=X``)

  .. code:: python

      >>> from yahoo_finance import Currency
      >>> eur_pln = Currency('EURPLN')
      >>> print eur_pln.get_bid()
      '4.2007'
      >>> print eur_pln.get_ask()
      '4.2091'
      >>> print eur_pln.get_rate()
      '4.2049'
      >>> print eur_pln.get_trade_datetime()
      '2014-03-05 11:23:00 UTC+0000'

  Refresh data from market

  .. code:: python

      >>> eur_pln.refresh()
      >>> print eur_pln.get_rate()
      '4.2052'
      >>> print eur_pln.get_trade_datetime()
      '2014-03-05 11:27:00 UTC+0000'

  Avalible methods

  - ``get_bid()``
  - ``get_ask()``
  - ``get_rate()``
  - ``get_trade_datetime()``
  - ``refresh()``

  Requirements
  ------------

  See ``requirements.txt``


pkgId: d9c58cb5fe1fe351fa9698a5b1f02f58f3b9fadc079e05894379c78406ccff69
name: python3-Flask
arch: noarch
version: 1.0.2
epoch: 0
release: 6.fc32
summary: A simple framework for building complex web applications.
url: https://www.palletsprojects.com/p/flask/
rpm_license: BSD
rpm_vendor: Pallets team <contact@palletsprojects.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-Flask-1.0.2-6.fc32.src.rpm
location_href: packages/python3-Flask-1.0.2-6.fc32.noarch.rpm
checksum_type: sha256
description:
  Flask
  =====

  Flask is a lightweight `WSGI`_ web application framework. It is designed
  to make getting started quick and easy, with the ability to scale up to
  complex applications. It began as a simple wrapper around `Werkzeug`_
  and `Jinja`_ and has become one of the most popular Python web
  application frameworks.

  Flask offers suggestions, but doesn't enforce any dependencies or
  project layout. It is up to the developer to choose the tools and
  libraries they want to use. There are many extensions provided by the
  community that make adding new functionality easy.


  Installing
  ----------

  Install and update using `pip`_:

  .. code-block:: text

      pip install -U Flask


  A Simple Example
  ----------------

  .. code-block:: python

      from flask import Flask

      app = Flask(__name__)

      @app.route('/')
      def hello():
          return 'Hello, World!'

  .. code-block:: text

      $ FLASK_APP=hello.py flask run
       * Serving Flask app "hello"
       * Running on http://127.0.0.1:5000/ (Press CTRL+C to quit)


  Donate
  ------

  The Pallets organization develops and supports Flask and the libraries
  it uses. In order to grow the community of contributors and users, and
  allow the maintainers to devote more time to the projects, `please
  donate today`_.

  .. _please donate today: https://psfmember.org/civicrm/contribute/transact?reset=1&id=20


  Links
  -----

  * Website: https://www.palletsprojects.com/p/flask/
  * Documentation: http://flask.pocoo.org/docs/
  * License: `BSD <https://github.com/pallets/flask/blob/master/LICENSE>`_
  * Releases: https://pypi.org/project/Flask/
  * Code: https://github.com/pallets/flask
  * Issue tracker: https://github.com/pallets/flask/issues
  * Test status:

    * Linux, Mac: https://travis-ci.org/pallets/flask
    * Windows: https://ci.appveyor.com/project/pallets/flask

  * Test coverage: https://codecov.io/gh/pallets/flask

  .. _WSGI: https://wsgi.readthedocs.io
  .. _Werkzeug: https://www.palletsprojects.com/p/werkzeug/
  .. _Jinja: https://www.palletsprojects.com/p/jinja/
  .. _pip: https://pip.pypa.io/en/stable/quickstart/


pkgId: d80a825363552988a9553600d6a2b9eb51ea2173385588bdc104facca8e8635c
name: python3-Flask
arch: noarch
version: 1.1.2
epoch: 0
release: 7.fc32
summary: A simple framework for building complex web applications.
url: https://palletsprojects.com/p/flask/
rpm_license: BSD-3-Clause
rpm_vendor: Pallets <contact@palletsprojects.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-Flask-1.1.2-7.fc32.src.rpm
location_href: packages/python3-Flask-1.1.2-7.fc32.noarch.rpm
checksum_type: sha256
description:
  Flask
  =====

  Flask is a lightweight `WSGI`_ web application framework. It is designed
  to make getting started quick and easy, with the ability to scale up to
  complex applications. It began as a simple wrapper around `Werkzeug`_
  and `Jinja`_ and has become one of the most popular Python web
  application frameworks.

  Flask offers suggestions, but doesn't enforce any dependencies or
  project layout. It is up to the developer to choose the tools and
  libraries they want to use. There are many extensions provided by the
  community that make adding new functionality easy.


  Installing
  ----------

  Install and update using `pip`_:

  .. code-block:: text

      pip install -U Flask


  A Simple Example
  ----------------

  .. code-block:: python

      from flask import Flask

      app = Flask(__name__)

      @app.route("/")
      def hello():
          return "Hello, World!"

  .. code-block:: text

      $ env FLASK_APP=hello.py flask run
       * Serving Flask app "hello"
       * Running on http://127.0.0.1:5000/ (Press CTRL+C to quit)


  Contributing
  ------------

  For guidance on setting up a development environment and how to make a
  contribution to Flask, see the `contributing guidelines`_.

  .. _contributing guidelines: https://github.com/pallets/flask/blob/master/CONTRIBUTING.rst


  Donate
  ------

  The Pallets organization develops and supports Flask and the libraries
  it uses. In order to grow the community of contributors and users, and
  allow the maintainers to devote more time to the projects, `please
  donate today`_.

  .. _please donate today: https://psfmember.org/civicrm/contribute/transact?reset=1&id=20


  Links
  -----

  * Website: https://palletsprojects.com/p/flask/
  * Documentation: https://flask.palletsprojects.com/
  * Releases: https://pypi.org/project/Flask/
  * Code: https://github.com/pallets/flask
  * Issue tracker: https://github.com/pallets/flask/issues
  * Test status: https://dev.azure.com/pallets/flask/_build
  * Official chat: https://discord.gg/t6rrQZH

  .. _WSGI: https://wsgi.readthedocs.io
  .. _Werkzeug: https://www.palletsprojects.com/p/werkzeug/
  .. _Jinja: https://www.palletsprojects.com/p/jinja/
  .. _pip: https://pip.pypa.io/en/stable/quickstart/


pkgId: a3076f5f523fcdecc5424d40a3226d6c2289998768020ec096e671c35ac5817e
name: python3-Flask-Babel
arch: noarch
version: 0.12.2
epoch: 0
release: 6.fc32
summary: Adds i18n/l10n support to Flask applications
url: http://github.com/python-babel/flask-babel
rpm_license: BSD
rpm_vendor: Armin Ronacher <armin.ronacher@active-4.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-Flask-Babel-0.12.2-6.fc32.src.rpm
location_href: packages/python3-Flask-Babel-0.12.2-6.fc32.noarch.rpm
checksum_type: sha256
description:
  [![Build Status](https://travis-ci.org/python-babel/flask-babel.svg?branch=master)](https://travis-ci.org/python-babel/flask-babel)
  [![PyPI](https://img.shields.io/pypi/v/flask-babel.svg?maxAge=2592000)](https://pypi.python.org/pypi/Flask-Babel)
  ![license](https://img.shields.io/github/license/python-babel/flask-babel.svg?maxAge=2592000)
  ![PyPI - Python Version](https://img.shields.io/pypi/pyversions/flask-babel.svg)

  Implements i18n and l10n support for Flask.  This is based on the Python
  [babel][] module as well as [pytz][] both of which are installed automatically
  for you if you install this library.



  The latest documentation is available [here][docs].

  [babel]: https://github.com/python-babel/babel
  [pytz]: https://pypi.python.org/pypi/pytz/
  [docs]: https://pythonhosted.org/Flask-Babel/


pkgId: 6d8a834cfae644895980339666611f1c5b3392efb98498d72515bfae9986e403
name: python3-Flask-Babel
arch: noarch
version: 1.0.0
epoch: 0
release: 7.fc32
summary: Adds i18n/l10n support to Flask applications
url: http://github.com/python-babel/flask-babel
rpm_license: BSD
rpm_vendor: Armin Ronacher <armin.ronacher@active-4.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-Flask-Babel-1.0.0-7.fc32.src.rpm
location_href: packages/python3-Flask-Babel-1.0.0-7.fc32.noarch.rpm
checksum_type: sha256
description:
  [![Build Status](https://travis-ci.org/python-babel/flask-babel.svg?branch=master)](https://travis-ci.org/python-babel/flask-babel)
  [![PyPI](https://img.shields.io/pypi/v/flask-babel.svg?maxAge=2592000)](https://pypi.python.org/pypi/Flask-Babel)
  ![license](https://img.shields.io/github/license/python-babel/flask-babel.svg?maxAge=2592000)
  ![PyPI - Python Version](https://img.shields.io/pypi/pyversions/flask-babel.svg)

  Implements i18n and l10n support for Flask.  This is based on the Python
  [babel][] module as well as [pytz][] both of which are installed automatically
  for you if you install this library.



  The latest documentation is available [here][docs].





  Starting with version 1, flask-babel has changed to
  [Semantic Versioning][semver].



  - pytz is an explicit dependency. (#14)
  - pytz.gae, used for Google App Engine, is no longer necessary and has been
    removed. (#153)
  - Fixed a deprecated werkzeug import (#158).
  - Fix issues switching locales in threaded contexts (#125).

  [babel]: https://github.com/python-babel/babel
  [pytz]: https://pypi.python.org/pypi/pytz/
  [docs]: https://pythonhosted.org/Flask-Babel/
  [semver]: https://semver.org/


pkgId: 75fe9ffa767970b6ae91f856c14d99a434589fb21a9a3d595a1cd9c80064cffa
name: python3-backports.functools_lru_cache
arch: noarch
version: 1.5
epoch: 0
release: 9.fc32
summary: backports.functools_lru_cache
url: https://github.com/jaraco/backports.functools_lru_cache
rpm_license: UNKNOWN
rpm_vendor: Jason R. Coombs <jaraco@jaraco.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-backports.functools_lru_cache-1.5-9.fc32.src.rpm
location_href: packages/python3-backports.functools_lru_cache-1.5-9.fc32.noarch.rpm
checksum_type: sha256
description:
  .. image:: https://img.shields.io/pypi/v/backports.functools_lru_cache.svg
     :target: https://pypi.org/project/backports.functools_lru_cache

  .. image:: https://img.shields.io/pypi/pyversions/backports.functools_lru_cache.svg

  .. image:: https://img.shields.io/travis/jaraco/backports.functools_lru_cache/master.svg
     :target: https://travis-ci.org/jaraco/backports.functools_lru_cache

  .. .. image:: https://readthedocs.org/projects/backportsfunctools_lru_cache/badge/?version=latest
  ..    :target: https://backportsfunctools_lru_cache.readthedocs.io/en/latest/?badge=latest

  Backport of functools.lru_cache from Python 3.3 as published at `ActiveState
  <http://code.activestate.com/recipes/578078/>`_.

  Usage
  =====

  Consider using this technique for importing the 'lru_cache' function::

      try:
          from functools import lru_cache
      except ImportError:
          from backports.functools_lru_cache import lru_cache


pkgId: 8fd2b80466062496b06206e2b2c1b2e65e4caf37029ac629b0ade7e4ec63d6e7
name: python3-beancount
arch: src
version: 2.2.1
epoch: 0
release: 6.fc32
summary: Command-line Double-Entry Accounting
url: http://furius.ca/beancount
rpm_license: GNU GPLv2 only
rpm_vendor: Martin Blais <blais@furius.ca>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
location_href: packages/python3-beancount-2.2.1-6.fc32.src.rpm
checksum_type: sha256
description:
        A double-entry accounting system that uses text files as input.

        Beancount defines a simple data format or "language" that lets you define
        financial transaction records in a text file, load them in memory and
        generate and export a variety of reports, such as balance sheets or income
        statements. It also provides a client with an SQL-like query language to
        filter and aggregate financial data, and a web interface which renders
        those reports to HTML. Finally, it provides the scaffolding required to
        automate the conversion of external data into one's input file in
        Beancount syntax.


pkgId: ad14da5c3bce88e743b33e2b077ce20cf9d1a6ecc848382d8fb17392001a51d4
name: python3-beancount-debuginfo
arch: x86_64
version: 2.2.1
epoch: 0
release: 6.fc32
summary: Debug information for package python3-beancount
url: http://furius.ca/beancount
rpm_license: GNU GPLv2 only
rpm_vendor: Martin Blais <blais@furius.ca>
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-beancount-2.2.1-6.fc32.src.rpm
location_href: packages/python3-beancount-debuginfo-2.2.1-6.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package python3-beancount.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: 4bd90d8560405365f448e82b781452f8b6f77a83ce9ca4806c38335f445c7f79
name: python3-beancount-debugsource
arch: x86_64
version: 2.2.1
epoch: 0
release: 6.fc32
summary: Debug sources for package python3-beancount
url: http://furius.ca/beancount
rpm_license: GNU GPLv2 only
rpm_vendor: Martin Blais <blais@furius.ca>
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-beancount-2.2.1-6.fc32.src.rpm
location_href: packages/python3-beancount-debugsource-2.2.1-6.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug sources for package python3-beancount.
  Debug sources are useful when developing applications that use this
  package or when debugging this package.


pkgId: c05de6c45144722323e038239ce8874524f6b46c783c129c4dab45abfee720a4
name: python3-black
arch: noarch
version: 19.10b0
epoch: 0
release: 2.fc32
summary: The uncompromising code formatter.
url: https://github.com/psf/black
rpm_license: MIT
rpm_vendor: Łukasz Langa <lukasz@langa.pl>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-black-19.10b0-2.fc32.src.rpm
location_href: packages/python3-black-19.10b0-2.fc32.noarch.rpm
checksum_type: sha256
description:
  ![Black Logo](https://raw.githubusercontent.com/psf/black/master/docs/_static/logo2-readme.png)

  <h2 align="center">The Uncompromising Code Formatter</h2>

  <p align="center">
  <a href="https://travis-ci.com/psf/black"><img alt="Build Status" src="https://travis-ci.com/psf/black.svg?branch=master"></a>
  <a href="https://black.readthedocs.io/en/stable/?badge=stable"><img alt="Documentation Status" src="https://readthedocs.org/projects/black/badge/?version=stable"></a>
  <a href="https://coveralls.io/github/psf/black?branch=master"><img alt="Coverage Status" src="https://coveralls.io/repos/github/psf/black/badge.svg?branch=master"></a>
  <a href="https://github.com/psf/black/blob/master/LICENSE"><img alt="License: MIT" src="https://black.readthedocs.io/en/stable/_static/license.svg"></a>
  <a href="https://pypi.org/project/black/"><img alt="PyPI" src="https://black.readthedocs.io/en/stable/_static/pypi.svg"></a>
  <a href="https://pepy.tech/project/black"><img alt="Downloads" src="https://pepy.tech/badge/black"></a>
  <a href="https://github.com/psf/black"><img alt="Code style: black" src="https://img.shields.io/badge/code%20style-black-000000.svg"></a>
  </p>

  > “Any color you like.”

  _Black_ is the uncompromising Python code formatter. By using it, you agree to cede
  control over minutiae of hand-formatting. In return, _Black_ gives you speed,
  determinism, and freedom from `pycodestyle` nagging about formatting. You will save time
  and mental energy for more important matters.

  Blackened code looks the same regardless of the project you're reading. Formatting
  becomes transparent after a while and you can focus on the content instead.

  _Black_ makes code review faster by producing the smallest diffs possible.

  Try it out now using the [Black Playground](https://black.now.sh). Watch the
  [PyCon 2019 talk](https://youtu.be/esZLCuWs_2Y) to learn more.

  ---

  _Contents:_ **[Installation and usage](#installation-and-usage)** |
  **[Code style](#the-black-code-style)** | **[pyproject.toml](#pyprojecttoml)** |
  **[Editor integration](#editor-integration)** | **[blackd](#blackd)** |
  **[Version control integration](#version-control-integration)** |
  **[Ignoring unmodified files](#ignoring-unmodified-files)** | **[Used by](#used-by)** |
  **[Testimonials](#testimonials)** | **[Show your style](#show-your-style)** |
  **[Contributing](#contributing-to-black)** | **[Change Log](#change-log)** |
  **[Authors](#authors)**

  ---





  _Black_ can be installed by running `pip install black`. It requires Python 3.6.0+ to
  run but you can reformat Python 2 code with it, too.



  To get started right away with sensible defaults:

  ```
  black {source_file_or_directory}
  ```



  _Black_ doesn't provide many options. You can list them by running `black --help`:

  ```text
  black [OPTIONS] [SRC]...

  Options:
    -c, --code TEXT                 Format the code passed in as a string.
    -l, --line-length INTEGER       How many characters per line to allow.
                                    [default: 88]
    -t, --target-version [py27|py33|py34|py35|py36|py37|py38]
                                    Python versions that should be supported by
                                    Black's output. [default: per-file auto-
                                    detection]
    --py36                          Allow using Python 3.6-only syntax on all
                                    input files.  This will put trailing commas
                                    in function signatures and calls also after
                                    *args and **kwargs. Deprecated; use
                                    --target-version instead. [default: per-file
                                    auto-detection]
    --pyi                           Format all input files like typing stubs
                                    regardless of file extension (useful when
                                    piping source on standard input).
    -S, --skip-string-normalization
                                    Don't normalize string quotes or prefixes.
    --check                         Don't write the files back, just return the
                                    status.  Return code 0 means nothing would
                                    change.  Return code 1 means some files
                                    would be reformatted.  Return code 123 means
                                    there was an internal error.
    --diff                          Don't write the files back, just output a
                                    diff for each file on stdout.
    --fast / --safe                 If --fast given, skip temporary sanity
                                    checks. [default: --safe]
    --include TEXT                  A regular expression that matches files and
                                    directories that should be included on
                                    recursive searches.  An empty value means
                                    all files are included regardless of the
                                    name.  Use forward slashes for directories
                                    on all platforms (Windows, too).  Exclusions
                                    are calculated first, inclusions later.
                                    [default: \.pyi?$]
    --exclude TEXT                  A regular expression that matches files and
                                    directories that should be excluded on
                                    recursive searches.  An empty value means no
                                    paths are excluded. Use forward slashes for
                                    directories on all platforms (Windows, too).
                                    Exclusions are calculated first, inclusions
                                    later.  [default: /(\.eggs|\.git|\.hg|\.mypy
                                    _cache|\.nox|\.tox|\.venv|_build|buck-
                                    out|build|dist)/]
    -q, --quiet                     Don't emit non-error messages to stderr.
                                    Errors are still emitted, silence those with
                                    2>/dev/null.
    -v, --verbose                   Also emit messages to stderr about files
                                    that were not changed or were ignored due to
                                    --exclude=.
    --version                       Show the version and exit.
    --config PATH                   Read configuration from PATH.
    -h, --help                      Show this message and exit.
  ```

  _Black_ is a well-behaved Unix-style command-line tool:

  - it does nothing if no sources are passed to it;
  - it will read from standard input and write to standard output if `-` is used as the
    filename;
  - it only outputs messages to users on standard error;
  - exits with code 0 unless an internal error occurred (or `--check` was used).



  _Black_ is already [successfully used](#used-by) by many projects, small and big. It
  also sports a decent test suite. However, it is still very new. Things will probably be
  wonky for a while. This is made explicit by the "Beta" trove classifier, as well as by
  the "b" in the version number. What this means for you is that **until the formatter
  becomes stable, you should expect some formatting to change in the future**. That being
  said, no drastic stylistic changes are planned, mostly responses to bug reports.

  Also, as a temporary safety measure, _Black_ will check that the reformatted code still
  produces a valid AST that is equivalent to the original. This slows it down. If you're
  feeling confident, use `--fast`.



  _Black_ reformats entire files in place. It is not configurable. It doesn't take
  previous formatting into account. It doesn't reformat blocks that start with
  `# fmt: off` and end with `# fmt: on`. `# fmt: on/off` have to be on the same level of
  indentation. It also recognizes [YAPF](https://github.com/google/yapf)'s block comments
  to the same effect, as a courtesy for straddling code.



  _Black_ ignores previous formatting and applies uniform horizontal and vertical
  whitespace to your code. The rules for horizontal whitespace can be summarized as: do
  whatever makes `pycodestyle` happy. The coding style used by _Black_ can be viewed as a
  strict subset of PEP 8.

  As for vertical whitespace, _Black_ tries to render one full expression or simple
  statement per line. If this fits the allotted line length, great.

  ```py3


  j = [1,
       2,
       3,
  ]



  j = [1, 2, 3]
  ```

  If not, _Black_ will look at the contents of the first outer matching brackets and put
  that in a separate indented line.

  ```py3


  ImportantClass.important_method(exc, limit, lookup_lines, capture_locals, extra_argument)



  ImportantClass.important_method(
      exc, limit, lookup_lines, capture_locals, extra_argument
  )
  ```

  If that still doesn't fit the bill, it will decompose the internal expression further
  using the same rule, indenting matching brackets every time. If the contents of the
  matching brackets pair are comma-separated (like an argument list, or a dict literal,
  and so on) then _Black_ will first try to keep them on the same line with the matching
  brackets. If that doesn't work, it will put all of them in separate lines.

  ```py3


  def very_important_function(template: str, *variables, file: os.PathLike, engine: str, header: bool = True, debug: bool = False):
      """Applies `variables` to the `template` and writes to `file`."""
      with open(file, 'w') as f:
          ...



  def very_important_function(
      template: str,
      *variables,
      file: os.PathLike,
      engine: str,
      header: bool = True,
      debug: bool = False,
  ):
      """Applies `variables` to the `template` and writes to `file`."""
      with open(file, "w") as f:
          ...
  ```

  You might have noticed that closing brackets are always dedented and that a trailing
  comma is always added. Such formatting produces smaller diffs; when you add or remove an
  element, it's always just one line. Also, having the closing bracket dedented provides a
  clear delimiter between two distinct sections of the code that otherwise share the same
  indentation level (like the arguments list and the docstring in the example above).

  If a data structure literal (tuple, list, set, dict) or a line of "from" imports cannot
  fit in the allotted length, it's always split into one element per line. This minimizes
  diffs as well as enables readers of code to find which commit introduced a particular
  entry. This also makes _Black_ compatible with [isort](https://pypi.org/p/isort/) with
  the following configuration.

  <details>
  <summary>A compatible `.isort.cfg`</summary>

  ```
  [settings]
  multi_line_output=3
  include_trailing_comma=True
  force_grid_wrap=0
  use_parentheses=True
  line_length=88
  ```

  The equivalent command line is:

  ```
  $ isort --multi-line=3 --trailing-comma --force-grid-wrap=0 --use-parentheses --line-width=88 [ file.py ]
  ```

  </details>



  You probably noticed the peculiar default line length. _Black_ defaults to 88 characters
  per line, which happens to be 10% over 80. This number was found to produce
  significantly shorter files than sticking with 80 (the most popular), or even 79 (used
  by the standard library). In general,
  [90-ish seems like the wise choice](https://youtu.be/wf-BqAjZb8M?t=260).

  If you're paid by the line of code you write, you can pass `--line-length` with a lower
  number. _Black_ will try to respect that. However, sometimes it won't be able to without
  breaking other rules. In those rare cases, auto-formatted code will exceed your allotted
  limit.

  You can also increase it, but remember that people with sight disabilities find it
  harder to work with line lengths exceeding 100 characters. It also adversely affects
  side-by-side diff review on typical screen resolutions. Long lines also make it harder
  to present code neatly in documentation or talk slides.

  If you're using Flake8, you can bump `max-line-length` to 88 and forget about it.
  Alternatively, use [Bugbear](https://github.com/PyCQA/flake8-bugbear)'s B950 warning
  instead of E501 and keep the max line length at 80 which you are probably already using.
  You'd do it like this:

  ```ini
  [flake8]
  max-line-length = 80
  ...
  select = C,E,F,W,B,B950
  ignore = E203, E501, W503
  ```

  You'll find _Black_'s own .flake8 config file is configured like this. Explanation of
  why W503 and E203 are disabled can be found further in this documentation. And if you're
  curious about the reasoning behind B950,
  [Bugbear's documentation](https://github.com/PyCQA/flake8-bugbear#opinionated-warnings)
  explains it. The tl;dr is "it's like highway speed limits, we won't bother you if you
  overdo it by a few km/h".



  _Black_ avoids spurious vertical whitespace. This is in the spirit of PEP 8 which says
  that in-function vertical whitespace should only be used sparingly.

  _Black_ will allow single empty lines inside functions, and single and double empty
  lines on module level left by the original editors, except when they're within
  parenthesized expressions. Since such expressions are always reformatted to fit minimal
  space, this whitespace is lost.

  It will also insert proper spacing before and after function definitions. It's one line
  before and after inner functions and two lines before and after module-level functions
  and classes. _Black_ will not put empty lines between function/class definitions and
  standalone comments that immediately precede the given function/class.

  _Black_ will enforce single empty lines between a class-level docstring and the first
  following field or method. This conforms to
  [PEP 257](https://www.python.org/dev/peps/pep-0257/#multi-line-docstrings).

  _Black_ won't insert empty lines after function docstrings unless that empty line is
  required due to an inner function starting immediately after.



  _Black_ will add trailing commas to expressions that are split by comma where each
  element is on its own line. This includes function signatures.

  Unnecessary trailing commas are removed if an expression fits in one line. This makes it
  1% more likely that your line won't exceed the allotted line length limit. Moreover, in
  this scenario, if you added another argument to your call, you'd probably fit it in the
  same line anyway. That doesn't make diffs any larger.

  One exception to removing trailing commas is tuple expressions with just one element. In
  this case _Black_ won't touch the single trailing comma as this would unexpectedly
  change the underlying data type. Note that this is also the case when commas are used
  while indexing. This is a tuple in disguise: `numpy_array[3, ]`.

  One exception to adding trailing commas is function signatures containing `*`, `*args`,
  or `**kwargs`. In this case a trailing comma is only safe to use on Python 3.6. _Black_
  will detect if your file is already 3.6+ only and use trailing commas in this situation.
  If you wonder how it knows, it looks for f-strings and existing use of trailing commas
  in function signatures that have stars in them. In other words, if you'd like a trailing
  comma in this situation and _Black_ didn't recognize it was safe to do so, put it there
  manually and _Black_ will keep it.



  _Black_ prefers double quotes (`"` and `"""`) over single quotes (`'` and `'''`). It
  will replace the latter with the former as long as it does not result in more backslash
  escapes than before.

  _Black_ also standardizes string prefixes, making them always lowercase. On top of that,
  if your code is already Python 3.6+ only or it's using the `unicode_literals` future
  import, _Black_ will remove `u` from the string prefix as it is meaningless in those
  scenarios.

  The main reason to standardize on a single form of quotes is aesthetics. Having one kind
  of quotes everywhere reduces reader distraction. It will also enable a future version of
  _Black_ to merge consecutive string literals that ended up on the same line (see
  [#26](https://github.com/psf/black/issues/26) for details).

  Why settle on double quotes? They anticipate apostrophes in English text. They match the
  docstring standard described in
  [PEP 257](https://www.python.org/dev/peps/pep-0257/#what-is-a-docstring). An empty
  string in double quotes (`""`) is impossible to confuse with a one double-quote
  regardless of fonts and syntax highlighting used. On top of this, double quotes for
  strings are consistent with C which Python interacts a lot with.

  On certain keyboard layouts like US English, typing single quotes is a bit easier than
  double quotes. The latter requires use of the Shift key. My recommendation here is to
  keep using whatever is faster to type and let _Black_ handle the transformation.

  If you are adopting _Black_ in a large project with pre-existing string conventions
  (like the popular
  ["single quotes for data, double quotes for human-readable strings"](https://stackoverflow.com/a/56190)),
  you can pass `--skip-string-normalization` on the command line. This is meant as an
  adoption helper, avoid using this for new projects.



  _Black_ standardizes most numeric literals to use lowercase letters for the syntactic
  parts and uppercase letters for the digits themselves: `0xAB` instead of `0XAB` and
  `1e10` instead of `1E10`. Python 2 long literals are styled as `2L` instead of `2l` to
  avoid confusion between `l` and `1`.



  _Black_ will break a line before a binary operator when splitting a block of code over
  multiple lines. This is so that _Black_ is compliant with the recent changes in the
  [PEP 8](https://www.python.org/dev/peps/pep-0008/#should-a-line-break-before-or-after-a-binary-operator)
  style guide, which emphasizes that this approach improves readability.

  This behaviour may raise `W503 line break before binary operator` warnings in style
  guide enforcement tools like Flake8. Since `W503` is not PEP 8 compliant, you should
  tell Flake8 to ignore these warnings.



  PEP 8
  [recommends](https://www.python.org/dev/peps/pep-0008/#whitespace-in-expressions-and-statements)
  to treat `:` in slices as a binary operator with the lowest priority, and to leave an
  equal amount of space on either side, except if a parameter is omitted (e.g.
  `ham[1 + 1 :]`). It also states that for extended slices, both `:` operators have to
  have the same amount of spacing, except if a parameter is omitted (`ham[1 + 1 ::]`).
  _Black_ enforces these rules consistently.

  This behaviour may raise `E203 whitespace before ':'` warnings in style guide
  enforcement tools like Flake8. Since `E203` is not PEP 8 compliant, you should tell
  Flake8 to ignore these warnings.



  Some parentheses are optional in the Python grammar. Any expression can be wrapped in a
  pair of parentheses to form an atom. There are a few interesting cases:

  - `if (...):`
  - `while (...):`
  - `for (...) in (...):`
  - `assert (...), (...)`
  - `from X import (...)`
  - assignments like:
    - `target = (...)`
    - `target: type = (...)`
    - `some, *un, packing = (...)`
    - `augmented += (...)`

  In those cases, parentheses are removed when the entire statement fits in one line, or
  if the inner expression doesn't have any delimiters to further split on. If there is
  only a single delimiter and the expression starts or ends with a bracket, the
  parenthesis can also be successfully omitted since the existing bracket pair will
  organize the expression neatly anyway. Otherwise, the parentheses are added.

  Please note that _Black_ does not add or remove any additional nested parentheses that
  you might want to have for clarity or further code organization. For example those
  parentheses are not going to be removed:

  ```py3
  return not (this or that)
  decision = (maybe.this() and values > 0) or (maybe.that() and values < 0)
  ```



  Some popular APIs, like ORMs, use call chaining. This API style is known as a
  [fluent interface](https://en.wikipedia.org/wiki/Fluent_interface). _Black_ formats
  those by treating dots that follow a call or an indexing operation like a very low
  priority delimiter. It's easier to show the behavior than to explain it. Look at the
  example:

  ```py3
  def example(session):
      result = (
          session.query(models.Customer.id)
          .filter(
              models.Customer.account_id == account_id,
              models.Customer.email == email_address,
          )
          .order_by(models.Customer.id.asc())
          .all()
      )
  ```



  PEP 484 describes the syntax for type hints in Python. One of the use cases for typing
  is providing type annotations for modules which cannot contain them directly (they might
  be written in C, or they might be third-party, or their implementation may be overly
  dynamic, and so on).

  To solve this,
  [stub files with the `.pyi` file extension](https://www.python.org/dev/peps/pep-0484/#stub-files)
  can be used to describe typing information for an external module. Those stub files omit
  the implementation of classes and functions they describe, instead they only contain the
  structure of the file (listing globals, functions, and classes with their members). The
  recommended code style for those files is more terse than PEP 8:

  - prefer `...` on the same line as the class/function signature;
  - avoid vertical whitespace between consecutive module-level functions, names, or
    methods and fields within a single class;
  - use a single blank line between top-level class definitions, or none if the classes
    are very small.

  _Black_ enforces the above rules. There are additional guidelines for formatting `.pyi`
  file that are not enforced yet but might be in a future version of the formatter:

  - all function bodies should be empty (contain `...` instead of the body);
  - do not use docstrings;
  - prefer `...` over `pass`;
  - for arguments with a default, use `...` instead of the actual default;
  - avoid using string literals in type annotations, stub files support forward references
    natively (like Python 3.7 code with `from __future__ import annotations`);
  - use variable annotations instead of type comments, even for stubs that target older
    versions of Python;
  - for arguments that default to `None`, use `Optional[]` explicitly;
  - use `float` instead of `Union[int, float]`.



  _Black_ is able to read project-specific default values for its command line options
  from a `pyproject.toml` file. This is especially useful for specifying custom
  `--include` and `--exclude` patterns for your project.

  **Pro-tip**: If you're asking yourself "Do I need to configure anything?" the answer is
  "No". _Black_ is all about sensible defaults.



  [PEP 518](https://www.python.org/dev/peps/pep-0518/) defines `pyproject.toml` as a
  configuration file to store build system requirements for Python projects. With the help
  of tools like [Poetry](https://poetry.eustace.io/) or
  [Flit](https://flit.readthedocs.io/en/latest/) it can fully replace the need for
  `setup.py` and `setup.cfg` files.



  By default _Black_ looks for `pyproject.toml` starting from the common base directory of
  all files and directories passed on the command line. If it's not there, it looks in
  parent directories. It stops looking when it finds the file, or a `.git` directory, or a
  `.hg` directory, or the root of the file system, whichever comes first.

  If you're formatting standard input, _Black_ will look for configuration starting from
  the current working directory.

  You can also explicitly specify the path to a particular file that you want with
  `--config`. In this situation _Black_ will not look for any other file.

  If you're running with `--verbose`, you will see a blue message if a file was found and
  used.

  Please note `blackd` will not use `pyproject.toml` configuration.



  As the file extension suggests, `pyproject.toml` is a
  [TOML](https://github.com/toml-lang/toml) file. It contains separate sections for
  different tools. _Black_ is using the `[tool.black]` section. The option keys are the
  same as long names of options on the command line.

  Note that you have to use single-quoted strings in TOML for regular expressions. It's
  the equivalent of r-strings in Python. Multiline strings are treated as verbose regular
  expressions by Black. Use `[ ]` to denote a significant space character.

  <details>
  <summary>Example `pyproject.toml`</summary>

  ```toml
  [tool.black]
  line-length = 88
  target-version = ['py37']
  include = '\.pyi?$'
  exclude = '''

  (
    /(
        \.eggs         # exclude a few common directories in the
      | \.git          # root of the project
      | \.hg
      | \.mypy_cache
      | \.tox
      | \.venv
      | _build
      | buck-out
      | build
      | dist
    )/
    | foo.py           # also separately exclude a file named foo.py in
                       
  )
  '''
  ```

  </details>



  Command-line options have defaults that you can see in `--help`. A `pyproject.toml` can
  override those defaults. Finally, options provided by the user on the command line
  override both.

  _Black_ will only ever use one `pyproject.toml` file during an entire run. It doesn't
  look for multiple files, and doesn't compose configuration from different levels of the
  file hierarchy.





  Use [proofit404/blacken](https://github.com/proofit404/blacken) or
  [Elpy](https://github.com/jorgenschaefer/elpy).



  1. Install `black`.

  ```console
  $ pip install black
  ```

  2. Locate your `black` installation folder.

  On macOS / Linux / BSD:

  ```console
  $ which black
  /usr/local/bin/black  # possible location
  ```

  On Windows:

  ```console
  $ where black
  %LocalAppData%\Programs\Python\Python36-32\Scripts\black.exe  # possible location
  ```

  3. Open External tools in PyCharm/IntelliJ IDEA

  On macOS:

  `PyCharm -> Preferences -> Tools -> External Tools`

  On Windows / Linux / BSD:

  `File -> Settings -> Tools -> External Tools`

  4. Click the + icon to add a new external tool with the following values:

     - Name: Black
     - Description: Black is the uncompromising Python code formatter.
     - Program: <install_location_from_step_2>
     - Arguments: `"$FilePath$"`

  5. Format the currently opened file by selecting `Tools -> External Tools -> black`.

     - Alternatively, you can set a keyboard shortcut by navigating to
       `Preferences or Settings -> Keymap -> External Tools -> External Tools - Black`.

  6. Optionally, run _Black_ on every file save:

     1. Make sure you have the
        [File Watcher](https://plugins.jetbrains.com/plugin/7177-file-watchers) plugin
        installed.
     2. Go to `Preferences or Settings -> Tools -> File Watchers` and click `+` to add a
        new watcher:
        - Name: Black
        - File type: Python
        - Scope: Project Files
        - Program: <install_location_from_step_2>
        - Arguments: `$FilePath$`
        - Output paths to refresh: `$FilePath$`
        - Working directory: `$ProjectFileDir$`

     - Uncheck "Auto-save edited files to trigger the watcher"



  Wing supports black via the OS Commands tool, as explained in the Wing documentation on
  [pep8 formatting](https://wingware.com/doc/edit/pep8). The detailed procedure is:

  1. Install `black`.

  ```console
  $ pip install black
  ```

  2. Make sure it runs from the command line, e.g.

  ```console
  $ black --help
  ```

  3. In Wing IDE, activate the **OS Commands** panel and define the command **black** to
     execute black on the currently selected file:

  - Use the Tools -> OS Commands menu selection
  - click on **+** in **OS Commands** -> New: Command line..
    - Title: black
    - Command Line: black %s
    - I/O Encoding: Use Default
    - Key Binding: F1
    - [x] Raise OS Commands when executed
    - [x] Auto-save files before execution
    - [x] Line mode

  4. Select a file in the editor and press **F1** , or whatever key binding you selected
     in step 3, to reformat the file.



  Commands and shortcuts:

  - `:Black` to format the entire file (ranges not supported);
  - `:BlackUpgrade` to upgrade _Black_ inside the virtualenv;
  - `:BlackVersion` to get the current version of _Black_ inside the virtualenv.

  Configuration:

  - `g:black_fast` (defaults to `0`)
  - `g:black_linelength` (defaults to `88`)
  - `g:black_skip_string_normalization` (defaults to `0`)
  - `g:black_virtualenv` (defaults to `~/.vim/black` or `~/.local/share/nvim/black`)

  To install with [vim-plug](https://github.com/junegunn/vim-plug):

  ```
  Plug 'psf/black'
  ```

  or with [Vundle](https://github.com/VundleVim/Vundle.vim):

  ```
  Plugin 'psf/black'
  ```

  or you can copy the plugin from
  [plugin/black.vim](https://github.com/psf/black/tree/master/plugin/black.vim).

  ```
  mkdir -p ~/.vim/pack/python/start/black/plugin
  curl https://raw.githubusercontent.com/psf/black/master/plugin/black.vim -o ~/.vim/pack/python/start/black/plugin/black.vim
  ```

  Let me know if this requires any changes to work with Vim 8's builtin `packadd`, or
  Pathogen, and so on.

  This plugin **requires Vim 7.0+ built with Python 3.6+ support**. It needs Python 3.6 to
  be able to run _Black_ inside the Vim process which is much faster than calling an
  external command.

  On first run, the plugin creates its own virtualenv using the right Python version and
  automatically installs _Black_. You can upgrade it later by calling `:BlackUpgrade` and
  restarting Vim.

  If you need to do anything special to make your virtualenv work and install _Black_ (for
  example you want to run a version from master), create a virtualenv manually and point
  `g:black_virtualenv` to it. The plugin will use it.

  To run _Black_ on save, add the following line to `.vimrc` or `init.vim`:

  ```
  autocmd BufWritePre *.py execute ':Black'
  ```

  To run _Black_ on a key press (e.g. F9 below), add this:

  ```
  nnoremap <F9> :Black<CR>
  ```

  **How to get Vim with Python 3.6?** On Ubuntu 17.10 Vim comes with Python 3.6 by
  default. On macOS with Homebrew run: `brew install vim --with-python3`. When building
  Vim from source, use: `./configure --enable-python3interp=yes`. There's many guides
  online how to do this.



  Use the
  [Python extension](https://marketplace.visualstudio.com/items?itemName=ms-python.python)
  ([instructions](https://code.visualstudio.com/docs/python/editing#_formatting)).



  Use [sublack plugin](https://github.com/jgirardet/sublack).



  Use [blackcellmagic](https://github.com/csurfer/blackcellmagic).



  If your editor supports the [Language Server Protocol](https://langserver.org/) (Atom,
  Sublime Text, Visual Studio Code and many more), you can use the
  [Python Language Server](https://github.com/palantir/python-language-server) with the
  [pyls-black](https://github.com/rupert/pyls-black) plugin.



  Use [python-black](https://atom.io/packages/python-black).



  Add the following hook to your kakrc, then run black with `:format`.

  ```
  hook global WinSetOption filetype=python %{
      set-option window formatcmd 'black -q  -'
  }
  ```



  Other editors will require external contributions.

  Patches welcome! ✨ 🍰 ✨

  Any tool that can pipe code through _Black_ using its stdio mode (just
  [use `-` as the file name](https://www.tldp.org/LDP/abs/html/special-chars.html#DASHREF2)).
  The formatted code will be returned on stdout (unless `--check` was passed). _Black_
  will still emit messages on stderr but that shouldn't affect your use case.

  This can be used for example with PyCharm's or IntelliJ's
  [File Watchers](https://www.jetbrains.com/help/pycharm/file-watchers.html).



  `blackd` is a small HTTP server that exposes _Black_'s functionality over a simple
  protocol. The main benefit of using it is to avoid paying the cost of starting up a new
  _Black_ process every time you want to blacken a file.



  `blackd` is not packaged alongside _Black_ by default because it has additional
  dependencies. You will need to do `pip install black[d]` to install it.

  You can start the server on the default port, binding only to the local interface by
  running `blackd`. You will see a single line mentioning the server's version, and the
  host and port it's listening on. `blackd` will then print an access log similar to most
  web servers on standard output, merged with any exception traces caused by invalid
  formatting requests.

  `blackd` provides even less options than _Black_. You can see them by running
  `blackd --help`:

  ```text
  Usage: blackd [OPTIONS]

  Options:
    --bind-host TEXT                Address to bind the server to.
    --bind-port INTEGER             Port to listen on
    --version                       Show the version and exit.
    -h, --help                      Show this message and exit.
  ```

  There is no official blackd client tool (yet!). You can test that blackd is working
  using `curl`:

  ```
  blackd --bind-port 9090 &  # or let blackd choose a port
  curl -s -XPOST "localhost:9090" -d "print('valid')"
  ```



  `blackd` only accepts `POST` requests at the `/` path. The body of the request should
  contain the python source code to be formatted, encoded according to the `charset` field
  in the `Content-Type` request header. If no `charset` is specified, `blackd` assumes
  `UTF-8`.

  There are a few HTTP headers that control how the source is formatted. These correspond
  to command line flags for _Black_. There is one exception to this: `X-Protocol-Version`
  which if present, should have the value `1`, otherwise the request is rejected with
  `HTTP 501` (Not Implemented).

  The headers controlling how code is formatted are:

  If any of these headers are set to invalid values, `blackd` returns a `HTTP 400` error
  response, mentioning the name of the problematic header in the message body.

  - `X-Line-Length`: corresponds to the `--line-length` command line flag.
  - `X-Skip-String-Normalization`: corresponds to the `--skip-string-normalization`
    command line flag. If present and its value is not the empty string, no string
    normalization will be performed.
  - `X-Fast-Or-Safe`: if set to `fast`, `blackd` will act as _Black_ does when passed the
    `--fast` command line flag.
  - `X-Python-Variant`: if set to `pyi`, `blackd` will act as _Black_ does when passed the
    `--pyi` command line flag. Otherwise, its value must correspond to a Python version or
    a set of comma-separated Python versions, optionally prefixed with `py`. For example,
    to request code that is compatible with Python 3.5 and 3.6, set the header to
    `py3.5,py3.6`.
  - `X-Diff`: corresponds to the `--diff` command line flag. If present, a diff of the
    formats will be output.

  If any of these headers are set to invalid values, `blackd` returns a `HTTP 400` error
  response, mentioning the name of the problematic header in the message body.

  Apart from the above, `blackd` can produce the following response codes:

  - `HTTP 204`: If the input is already well-formatted. The response body is empty.
  - `HTTP 200`: If formatting was needed on the input. The response body contains the
    blackened Python code, and the `Content-Type` header is set accordingly.
  - `HTTP 400`: If the input contains a syntax error. Details of the error are returned in
    the response body.
  - `HTTP 500`: If there was any kind of error while trying to format the input. The
    response body contains a textual representation of the error.

  The response headers include a `X-Black-Version` header containing the version of
  _Black_.



  Use [pre-commit](https://pre-commit.com/). Once you
  [have it installed](https://pre-commit.com/#install), add this to the
  `.pre-commit-config.yaml` in your repository:

  ```yaml
  repos:
    - repo: https://github.com/psf/black
      rev: stable
      hooks:
        - id: black
          language_version: python3.6
  ```

  Then run `pre-commit install` and you're ready to go.

  Avoid using `args` in the hook. Instead, store necessary configuration in
  `pyproject.toml` so that editors and command-line usage of Black all behave consistently
  for your project. See _Black_'s own [pyproject.toml](/pyproject.toml) for an example.

  If you're already using Python 3.7, switch the `language_version` accordingly. Finally,
  `stable` is a tag that is pinned to the latest release on PyPI. If you'd rather run on
  master, this is also an option.



  _Black_ remembers files it has already formatted, unless the `--diff` flag is used or
  code is passed via standard input. This information is stored per-user. The exact
  location of the file depends on the _Black_ version and the system on which _Black_ is
  run. The file is non-portable. The standard location on common operating systems is:

  - Windows:
    `C:\\Users\<username>\AppData\Local\black\black\Cache\<version>\cache.<line-length>.<file-mode>.pickle`
  - macOS:
    `/Users/<username>/Library/Caches/black/<version>/cache.<line-length>.<file-mode>.pickle`
  - Linux:
    `/home/<username>/.cache/black/<version>/cache.<line-length>.<file-mode>.pickle`

  `file-mode` is an int flag that determines whether the file was formatted as 3.6+ only,
  as .pyi, and whether string normalization was omitted.

  To override the location of these files on macOS or Linux, set the environment variable
  `XDG_CACHE_HOME` to your preferred location. For example, if you want to put the cache
  in the directory you're running _Black_ from, set `XDG_CACHE_HOME=.cache`. _Black_ will
  then write the above files to `.cache/black/<version>/`.



  The following notable open-source projects trust _Black_ with enforcing a consistent
  code style: pytest, tox, Pyramid, Django Channels, Hypothesis, attrs, SQLAlchemy,
  Poetry, PyPA applications (Warehouse, Pipenv, virtualenv), pandas, Pillow, every Datadog
  Agent Integration.

  Are we missing anyone? Let us know.



  **Dusty Phillips**,
  [writer](https://smile.amazon.com/s/ref=nb_sb_noss?url=search-alias%3Daps&field-keywords=dusty+phillips):

  > _Black_ is opinionated so you don't have to be.

  **Hynek Schlawack**, [creator of `attrs`](https://www.attrs.org/), core developer of
  Twisted and CPython:

  > An auto-formatter that doesn't suck is all I want for Xmas!

  **Carl Meyer**, [Django](https://www.djangoproject.com/) core developer:

  > At least the name is good.

  **Kenneth Reitz**, creator of [`requests`](http://python-requests.org/) and
  [`pipenv`](https://docs.pipenv.org/):

  > This vastly improves the formatting of our code. Thanks a ton!



  Use the badge in your project's README.md:

  ```markdown
  [![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
  ```

  Using the badge in README.rst:

  ```
  .. image:: https://img.shields.io/badge/code%20style-black-000000.svg
      :target: https://github.com/psf/black
  ```

  Looks like this:
  [![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)



  MIT



  In terms of inspiration, _Black_ is about as configurable as _gofmt_. This is
  deliberate.

  Bug reports and fixes are always welcome! However, before you suggest a new feature or
  configuration knob, ask yourself why you want it. If it enables better integration with
  some workflow, fixes an inconsistency, speeds things up, and so on - go for it! On the
  other hand, if your answer is "because I don't like a particular formatting" then you're
  not ready to embrace _Black_ yet. Such changes are unlikely to get accepted. You can
  still try but prepare to be disappointed.

  More details can be found in [CONTRIBUTING](CONTRIBUTING.md).





  - added support for PEP 572 assignment expressions (#711)

  - added support for PEP 570 positional-only arguments (#943)

  - added support for async generators (#593)

  - added support for pre-splitting collections by putting an explicit trailing comma
    inside (#826)

  - added `black -c` as a way to format code passed from the command line (#761)

  - --safe now works with Python 2 code (#840)

  - fixed grammar selection for Python 2-specific code (#765)

  - fixed feature detection for trailing commas in function definitions and call sites
    (#763)

  - `# fmt: off`/`# fmt: on` comment pairs placed multiple times within the same block of
    code now behave correctly (#1005)

  - _Black_ no longer crashes on Windows machines with more than 61 cores (#838)

  - _Black_ no longer crashes on standalone comments prepended with a backslash (#767)

  - _Black_ no longer crashes on `from` ... `import` blocks with comments (#829)

  - _Black_ no longer crashes on Python 3.7 on some platform configurations (#494)

  - _Black_ no longer fails on comments in from-imports (#671)

  - _Black_ no longer fails when the file starts with a backslash (#922)

  - _Black_ no longer merges regular comments with type comments (#1027)

  - _Black_ no longer splits long lines that contain type comments (#997)

  - removed unnecessary parentheses around `yield` expressions (#834)

  - added parentheses around long tuples in unpacking assignments (#832)

  - added parentheses around complex powers when they are prefixed by a unary operator
    (#646)

  - fixed bug that led _Black_ format some code with a line length target of 1 (#762)

  - _Black_ no longer introduces quotes in f-string subexpressions on string boundaries
    (#863)

  - if _Black_ puts parenthesis around a single expression, it moves comments to the
    wrapped expression instead of after the brackets (#872)

  - `blackd` now returns the version of _Black_ in the response headers (#1013)

  - `blackd` can now output the diff of formats on source code when the `X-Diff` header is
    provided (#969)



  - new option `--target-version` to control which Python versions _Black_-formatted code
    should target (#618)

  - deprecated `--py36` (use `--target-version=py36` instead) (#724)

  - _Black_ no longer normalizes numeric literals to include `_` separators (#696)

  - long `del` statements are now split into multiple lines (#698)

  - type comments are no longer mangled in function signatures

  - improved performance of formatting deeply nested data structures (#509)

  - _Black_ now properly formats multiple files in parallel on Windows (#632)

  - _Black_ now creates cache files atomically which allows it to be used in parallel
    pipelines (like `xargs -P8`) (#673)

  - _Black_ now correctly indents comments in files that were previously formatted with
    tabs (#262)

  - `blackd` now supports CORS (#622)



  - numeric literals are now formatted by _Black_ (#452, #461, #464, #469):

    - numeric literals are normalized to include `_` separators on Python 3.6+ code

    - added `--skip-numeric-underscore-normalization` to disable the above behavior and
      leave numeric underscores as they were in the input

    - code with `_` in numeric literals is recognized as Python 3.6+

    - most letters in numeric literals are lowercased (e.g., in `1e10`, `0x01`)

    - hexadecimal digits are always uppercased (e.g. `0xBADC0DE`)

  - added `blackd`, see [its documentation](#blackd) for more info (#349)

  - adjacent string literals are now correctly split into multiple lines (#463)

  - trailing comma is now added to single imports that don't fit on a line (#250)

  - cache is now populated when `--check` is successful for a file which speeds up
    consecutive checks of properly formatted unmodified files (#448)

  - whitespace at the beginning of the file is now removed (#399)

  - fixed mangling [pweave](http://mpastell.com/pweave/) and
    [Spyder IDE](https://pythonhosted.org/spyder/) special comments (#532)

  - fixed unstable formatting when unpacking big tuples (#267)

  - fixed parsing of `__future__` imports with renames (#389)

  - fixed scope of `# fmt: off` when directly preceding `yield` and other nodes (#385)

  - fixed formatting of lambda expressions with default arguments (#468)

  - fixed `async for` statements: _Black_ no longer breaks them into separate lines (#372)

  - note: the Vim plugin stopped registering `,=` as a default chord as it turned out to
    be a bad idea (#415)



  - hotfix: don't freeze when multiple comments directly precede `# fmt: off` (#371)



  - typing stub files (`.pyi`) now have blank lines added after constants (#340)

  - `# fmt: off` and `# fmt: on` are now much more dependable:

    - they now work also within bracket pairs (#329)

    - they now correctly work across function/class boundaries (#335)

    - they now work when an indentation block starts with empty lines or misaligned
      comments (#334)

  - made Click not fail on invalid environments; note that Click is right but the
    likelihood we'll need to access non-ASCII file paths when dealing with Python source
    code is low (#277)

  - fixed improper formatting of f-strings with quotes inside interpolated expressions
    (#322)

  - fixed unnecessary slowdown when long list literals where found in a file

  - fixed unnecessary slowdown on AST nodes with very many siblings

  - fixed cannibalizing backslashes during string normalization

  - fixed a crash due to symbolic links pointing outside of the project directory (#338)



  - added `--config` (#65)

  - added `-h` equivalent to `--help` (#316)

  - fixed improper unmodified file caching when `-S` was used

  - fixed extra space in string unpacking (#305)

  - fixed formatting of empty triple quoted strings (#313)

  - fixed unnecessary slowdown in comment placement calculation on lines without comments



  - hotfix: don't output human-facing information on stdout (#299)

  - hotfix: don't output cake emoji on non-zero return code (#300)



  - added `--include` and `--exclude` (#270)

  - added `--skip-string-normalization` (#118)

  - added `--verbose` (#283)

  - the header output in `--diff` now actually conforms to the unified diff spec

  - fixed long trivial assignments being wrapped in unnecessary parentheses (#273)

  - fixed unnecessary parentheses when a line contained multiline strings (#232)

  - fixed stdin handling not working correctly if an old version of Click was used (#276)

  - _Black_ now preserves line endings when formatting a file in place (#258)



  - added `--pyi` (#249)

  - added `--py36` (#249)

  - Python grammar pickle caches are stored with the formatting caches, making _Black_
    work in environments where site-packages is not user-writable (#192)

  - _Black_ now enforces a PEP 257 empty line after a class-level docstring (and/or
    fields) and the first method

  - fixed invalid code produced when standalone comments were present in a trailer that
    was omitted from line splitting on a large expression (#237)

  - fixed optional parentheses being removed within `# fmt: off` sections (#224)

  - fixed invalid code produced when stars in very long imports were incorrectly wrapped
    in optional parentheses (#234)

  - fixed unstable formatting when inline comments were moved around in a trailer that was
    omitted from line splitting on a large expression (#238)

  - fixed extra empty line between a class declaration and the first method if no class
    docstring or fields are present (#219)

  - fixed extra empty line between a function signature and an inner function or inner
    class (#196)



  - call chains are now formatted according to the
    [fluent interfaces](https://en.wikipedia.org/wiki/Fluent_interface) style (#67)

  - data structure literals (tuples, lists, dictionaries, and sets) are now also always
    exploded like imports when they don't fit in a single line (#152)

  - slices are now formatted according to PEP 8 (#178)

  - parentheses are now also managed automatically on the right-hand side of assignments
    and return statements (#140)

  - math operators now use their respective priorities for delimiting multiline
    expressions (#148)

  - optional parentheses are now omitted on expressions that start or end with a bracket
    and only contain a single operator (#177)

  - empty parentheses in a class definition are now removed (#145, #180)

  - string prefixes are now standardized to lowercase and `u` is removed on Python 3.6+
    only code and Python 2.7+ code with the `unicode_literals` future import (#188, #198,
    

  - typing stub files (`.pyi`) are now formatted in a style that is consistent with PEP
    484 (#207, #210)

  - progress when reformatting many files is now reported incrementally

  - fixed trailers (content with brackets) being unnecessarily exploded into their own
    lines after a dedented closing bracket (#119)

  - fixed an invalid trailing comma sometimes left in imports (#185)

  - fixed non-deterministic formatting when multiple pairs of removable parentheses were
    used (#183)

  - fixed multiline strings being unnecessarily wrapped in optional parentheses in long
    assignments (#215)

  - fixed not splitting long from-imports with only a single name

  - fixed Python 3.6+ file discovery by also looking at function calls with unpacking.
    This fixed non-deterministic formatting if trailing commas where used both in function
    signatures with stars and function calls with stars but the former would be
    reformatted to a single line.

  - fixed crash on dealing with optional parentheses (#193)

  - fixed "is", "is not", "in", and "not in" not considered operators for splitting
    purposes

  - fixed crash when dead symlinks where encountered



  - don't populate the cache on `--check` (#175)



  - added a "cache"; files already reformatted that haven't changed on disk won't be
    reformatted again (#109)

  - `--check` and `--diff` are no longer mutually exclusive (#149)

  - generalized star expression handling, including double stars; this fixes
    multiplication making expressions "unsafe" for trailing commas (#132)

  - _Black_ no longer enforces putting empty lines behind control flow statements (#90)

  - _Black_ now splits imports like "Mode 3 + trailing comma" of isort (#127)

  - fixed comment indentation when a standalone comment closes a block (#16, #32)

  - fixed standalone comments receiving extra empty lines if immediately preceding a
    class, def, or decorator (#56, #154)

  - fixed `--diff` not showing entire path (#130)

  - fixed parsing of complex expressions after star and double stars in function calls
    (#2)

  - fixed invalid splitting on comma in lambda arguments (#133)

  - fixed missing splits of ternary expressions (#141)



  - fixed parsing of unaligned standalone comments (#99, #112)

  - fixed placement of dictionary unpacking inside dictionary literals (#111)

  - Vim plugin now works on Windows, too

  - fixed unstable formatting when encountering unnecessarily escaped quotes in a string
    (#120)



  - added `--quiet` (#78)

  - added automatic parentheses management (#4)

  - added [pre-commit](https://pre-commit.com) integration (#103, #104)

  - fixed reporting on `--check` with multiple files (#101, #102)

  - fixed removing backslash escapes from raw strings (#100, #105)



  - added `--diff` (#87)

  - add line breaks before all delimiters, except in cases like commas, to better comply
    with PEP 8 (#73)

  - standardize string literals to use double quotes (almost) everywhere (#75)

  - fixed handling of standalone comments within nested bracketed expressions; _Black_
    will no longer produce super long lines or put all standalone comments at the end of
    the expression (#22)

  - fixed 18.3a4 regression: don't crash and burn on empty lines with trailing whitespace
    (#80)

  - fixed 18.3a4 regression: `# yapf: disable` usage as trailing comment would cause
    _Black_ to not emit the rest of the file (#95)

  - when CTRL+C is pressed while formatting many files, _Black_ no longer freaks out with
    a flurry of asyncio-related exceptions

  - only allow up to two empty lines on module level and only single empty lines within
    functions (#74)



  - `# fmt: off` and `# fmt: on` are implemented (#5)

  - automatic detection of deprecated Python 2 forms of print statements and exec
    statements in the formatted file (#49)

  - use proper spaces for complex expressions in default values of typed function
    arguments (#60)

  - only return exit code 1 when --check is used (#50)

  - don't remove single trailing commas from square bracket indexing (#59)

  - don't omit whitespace if the previous factor leaf wasn't a math operator (#55)

  - omit extra space in kwarg unpacking if it's the first argument (#46)

  - omit extra space in
    [Sphinx auto-attribute comments](http://www.sphinx-doc.org/en/stable/ext/autodoc.html#directive-autoattribute)
    (#68)



  - don't remove single empty lines outside of bracketed expressions (#19)

  - added ability to pipe formatting from stdin to stdin (#25)

  - restored ability to format code with legacy usage of `async` as a name (#20, #42)

  - even better handling of numpy-style array indexing (#33, again)



  - changed positioning of binary operators to occur at beginning of lines instead of at
    the end, following
    [a recent change to PEP 8](https://github.com/python/peps/commit/c59c4376ad233a62ca4b3a6060c81368bd21e85b)
    (#21)

  - ignore empty bracket pairs while splitting. This avoids very weirdly looking
    formattings (#34, #35)

  - remove a trailing comma if there is a single argument to a call

  - if top level functions were separated by a comment, don't put four empty lines after
    the upper function

  - fixed unstable formatting of newlines with imports

  - fixed unintentional folding of post scriptum standalone comments into last statement
    if it was a simple statement (#18, #28)

  - fixed missing space in numpy-style array indexing (#33)

  - fixed spurious space after star-based unary expressions (#31)



  - added `--check`

  - only put trailing commas in function signatures and calls if it's safe to do so. If
    the file is Python 3.6+ it's always safe, otherwise only safe if there are no `*args`
    or `**kwargs` used in the signature or call. (#8)

  - fixed invalid spacing of dots in relative imports (#6, #13)

  - fixed invalid splitting after comma on unpacked variables in for-loops (#23)

  - fixed spurious space in parenthesized set expressions (#7)

  - fixed spurious space after opening parentheses and in default arguments (#14, #17)

  - fixed spurious space after unary operators when the operand was a complex expression
    (#15)



  - first published version, Happy 🍰 Day 2018!

  - alpha quality

  - date-versioned (see: https://calver.org/)



  Glued together by [Łukasz Langa](mailto:lukasz@langa.pl).

  Maintained with [Carol Willing](mailto:carolcode@willingconsulting.com),
  [Carl Meyer](mailto:carl@oddbird.net),
  [Jelle Zijlstra](mailto:jelle.zijlstra@gmail.com),
  [Mika Naylor](mailto:mail@autophagy.io), and
  [Zsolt Dollenstein](mailto:zsol.zsol@gmail.com).

  Multiple contributions by:

  - [Abdur-Rahmaan Janhangeer](mailto:cryptolabour@gmail.com)
  - [Adam Johnson](mailto:me@adamj.eu)
  - [Alexander Huynh](mailto:github@grande.coffee)
  - [Andrew Thorp](mailto:andrew.thorp.dev@gmail.com)
  - [Andrey](mailto:dyuuus@yandex.ru)
  - [Andy Freeland](mailto:andy@andyfreeland.net)
  - [Anthony Sottile](mailto:asottile@umich.edu)
  - [Arjaan Buijk](mailto:arjaan.buijk@gmail.com)
  - [Artem Malyshev](mailto:proofit404@gmail.com)
  - [Asger Hautop Drewsen](mailto:asgerdrewsen@gmail.com)
  - [Augie Fackler](mailto:raf@durin42.com)
  - [Aviskar KC](mailto:aviskarkc10@gmail.com)
  - [Benjamin Woodruff](mailto:github@benjam.info)
  - [Brandt Bucher](mailto:brandtbucher@gmail.com)
  - Charles Reid
  - [Christian Heimes](mailto:christian@python.org)
  - [Chuck Wooters](mailto:chuck.wooters@microsoft.com)
  - [Daniel Hahler](mailto:github@thequod.de)
  - [Daniel M. Capella](mailto:polycitizen@gmail.com)
  - Daniele Esposti
  - dylanjblack
  - [Eli Treuherz](mailto:eli@treuherz.com)
  - [Florent Thiery](mailto:fthiery@gmail.com)
  - hauntsaninja
  - Hugo van Kemenade
  - [Ivan Katanić](mailto:ivan.katanic@gmail.com)
  - [Jason Fried](mailto:me@jasonfried.info)
  - [jgirardet](mailto:ijkl@netc.fr)
  - [Joe Antonakakis](mailto:jma353@cornell.edu)
  - [Jon Dufresne](mailto:jon.dufresne@gmail.com)
  - [Jonas Obrist](mailto:ojiidotch@gmail.com)
  - [Josh Bode](mailto:joshbode@fastmail.com)
  - [Juan Luis Cano Rodríguez](mailto:hello@juanlu.space)
  - [Katie McLaughlin](mailto:katie@glasnt.com)
  - Lawrence Chan
  - [Linus Groh](mailto:mail@linusgroh.de)
  - [Luka Sterbic](mailto:luka.sterbic@gmail.com)
  - Mariatta
  - [Matt VanEseltine](mailto:vaneseltine@gmail.com)
  - [Michael Flaxman](mailto:michael.flaxman@gmail.com)
  - [Michael J. Sullivan](mailto:sully@msully.net)
  - [Michael McClimon](mailto:michael@mcclimon.org)
  - [Miguel Gaiowski](mailto:miggaiowski@gmail.com)
  - [Mike](mailto:roshi@fedoraproject.org)
  - [Min ho Kim](mailto:minho42@gmail.com)
  - [Miroslav Shubernetskiy](mailto:miroslav@miki725.com)
  - [Neraste](mailto:neraste.herr10@gmail.com)
  - [Ofek Lev](mailto:ofekmeister@gmail.com)
  - [Osaetin Daniel](mailto:osaetindaniel@gmail.com)
  - [Pablo Galindo](mailto:Pablogsal@gmail.com)
  - [Peter Bengtsson](mailto:mail@peterbe.com)
  - pmacosta
  - [Rishikesh Jha](mailto:rishijha424@gmail.com)
  - [Stavros Korokithakis](mailto:hi@stavros.io)
  - [Stephen Rosen](mailto:sirosen@globus.org)
  - [Sunil Kapil](mailto:snlkapil@gmail.com)
  - [Thom Lu](mailto:thomas.c.lu@gmail.com)
  - [Tom Christie](mailto:tom@tomchristie.com)
  - [Tzu-ping Chung](mailto:uranusjr@gmail.com)
  - [Utsav Shah](mailto:ukshah2@illinois.edu)
  - vezeli
  - [Vishwas B Sharma](mailto:sharma.vishwas88@gmail.com)
  - [Yngve Høiseth](mailto:yngve@hoiseth.net)
  - [Yurii Karabas](mailto:1998uriyyo@gmail.com)


pkgId: 479dd7534a296db5865cf5cba30da044bfbd2ffbfb0c61290865ce4dcae4ea93
name: python3-cheroot
arch: noarch
version: 8.3.0
epoch: 0
release: 13.fc32
summary: Highly-optimized, pure-python HTTP server
url: https://cheroot.cherrypy.org
rpm_license: UNKNOWN
rpm_vendor: CherryPy Team <team@cherrypy.org>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-cheroot-8.3.0-13.fc32.src.rpm
location_href: packages/python3-cheroot-8.3.0-13.fc32.noarch.rpm
checksum_type: sha256
description:
  .. image:: https://img.shields.io/pypi/v/cheroot.svg
     :target: https://pypi.org/project/cheroot

  .. image:: https://tidelift.com/badges/package/pypi/cheroot
     :target: https://tidelift.com/subscription/pkg/pypi-cheroot?utm_source=pypi-cheroot&utm_medium=readme
     :alt: Cheroot is available as part of the Tidelift Subscription

  .. image:: https://img.shields.io/travis/com/cherrypy/cheroot/master.svg?logo=travis&label=Linux%20build%20%40%20Travis%20CI
     :target: https://travis-ci.com/cherrypy/cheroot

  .. image:: https://circleci.com/gh/cherrypy/cheroot/tree/master.svg?style=svg
     :target: https://circleci.com/gh/cherrypy/cheroot/tree/master

  .. image:: https://img.shields.io/appveyor/ci/cherrypy/cheroot/master.svg?label=Windows%20build%20%40%20Appveyor
     :target: https://ci.appveyor.com/project/cherrypy/cheroot/branch/master

  .. image:: https://github.com/cherrypy/cheroot/workflows/Test%20suite/badge.svg
     :target: https://github.com/cherrypy/cheroot/actions?query=workflow%3A%22Test+suite%22+branch%3Amaster
     :alt: GitHub Actions Workflow — Test suite

  .. image:: https://github.com/cherrypy/cheroot/workflows/Code%20quality/badge.svg
     :target: https://github.com/cherrypy/cheroot/actions?query=workflow%3A%22Code+quality%22+branch%3Amaster
     :alt: GitHub Actions Workflow — Code quality

  .. image:: https://img.shields.io/badge/license-BSD-blue.svg?maxAge=3600
     :target: https://pypi.org/project/cheroot

  .. image:: https://img.shields.io/pypi/pyversions/cheroot.svg
     :target: https://pypi.org/project/cheroot

  .. image:: https://codecov.io/gh/cherrypy/cheroot/branch/master/graph/badge.svg
     :target: https://codecov.io/gh/cherrypy/cheroot
     :alt: codecov

  .. image:: https://readthedocs.org/projects/cheroot/badge/?version=latest
     :target: https://cheroot.cherrypy.org/en/latest/?badge=latest

  .. image:: https://img.shields.io/badge/StackOverflow-Cheroot-blue.svg
     :target: https://stackoverflow.com/questions/tagged/cheroot+or+cherrypy

  .. image:: https://img.shields.io/gitter/room/cherrypy/cherrypy.svg
     :target: https://gitter.im/cherrypy/cherrypy

  .. image:: https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square
     :target: http://makeapullrequest.com/

  .. image:: https://app.fossa.io/api/projects/git%2Bgithub.com%2Fcherrypy%2Fcheroot.svg?type=shield
     :target: https://app.fossa.io/projects/git%2Bgithub.com%2Fcherrypy%2Fcheroot?ref=badge_shield
     :alt: FOSSA Status

  Cheroot is the high-performance, pure-Python HTTP server used by CherryPy.

  Status
  ======

  The test suite currently relies on pytest. It's being run via Travis CI.

  For Enterprise
  ==============

  Cheroot is available as part of the Tidelift Subscription.

  The CherryPy maintainers and the maintainers of thousands of other packages
  are working with Tidelift to deliver one enterprise subscription that covers
  all of the open source you use.

  `Learn more <https://tidelift.com/subscription/pkg/pypi-cheroot?utm_source=pypi-cheroot&utm_medium=referral&utm_campaign=github>`_.

  Contribute Cheroot
  ==================
  **Want to add something to upstream?** Feel free to submit a PR or file an issue
  if unsure. Please follow `CherryPy's common contribution guidelines
  <https://github.com/cherrypy/cherrypy/blob/master/.github/CONTRIBUTING.rst>`_.
  Note that PR is more likely to be accepted if it includes tests and detailed
  description helping maintainers to understand it better 🎉

  Oh, and be pythonic, please 🐍

  **Don't know how?** Check out `How to Contribute to Open Source
  <https://opensource.guide/how-to-contribute/>`_ article by GitHub 🚀


  License
  =======
  .. image:: https://app.fossa.io/api/projects/git%2Bgithub.com%2Fcherrypy%2Fcheroot.svg?type=large
     :target: https://app.fossa.io/projects/git%2Bgithub.com%2Fcherrypy%2Fcheroot?ref=badge_large
     :alt: FOSSA Status


pkgId: 67d875c89872576d56a1c9b5c6c8fc392bf5d257fd8666d55777a35ec24f6192
name: python3-fuzzywuzzy
arch: noarch
version: 0.17.0
epoch: 0
release: 5.fc32
summary: Fuzzy string matching in python
url: https://github.com/seatgeek/fuzzywuzzy
rpm_license: GPL
rpm_vendor: Adam Cohen <adam@seatgeek.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-fuzzywuzzy-0.17.0-5.fc32.src.rpm
location_href: packages/python3-fuzzywuzzy-0.17.0-5.fc32.noarch.rpm
checksum_type: sha256
description:
  .. image:: https://travis-ci.org/seatgeek/fuzzywuzzy.svg?branch=master
      :target: https://travis-ci.org/seatgeek/fuzzywuzzy

  FuzzyWuzzy
  ==========

  Fuzzy string matching like a boss. It uses `Levenshtein Distance <https://en.wikipedia.org/wiki/Levenshtein_distance>`_ to calculate the differences between sequences in a simple-to-use package.

  Requirements
  ============

  -  Python 2.7 or higher
  -  difflib
  -  `python-Levenshtein <https://github.com/ztane/python-Levenshtein/>`_ (optional, provides a 4-10x speedup in String
     Matching, though may result in `differing results for certain cases <https://github.com/seatgeek/fuzzywuzzy/issues/128>`_)

  For testing
  ~~~~~~~~~~~
  -  pycodestyle
  -  hypothesis
  -  pytest

  Installation
  ============

  Using PIP via PyPI

  .. code:: bash

      pip install fuzzywuzzy

  or the following to install `python-Levenshtein` too

  .. code:: bash

      pip install fuzzywuzzy[speedup]


  Using PIP via Github

  .. code:: bash

      pip install git+git://github.com/seatgeek/fuzzywuzzy.git@0.17.0#egg=fuzzywuzzy

  Adding to your ``requirements.txt`` file (run ``pip install -r requirements.txt`` afterwards)

  .. code:: bash

      git+ssh://git@github.com/seatgeek/fuzzywuzzy.git@0.17.0#egg=fuzzywuzzy

  Manually via GIT

  .. code:: bash

      git clone git://github.com/seatgeek/fuzzywuzzy.git fuzzywuzzy
      cd fuzzywuzzy
      python setup.py install


  Usage
  =====

  .. code:: python

      >>> from fuzzywuzzy import fuzz
      >>> from fuzzywuzzy import process

  Simple Ratio
  ~~~~~~~~~~~~

  .. code:: python

      >>> fuzz.ratio("this is a test", "this is a test!")
          97

  Partial Ratio
  ~~~~~~~~~~~~~

  .. code:: python

      >>> fuzz.partial_ratio("this is a test", "this is a test!")
          100

  Token Sort Ratio
  ~~~~~~~~~~~~~~~~

  .. code:: python

      >>> fuzz.ratio("fuzzy wuzzy was a bear", "wuzzy fuzzy was a bear")
          91
      >>> fuzz.token_sort_ratio("fuzzy wuzzy was a bear", "wuzzy fuzzy was a bear")
          100

  Token Set Ratio
  ~~~~~~~~~~~~~~~

  .. code:: python

      >>> fuzz.token_sort_ratio("fuzzy was a bear", "fuzzy fuzzy was a bear")
          84
      >>> fuzz.token_set_ratio("fuzzy was a bear", "fuzzy fuzzy was a bear")
          100

  Process
  ~~~~~~~

  .. code:: python

      >>> choices = ["Atlanta Falcons", "New York Jets", "New York Giants", "Dallas Cowboys"]
      >>> process.extract("new york jets", choices, limit=2)
          [('New York Jets', 100), ('New York Giants', 78)]
      >>> process.extractOne("cowboys", choices)
          ("Dallas Cowboys", 90)

  You can also pass additional parameters to ``extractOne`` method to make it use a specific scorer. A typical use case is to match file paths:

  .. code:: python

      >>> process.extractOne("System of a down - Hypnotize - Heroin", songs)
          ('/music/library/good/System of a Down/2005 - Hypnotize/01 - Attack.mp3', 86)
      >>> process.extractOne("System of a down - Hypnotize - Heroin", songs, scorer=fuzz.token_sort_ratio)
          ("/music/library/good/System of a Down/2005 - Hypnotize/10 - She's Like Heroin.mp3", 61)

  .. |Build Status| image:: https://api.travis-ci.org/seatgeek/fuzzywuzzy.png?branch=master
     :target: https:travis-ci.org/seatgeek/fuzzywuzzy

  Known Ports
  ============

  FuzzyWuzzy is being ported to other languages too! Here are a few ports we know about:

  -  Java: `xpresso's fuzzywuzzy implementation <https://github.com/WantedTechnologies/xpresso/wiki/Approximate-string-comparison-and-pattern-matching-in-Java>`_
  -  Java: `fuzzywuzzy (java port) <https://github.com/xdrop/fuzzywuzzy>`_
  -  Rust: `fuzzyrusty (Rust port) <https://github.com/logannc/fuzzyrusty>`_
  -  JavaScript: `fuzzball.js (JavaScript port) <https://github.com/nol13/fuzzball.js>`_
  -  C++: `Tmplt/fuzzywuzzy <https://github.com/Tmplt/fuzzywuzzy>`_
  -  C#: `fuzzysharp (.Net port) <https://github.com/BoomTownRoi/BoomTown.FuzzySharp>`_
  -  Go: `go-fuzzywuzz (Go port) <https://github.com/paul-mannino/go-fuzzywuzzy>`_


pkgId: 099bbbb3130bacabedc96977cd05bde810502b16f0000a6af9ba94d553658ef0
name: python3-google-api-python-client
arch: noarch
version: 1.7.8
epoch: 0
release: 6.fc32
summary: Google API Client Library for Python
url: http://github.com/google/google-api-python-client/
rpm_license: Apache 2.0
rpm_vendor: Google Inc. <UNKNOWN>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-google-api-python-client-1.7.8-6.fc32.src.rpm
location_href: packages/python3-google-api-python-client-1.7.8-6.fc32.noarch.rpm
checksum_type: sha256
description:
  The Google API Client for Python is a client library for
  accessing the Plus, Moderator, and many other Google APIs.


pkgId: 6d6d0bec19ecdd306b8a5f4b0d5533da1cd41fc98c76f3589c7ddfa6438e29c0
name: python3-google-auth
arch: noarch
version: 1.6.3
epoch: 2
release: 6.fc32
summary: Google Authentication Library
url: https://github.com/GoogleCloudPlatform/google-auth-library-python
rpm_license: Apache 2.0
rpm_vendor: Google Cloud Platform <jonwayne+google-auth@google.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-google-auth-1.6.3-6.fc32.src.rpm
location_href: packages/python3-google-auth-1.6.3-6.fc32.noarch.rpm
checksum_type: sha256
description:
  Google Auth Python Library
  ==========================

  |build| |docs| |pypi|

  This library simplifies using Google's various server-to-server authentication
  mechanisms to access Google APIs.

  .. |build| image:: https://travis-ci.org/GoogleCloudPlatform/google-auth-library-python.svg?branch=master
     :target: https://travis-ci.org/GoogleCloudPlatform/google-auth-library-python
  .. |docs| image:: https://readthedocs.org/projects/google-auth/badge/?version=latest
     :target: https://google-auth.readthedocs.io/en/latest/
  .. |pypi| image:: https://img.shields.io/pypi/v/google-auth.svg
     :target: https://pypi.python.org/pypi/google-auth

  Installing
  ----------

  You can install using `pip`_::

      $ pip install google-auth

  .. _pip: https://pip.pypa.io/en/stable/

  For more information on setting up your Python development environment, please refer to `Python Development Environment Setup Guide`_ for Google Cloud Platform.

  .. _`Python Development Environment Setup Guide`: https://cloud.google.com/python/setup

  Supported Python Versions
  ^^^^^^^^^^^^^^^^^^^^^^^^^
  Python >= 3.4

  Deprecated Python Versions
  ^^^^^^^^^^^^^^^^^^^^^^^^^^
  Python == 2.7. Python 2.7 support will be removed on January 1, 2020.

  Documentation
  -------------

  Google Auth Python Library has usage and reference documentation at `google-auth.readthedocs.io <https://google-auth.readthedocs.io>`_.

  Maintainers
  -----------

  - `@theacodes <https://github.com/theacodes>`_ (Thea Flowers)
  - `@dhermes <https://github.com/dhermes>`_ (Danny Hermes)
  - `@lukesneeringer <https://github.com/lukesneeringer>`_ (Luke Sneeringer)

  Contributing
  ------------

  Contributions to this library are always welcome and highly encouraged.

  See `CONTRIBUTING.rst`_ for more information on how to get started.

  .. _CONTRIBUTING.rst: https://github.com/GoogleCloudPlatform/google-auth-library-python/blob/master/CONTRIBUTING.rst

  License
  -------

  Apache 2.0 - See `the LICENSE`_ for more information.

  .. _the LICENSE: https://github.com/GoogleCloudPlatform/google-auth-library-python/blob/master/LICENSE


pkgId: 1f08265b1937d7bbbb636269a16de225e17921fae28ad161b3178580c996ed1a
name: python3-google-auth-httplib2
arch: noarch
version: 0.0.3
epoch: 0
release: 6.fc32
summary: Google Authentication Library: httplib2 transport
url: https://github.com/GoogleCloudPlatform/google-auth-library-python-httplib2
rpm_license: Apache 2.0
rpm_vendor: Google Cloud Platform <jonwayne+google-auth@google.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-google-auth-httplib2-0.0.3-6.fc32.src.rpm
location_href: packages/python3-google-auth-httplib2-0.0.3-6.fc32.noarch.rpm
checksum_type: sha256
description:
  ``httplib2`` Transport for Google Auth
  ======================================

  |pypi|

  This library provides an `httplib2`_ transport for `google-auth`_.

  .. note:: ``httplib`` has lots of problems such as lack of threadsafety
      and insecure usage of TLS. Using it is highly discouraged. This
      library is intended to help existing users of ``oauth2client`` migrate to
      ``google-auth``.

  .. |pypi| image:: https://img.shields.io/pypi/v/google-auth-httplib2.svg
     :target: https://pypi.python.org/pypi/google-auth-httplib2

  .. _httplib2: https://github.com/httplib2/httplib2
  .. _google-auth: https://github.com/GoogleCloudPlatform/google-auth-library-python/

  Installing
  ----------

  You can install using `pip`_::

      $ pip install google-auth-httplib2

  .. _pip: https://pip.pypa.io/en/stable/

  License
  -------

  Apache 2.0 - See `the LICENSE`_ for more information.

  .. _the LICENSE: https://github.com/GoogleCloudPlatform/google-auth-library-python/blob/master/LICENSE


pkgId: aadc693bd10cfcf69f63cfc6ef44db5e673b713d1ae16706aa2a4b8027ad165d
name: python3-ipywidgets
arch: noarch
version: 7.4.2
epoch: 0
release: 7.fc32
summary: IPython HTML widgets for Jupyter
url: http://ipython.org
rpm_license: BSD
rpm_vendor: IPython Development Team <ipython-dev@scipy.org>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-ipywidgets-7.4.2-7.fc32.src.rpm
location_href: packages/python3-ipywidgets-7.4.2-7.fc32.noarch.rpm
checksum_type: sha256
description:
  .. image:: https://img.shields.io/pypi/v/ipywidgets.svg
     :target: https://pypi.python.org/pypi/ipywidgets/
     :alt: Version Number

  .. image:: https://img.shields.io/pypi/dm/ipywidgets.svg
     :target: https://pypi.python.org/pypi/ipywidgets/
     :alt: Number of PyPI downloads

  Interactive HTML Widgets
  ========================

  Interactive HTML widgets for Jupyter notebooks and the IPython kernel.

  Usage
  =====

  .. code-block:: python

      from ipywidgets import IntSlider
      IntSlider()


pkgId: 047bc852ee43dff8e0dc7f1e4e7321e919bd232ba284e3a96106e5048abe3f66
name: python3-jsonrpclib-pelix
arch: noarch
version: 0.4.0
epoch: 0
release: 7.fc32
url: http://github.com/tcalmant/jsonrpclib/
rpm_license: Apache License 2.0
rpm_vendor: Thomas Calmant <thomas.calmant+github@gmail.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-jsonrpclib-pelix-0.4.0-7.fc32.src.rpm
location_href: packages/python3-jsonrpclib-pelix-0.4.0-7.fc32.noarch.rpm
checksum_type: sha256
summary:
  This project is an implementation of the JSON-RPC v2.0 specification (backwards-compatible) as a client library, for Python 2.7 and Python 3. This version is a fork of jsonrpclib by Josh Marshall, made to be also usable with Pelix/iPOPO remote services.

description:
  [![Latest Version](https://img.shields.io/pypi/v/jsonrpclib-pelix.svg)](https://pypi.python.org/pypi/jsonrpclib-pelix/)
  [![License](https://img.shields.io/pypi/l/jsonrpclib-pelix.svg)](https://pypi.python.org/pypi/jsonrpclib-pelix/)
  [![Travis-CI status](https://travis-ci.org/tcalmant/jsonrpclib.svg?branch=master)](https://travis-ci.org/tcalmant/jsonrpclib)
  [![Coveralls status](https://coveralls.io/repos/tcalmant/jsonrpclib/badge.svg?branch=master)](https://coveralls.io/r/tcalmant/jsonrpclib?branch=master)

  This library is an implementation of the JSON-RPC specification.
  It supports both the original 1.0 specification, as well as the new
  (proposed) 2.0 specification, which includes batch submission, keyword
  arguments, etc.

  This library is licensed under the terms of the
  [Apache Software License 2.0](<http://www.apache.org/licenses/LICENSE-2.0.html>).




  This is a patched version of the original `jsonrpclib` project by Josh Marshall,
  available at
  [joshmarshall/jsonrpclib](<https://github.com/joshmarshall/jsonrpclib>).

  The suffix *-pelix* only indicates that this version works with Pelix
  Remote Services, but it is **not** a Pelix specific implementation.

  * This version adds support for Python 3, staying compatible with Python 2.7.
    The support for Python 2.6 has been dropped, as it was becoming to hard to
    maintain.
  * It is now possible to use the `dispatch_method` argument while extending the
    `SimpleJSONRPCDispatcher`, to use a custom dispatcher.
    This allows to use this package by Pelix Remote Services.
  * It can use thread pools to control the number of threads spawned to handle
    notification requests and clients connections.
  * The modifications added in other forks of this project have been added:
      * From [drdaeman/jsonrpclib](<https://github.com/drdaeman/jsonrpclib>):
        * Improved JSON-RPC 1.0 support
        * Less strict error response handling
      * From [tuomassalo/jsonrpclib](<https://github.com/tuomassalo/jsonrpclib>):
        * In case of a non-predefined error, raise an AppError and give access
          to *error.data*
      * From [dejw/jsonrpclib](<https://github.com/dejw/jsonrpclib>):
        * Custom headers can be sent with request and associated tests
  * Since version 0.4, this package added back the support of Unix sockets.
  * This package cannot be installed with the original `jsonrpclib`, as it uses
    the same name.



  This library implements the JSON-RPC 2.0 proposed specification in pure Python.
  It is designed to be as compatible with the syntax of `xmlrpclib` as possible
  (it extends where possible), so that projects using `xmlrpclib` could easily be
  modified to use JSON and experiment with the differences.

  It is backwards-compatible with the 1.0 specification, and supports all of the
  new proposed features of 2.0, including:

  - Batch submission (via the `MultiCall` class)
  - Keyword arguments
  - Notifications (both in a batch and 'normal')
  - Class translation using the `__jsonclass__` key.

  A `SimpleJSONRPCServer` class has been added. It is intended to emulate the
  `SimpleXMLRPCServer` from the default Python distribution.



  This library supports `cjson` and `simplejson`, and looks for the parsers in
  that order (searching first for `cjson`, then for the *built-in* `json` in 2.7+,
  and then the `simplejson` external library).
  One of these must be installed to use this library, although if you have a
  standard distribution of 2.7+, you should already have one.
  Keep in mind that `cjson` is supposed to be the quickest, I believe, so if you
  are going for full-on optimization you may want to pick it up.



  You can install this from PyPI with one of the following commands (`sudo`
  might be required):

  ```

  pip install jsonrpclib-pelix


  pip install --user jsonrpclib-pelix
  ```

  Alternatively, you can download the source from the GitHub repository at
  [tcalmant/jsonrpclib](http://github.com/tcalmant/jsonrpclib) and manually
  install it with the following commands:

  ```
  git clone git://github.com/tcalmant/jsonrpclib.git
  cd jsonrpclib
  python3 setup.py install
  ```



  This is identical in usage (or should be) to the `SimpleXMLRPCServer` in the
  Python standard library.
  Some of the differences in features are that it obviously supports notification,
  batch calls, class translation (if left on), etc.

  **Note:** The import line is slightly different from the regular
  `SimpleXMLRPCServer`, since the `SimpleJSONRPCServer` is provided by th
  `jsonrpclib` library.

  ```python
  from jsonrpclib.SimpleJSONRPCServer import SimpleJSONRPCServer

  server = SimpleJSONRPCServer(('localhost', 8080))
  server.register_function(pow)
  server.register_function(lambda x,y: x+y, 'add')
  server.register_function(lambda x: x, 'ping')
  server.serve_forever()
  ```

  To start protect the server with SSL, use the following snippet:

  ```python
  from jsonrpclib.SimpleJSONRPCServer import SimpleJSONRPCServer
  import ssl


  server = SimpleJSONRPCServer(('localhost', 8080), bind_and_activate=False)
  server.socket = ssl.wrap_socket(server.socket, certfile='server.pem',
                                  server_side=True)
  server.server_bind()
  server.server_activate()



  server.serve_forever()
  ```



  By default, notification calls are handled in the request handling thread.
  It is possible to use a thread pool to handle them, by giving it to the server
  using the `set_notification_pool()` method:

  ```python
  from jsonrpclib.SimpleJSONRPCServer import SimpleJSONRPCServer
  from jsonrpclib.threadpool import ThreadPool


  pool = ThreadPool(max_threads=10, min_threads=0)


  pool.start()


  server = SimpleJSONRPCServer(('localhost', 8080))
  server.set_notification_pool(pool)


  server.register_function(pow)
  server.register_function(lambda x,y: x+y, 'add')
  server.register_function(lambda x: x, 'ping')

  try:
      server.serve_forever()
  finally:
      
      pool.stop()
      server.set_notification_pool(None)
  ```



  It is also possible to use a thread pool to handle clients requests, using the
  `PooledJSONRPCServer` class.
  By default, this class uses pool of 0 to 30 threads.
  A custom pool can be given with the `thread_pool` parameter of the class
  constructor.

  The notification pool and the request pool are different: by default, a server
  with a request pool doesn't have a notification pool.

  ```python
  from jsonrpclib.SimpleJSONRPCServer import PooledJSONRPCServer
  from jsonrpclib.threadpool import ThreadPool


  nofif_pool = ThreadPool(max_threads=10, min_threads=0)
  request_pool = ThreadPool(max_threads=50, min_threads=10)


  nofif_pool.start()
  request_pool.start()


  server = PooledJSONRPCServer(('localhost', 8080), thread_pool=request_pool)
  server.set_notification_pool(nofif_pool)


  server.register_function(pow)
  server.register_function(lambda x,y: x+y, 'add')
  server.register_function(lambda x: x, 'ping')

  try:
      server.serve_forever()
  finally:
      
      request_pool.stop()
      nofif_pool.stop()
      server.set_notification_pool(None)
  ```



  To start a server listening on a Unix socket, you will have to use the
  following snippet:

  ```python
  from jsonrpclib.SimpleJSONRPCServer import SimpleJSONRPCServer
  import os
  import socket


  socket_name = "/tmp/my_socket.socket"


  if os.path.exists(socket_name):
     os.remove(socket_name)

  try:
     
     
     
     srv = SimpleJSONRPCServer(socket_name, address_family=socket.AF_UNIX)

     
     
     srv.serve_forever()
  except KeyboardInterrupt:
     
     srv.shutdown()
     srv.server_close()
  finally:
     
     os.remove(socket_name)
  ```

  This feature is tested on Linux during Travis-CI builds. It also has
  been tested on Windows Subsystem for Linux (WSL) on Windows 10 1809.

  This feature is not available on "pure" Windows, as it doesn't provide
  the `AF_UNIX` address family.



  This is (obviously) taken from a console session.

  ```python
  >>> import jsonrpclib
  >>> server = jsonrpclib.ServerProxy('http://localhost:8080')
  >>> server.add(5,6)
  11
  >>> server.add(x=5, y=10)
  15
  >>> server._notify.add(5,6)

  >>> batch = jsonrpclib.MultiCall(server)
  >>> batch.add(5, 6)
  >>> batch.ping({'key':'value'})
  >>> batch._notify.add(4, 30)
  >>> results = batch()
  >>> for result in results:
  >>> ... print(result)
  11
  {'key': 'value'}



  >>> server('close')()


  >>> history = jsonrpclib.history.History()
  >>> server = jsonrpclib.ServerProxy('http://localhost:8080', history=history)
  >>> server.add(5,6)
  11
  >>> print(history.request)
  {"id": "f682b956-c8e1-4506-9db4-29fe8bc9fcaa", "jsonrpc": "2.0",
   "method": "add", "params": [5, 6]}
  >>> print(history.response)
  {"id": "f682b956-c8e1-4506-9db4-29fe8bc9fcaa", "jsonrpc": "2.0",
   "result": 11}


  >>> server('close')()
  ```

  If you need 1.0 functionality, there are a bunch of places you can pass
  that in, although the best is just to give a specific configuration to
  `jsonrpclib.ServerProxy`:

  ```python
  >>> import jsonrpclib
  >>> jsonrpclib.config.DEFAULT.version
  2.0
  >>> config = jsonrpclib.config.Config(version=1.0)
  >>> history = jsonrpclib.history.History()
  >>> server = jsonrpclib.ServerProxy('http://localhost:8080', config=config,
                                      history=history)
  >>> server.add(7, 10)
  17
  >>> print(history.request)
  {"id": "827b2923-5b37-49a5-8b36-e73920a16d32",
   "method": "add", "params": [7, 10]}
  >>> print(history.response)
  {"id": "827b2923-5b37-49a5-8b36-e73920a16d32", "error": null, "result": 17}
  >>> server('close')()
  ```

  The equivalent `loads` and `dumps` functions also exist, although with
  minor modifications.
  The `dumps` arguments are almost identical, but it adds three arguments:
  `rpcid` for the `id` key, `version` to specify the JSON-RPC compatibility,
  and `notify` if it's a request that you want to be a notification.

  Additionally, the `loads` method does not return the params and method like
  `xmlrpclib`, but instead
  a.) parses for errors, raising ProtocolErrors, and
  b.) returns the entire structure of the request / response for manual parsing.



  To connect a JSON-RPC server over a Unix socket, you have to use a specific
  protocol: `unix+http`.

  When connecting to a Unix socket in the current working directory, you can use
  the following syntax: `unix+http://my.socket`

  When you need to give an absolute path you must use the path part of the URL,
  the host part will be ignored. For example, you can use this URL to indicate a
  Unix socket in `/var/lib/daemon.socket`: `unix+http://./var/lib/daemon.socket`

  **Note:** Currently, only HTTP is supported over a Unix socket.
  If you want HTTPS support to be implemented, please create an
  [issue on GitHub](https://github.com/tcalmant/jsonrpclib/issues)



  If your remote service requires custom headers in request, you can pass them
  using the `headers` keyword argument, when creating the `ServerProxy`:

  ```python
  >>> import jsonrpclib
  >>> server = jsonrpclib.ServerProxy("http://localhost:8080",
                                      headers={'X-Test' : 'Test'})
  ```

  You can also put additional request headers only for certain method
  invocation:

  ```python
  >>> import jsonrpclib
  >>> server = jsonrpclib.Server("http://localhost:8080")
  >>> with server._additional_headers({'X-Test' : 'Test'}) as test_server:
  ...     test_server.ping(42)
  ...
  >>> # X-Test header will be no longer sent in requests
  ```

  Of course `_additional_headers` contexts can be nested as well.



  The library supports an *"automatic"* class translation process, although it
  is turned off by default.
  This can be devastatingly slow if improperly used, so the following is just a
  short list of things to keep in mind when using it.

  - Keep It (the object) Simple Stupid. (for exceptions, keep reading)
  - Do not require init params (for exceptions, keep reading)
  - Getter properties without setters could be dangerous (read: not tested)

  If any of the above are issues, use the `_serialize` method (see usage below).
  The server and client must **BOTH** have the `use_jsonclass` configuration
  item on and they must both have access to the same libraries used by the
  objects for this to work.

  If you have excessively nested arguments, it would be better to turn off the
  translation and manually invoke it on specific objects using
  `jsonrpclib.jsonclass.dump` / `jsonrpclib.jsonclass.load` (since the
  default behavior recursively goes through attributes and lists/dicts/tuples).

  * Sample file: `test_obj.py`

  ```python


  class TestObj(object):
      foo = 'bar'




  class TestSerial(object):
      foo = 'bar'
      def __init__(self, *args):
          self.args = args
      def _serialize(self):
          return (self.args, {'foo':self.foo,})
  ```

  - Sample usage:

  ```python
  >>> import jsonrpclib
  >>> import test_obj


  >>> history = jsonrpclib.history.History()
  >>> testobj1 = test_obj.TestObj()
  >>> testobj2 = test_obj.TestSerial()
  >>> server = jsonrpclib.Server('http://localhost:8080', history=history)


  >>> ping1 = server.ping(testobj1)
  >>> ping2 = server.ping(testobj2)

  >>> print(history.request)
  {"id": "7805f1f9-9abd-49c6-81dc-dbd47229fe13", "jsonrpc": "2.0",
   "method": "ping", "params": [{"__jsonclass__":
                                 ["test_obj.TestSerial", []], "foo": "bar"}
                               ]}
  >>> print(history.response)
  {"id": "7805f1f9-9abd-49c6-81dc-dbd47229fe13", "jsonrpc": "2.0",
   "result": {"__jsonclass__": ["test_obj.TestSerial", []], "foo": "bar"}}
  ```

  This behavior is turned on by default.
  To deactivate it, just set the `use_jsonclass` member of a server `Config` to
  `False`.
  If you want to use a per-class serialization method, set its name in the
  `serialize_method` member of a server `Config`.
  Finally, if you are using classes that you have defined in the implementation
  (as in, not a separate library), you'll need to add those
  (on **BOTH** the server and the client) using the `config.classes.add()` method.

  Feedback on this "feature" is very, VERY much appreciated.



  Tests are an almost-verbatim drop from the JSON-RPC specification 2.0
  page. They can be run using *unittest* or *nosetest*:

  ```
  python -m unittest discover tests
  python3 -m unittest discover tests
  nosetests tests
  ```



  In my opinion, there are several reasons to choose JSON over XML for RPC:

  * Much simpler to read (I suppose this is opinion, but I know I'm right. :)
  * Size / Bandwidth - Main reason, a JSON object representation is just much
    smaller.
  * Parsing - JSON should be much quicker to parse than XML.
  * Easy class passing with `jsonclass` (when enabled)

  In the interest of being fair, there are also a few reasons to choose XML over
  JSON:

  * Your server doesn't do JSON (rather obvious)
  * Wider XML-RPC support across APIs (can we change this? :))
  * Libraries are more established, *i.e.* more stable (Let's change this too)


pkgId: f97b3b69ce3bea20ee286fa1faef48ca51882c23c4d8a11e6e84514dddd85ed3
name: python3-more-itertools
arch: noarch
version: 6.0.0
epoch: 0
release: 6.fc32
summary: More routines for operating on iterables, beyond itertools
url: https://github.com/erikrose/more-itertools
rpm_license: MIT
rpm_vendor: Erik Rose <erikrose@grinchcentral.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-more-itertools-6.0.0-6.fc32.src.rpm
location_href: packages/python3-more-itertools-6.0.0-6.fc32.noarch.rpm
checksum_type: sha256
description:
  ==============
  More Itertools
  ==============

  .. image:: https://coveralls.io/repos/github/erikrose/more-itertools/badge.svg?branch=master
    :target: https://coveralls.io/github/erikrose/more-itertools?branch=master

  Python's ``itertools`` library is a gem - you can compose elegant solutions
  for a variety of problems with the functions it provides. In ``more-itertools``
  we collect additional building blocks, recipes, and routines for working with
  Python iterables.

  ----

  +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
  | Grouping               | `chunked <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.chunked>`_,                                                                                                                        |
  |                        | `sliced <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.sliced>`_,                                                                                                                          |
  |                        | `distribute <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.distribute>`_,                                                                                                                  |
  |                        | `divide <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.divide>`_,                                                                                                                          |
  |                        | `split_at <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.split_at>`_,                                                                                                                      |
  |                        | `split_before <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.split_before>`_,                                                                                                              |
  |                        | `split_after <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.split_after>`_,                                                                                                                |
  |                        | `split_into <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.split_into>`_,                                                                                                                  |
  |                        | `bucket <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.bucket>`_,                                                                                                                          |
  |                        | `unzip <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.unzip>`_,                                                                                                                            |
  |                        | `grouper <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.grouper>`_,                                                                                                                        |
  |                        | `partition <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.partition>`_                                                                                                                     |
  +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
  | Lookahead and lookback | `spy <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.spy>`_,                                                                                                                                |
  |                        | `peekable <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.peekable>`_,                                                                                                                      |
  |                        | `seekable <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.seekable>`_                                                                                                                       |
  +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
  | Windowing              | `windowed <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.windowed>`_,                                                                                                                      |
  |                        | `substrings <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.substrings>`_,                                                                                                                  |
  |                        | `stagger <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.stagger>`_,                                                                                                                        |
  |                        | `pairwise <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.pairwise>`_                                                                                                                       |
  +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
  | Augmenting             | `count_cycle <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.count_cycle>`_,                                                                                                                |
  |                        | `intersperse <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.intersperse>`_,                                                                                                                |
  |                        | `padded <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.padded>`_,                                                                                                                          |
  |                        | `adjacent <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.adjacent>`_,                                                                                                                      |
  |                        | `groupby_transform <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.groupby_transform>`_,                                                                                                    |
  |                        | `padnone <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.padnone>`_,                                                                                                                        |
  |                        | `ncycles <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.ncycles>`_                                                                                                                         |
  +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
  | Combining              | `collapse <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.collapse>`_,                                                                                                                      |
  |                        | `sort_together <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.sort_together>`_,                                                                                                            |
  |                        | `interleave <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.interleave>`_,                                                                                                                  |
  |                        | `interleave_longest <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.interleave_longest>`_,                                                                                                  |
  |                        | `collate <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.collate>`_,                                                                                                                        |
  |                        | `zip_offset <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.zip_offset>`_,                                                                                                                  |
  |                        | `dotproduct <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.dotproduct>`_,                                                                                                                  |
  |                        | `flatten <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.flatten>`_,                                                                                                                        |
  |                        | `roundrobin <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.roundrobin>`_,                                                                                                                  |
  |                        | `prepend <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.prepend>`_                                                                                                                         |
  +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
  | Summarizing            | `ilen <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.ilen>`_,                                                                                                                              |
  |                        | `first <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.first>`_,                                                                                                                            |
  |                        | `last <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.last>`_,                                                                                                                              |
  |                        | `one <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.one>`_,                                                                                                                                |
  |                        | `unique_to_each <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.unique_to_each>`_,                                                                                                          |
  |                        | `locate <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.locate>`_,                                                                                                                          |
  |                        | `rlocate <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.rlocate>`_,                                                                                                                        |
  |                        | `consecutive_groups <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.consecutive_groups>`_,                                                                                                  |
  |                        | `exactly_n <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.exactly_n>`_,                                                                                                                    |
  |                        | `run_length <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.run_length>`_,                                                                                                                  |
  |                        | `map_reduce <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.map_reduce>`_,                                                                                                                  |
  |                        | `all_equal <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.all_equal>`_,                                                                                                                    |
  |                        | `first_true <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.first_true>`_,                                                                                                                  |
  |                        | `nth <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.nth>`_,                                                                                                                                |
  |                        | `quantify <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.quantify>`_                                                                                                                       |
  +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
  | Selecting              | `islice_extended <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.islice_extended>`_,                                                                                                        |
  |                        | `strip <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.strip>`_,                                                                                                                            |
  |                        | `lstrip <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.lstrip>`_,                                                                                                                          |
  |                        | `rstrip <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.rstrip>`_,                                                                                                                          |
  |                        | `take <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.take>`_,                                                                                                                              |
  |                        | `tail <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.tail>`_,                                                                                                                              |
  |                        | `unique_everseen <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertoo ls.unique_everseen>`_,                                                                                                       |
  |                        | `unique_justseen <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.unique_justseen>`_                                                                                                         |
  +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
  | Combinatorics          | `distinct_permutations <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.distinct_permutations>`_,                                                                                            |
  |                        | `circular_shifts <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.circular_shifts>`_,                                                                                                        |
  |                        | `powerset <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.powerset>`_,                                                                                                                      |
  |                        | `random_product <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.random_product>`_,                                                                                                          |
  |                        | `random_permutation <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.random_permutation>`_,                                                                                                  |
  |                        | `random_combination <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.random_combination>`_,                                                                                                  |
  |                        | `random_combination_with_replacement <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.random_combination_with_replacement>`_,                                                                |
  |                        | `nth_combination <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.nth_combination>`_                                                                                                         |
  +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
  | Wrapping               | `always_iterable <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.always_iterable>`_,                                                                                                        |
  |                        | `consumer <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.consumer>`_,                                                                                                                      |
  |                        | `with_iter <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.with_iter>`_,                                                                                                                    |
  |                        | `iter_except <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.iter_except>`_                                                                                                                 |
  +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
  | Others                 | `replace <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.replace>`_,                                                                                                                        |
  |                        | `numeric_range <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.numeric_range>`_,                                                                                                            |
  |                        | `always_reversible <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.always_reversible>`_,                                                                                                    |
  |                        | `side_effect <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.side_effect>`_,                                                                                                                |
  |                        | `iterate <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.iterate>`_,                                                                                                                        |
  |                        | `difference <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.difference>`_,                                                                                                                  |
  |                        | `make_decorator <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.make_decorator>`_,                                                                                                          |
  |                        | `SequenceView <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.SequenceView>`_,                                                                                                              |
  |                        | `consume <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.consume>`_,                                                                                                                        |
  |                        | `tabulate <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.tabulate>`_,                                                                                                                      |
  |                        | `repeatfunc <https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.repeatfunc>`_                                                                                                                   |
  +------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+


  Getting started
  ===============

  To get started, install the library with `pip <https://pip.pypa.io/en/stable/>`_:

  .. code-block:: shell

      pip install more-itertools

  The recipes from the `itertools docs <https://docs.python.org/3/library/itertools.html#itertools-recipes>`_
  are included in the top-level package:

  .. code-block:: python

      >>> from more_itertools import flatten
      >>> iterable = [(0, 1), (2, 3)]
      >>> list(flatten(iterable))
      [0, 1, 2, 3]

  Several new recipes are available as well:

  .. code-block:: python

      >>> from more_itertools import chunked
      >>> iterable = [0, 1, 2, 3, 4, 5, 6, 7, 8]
      >>> list(chunked(iterable, 3))
      [[0, 1, 2], [3, 4, 5], [6, 7, 8]]

      >>> from more_itertools import spy
      >>> iterable = (x * x for x in range(1, 6))
      >>> head, iterable = spy(iterable, n=3)
      >>> list(head)
      [1, 4, 9]
      >>> list(iterable)
      [1, 4, 9, 16, 25]



  For the full listing of functions, see the `API documentation <https://more-itertools.readthedocs.io/en/latest/api.html>`_.

  Development
  ===========

  ``more-itertools`` is maintained by `@erikrose <https://github.com/erikrose>`_
  and `@bbayles <https://github.com/bbayles>`_, with help from `many others <https://github.com/erikrose/more-itertools/graphs/contributors>`_.
  If you have a problem or suggestion, please file a bug or pull request in this
  repository. Thanks for contributing!


  Version History
  ===============



  6.0.0
  -----

  * Major chances:
      * Python 2.7 is no longer supported. The 5.0.0 release will be the last
        version targeting Python 2.7.
      * All future releases will target the active versions of Python 3.
        As of 2019, those are Python 3.4 and above.
      * The ``six`` library is no longer a dependency.
      * The accumulate function is no longer part of this library. You
        may import a better version from the standard ``itertools`` module.

  * Changes to existing itertools:
      * The order of the parameters in grouper have changed to match
        the latest recipe in the itertools documentation. Use of the old order
        will be supported in this release, but emit a  ``DeprecationWarning``.
        The legacy behavior will be dropped in a future release. (thanks to jaraco)
      * distinct_permutations was improved (thanks to jferard - see also `permutations with unique values <https://stackoverflow.com/questions/6284396/permutations-with-unique-values>`_ at StackOverflow.)
      * An unused parameter was removed from substrings. (thanks to pylang)

  * Other changes:
      * The docs for unique_everseen were improved. (thanks to jferard and MSeifert04)
      * Several Python 2-isms were removed. (thanks to jaraco, MSeifert04, and hugovk)

  5.0.0
  -----

  * New itertools:
      * split_into (thanks to rovyko)
      * unzip (thanks to bmintz)
      * substrings (thanks to pylang)

  * Changes to existing itertools:
      * ilen was optimized a bit (thanks to MSeifert04, achampion, and  bmintz)
      * first_true now returns ``None`` by default. This is the reason for the major version bump - see below. (thanks to sk and OJFord)

  * Other changes:
     * Some code for old Python versions was removed (thanks to hugovk)
     * Some documentation mistakes were corrected  (thanks to belm0 and hugovk)
     * Tests now run properly on 32-bit versions of Python (thanks to Millak)
     * Newer versions of CPython and PyPy are now tested against

  The major version update is due to the change in the default return value of
  first_true. It's now ``None``.

  .. code-block:: python

      >>> from more_itertools import first_true
      >>> iterable = [0, '', False, [], ()]  # All these are False
      >>> answer = first_true(iterable)
      >>> print(answer)
      None

  4.3.0
  -----

  * New itertools:
      * last (thanks to tmshn)
      * replace (thanks to pylang)
      * rlocate (thanks to jferard and pylang)

  * Improvements to existing itertools:
      * locate can now search for multiple items

  * Other changes:
     * The docs now include a nice table of tools (thanks MSeifert04)

  4.2.0
  -----

  * New itertools:
      * map_reduce (thanks to pylang)
      * prepend (from the `Python 3.7 docs <https://docs.python.org/3.7/library/itertools.html#itertools-recipes>`_)

  * Improvements to existing itertools:
      * bucket now complies with PEP 479 (thanks to irmen)

  * Other changes:
     * Python 3.7 is now supported (thanks to irmen)
     * Python 3.3 is no longer supported
     * The test suite no longer requires third-party modules to run
     * The API docs now include links to source code

  4.1.0
  -----

  * New itertools:
      * split_at (thanks to michael-celani)
      * circular_shifts (thanks to hiqua)
      * make_decorator - see the blog post `Yo, I heard you like decorators <https://sites.google.com/site/bbayles/index/decorator_factory>`_
        for a tour (thanks to pylang)
      * always_reversible (thanks to michael-celani)
      * nth_combination (from the `Python 3.7 docs <https://docs.python.org/3.7/library/itertools.html#itertools-recipes>`_)

  * Improvements to existing itertools:
      * seekable now has an ``elements`` method to return cached items.
      * The performance tradeoffs between roundrobin and
        interleave_longest are now documented (thanks michael-celani,
        pylang, and MSeifert04)

  4.0.1
  -----

  * No code changes - this release fixes how the docs display on PyPI.

  4.0.0
  -----

  * New itertools:
      * consecutive_groups (Based on the example in the `Python 2.4 docs <https://docs.python.org/release/2.4.4/lib/itertools-example.html>`_)
      * seekable (If you're looking for how to "reset" an iterator,
        you're in luck!)
      * exactly_n (thanks to michael-celani)
      * run_length.encode and run_length.decode
      * difference

  * Improvements to existing itertools:
      * The number of items between filler elements in intersperse can
        now be specified (thanks to pylang)
      * distinct_permutations and peekable got some minor
        adjustments (thanks to MSeifert04)
      * always_iterable now returns an iterator object. It also now
        allows different types to be considered iterable (thanks to jaraco)
      * bucket can now limit the keys it stores in memory
      * one now allows for custom exceptions (thanks to kalekundert)

  * Other changes:
      * A few typos were fixed (thanks to EdwardBetts)
      * All tests can now be run with ``python setup.py test``

  The major version update is due to the change in the return value of always_iterable.
  It now always returns iterator objects:

  .. code-block:: python

      >>> from more_itertools import always_iterable
      
      >>> always_iterable(12345)
      <tuple_iterator object at 0x7fb24c9488d0>
      >>> list(always_iterable(12345))
      [12345]
      
      >>> always_iterable([1, 2, 3, 4, 5])
      <list_iterator object at 0x7fb24c948c50>

  3.2.0
  -----

  * New itertools:
      * lstrip, rstrip, and strip
        (thanks to MSeifert04 and pylang)
      * islice_extended
  * Improvements to existing itertools:
      * Some bugs with slicing peekable-wrapped iterables were fixed

  3.1.0
  -----

  * New itertools:
      * numeric_range (Thanks to BebeSparkelSparkel and MSeifert04)
      * count_cycle (Thanks to BebeSparkelSparkel)
      * locate (Thanks to pylang and MSeifert04)
  * Improvements to existing itertools:
      * A few itertools are now slightly faster due to some function
        optimizations. (Thanks to MSeifert04)
  * The docs have been substantially revised with installation notes,
    categories for library functions, links, and more. (Thanks to pylang)


  3.0.0
  -----

  * Removed itertools:
      * ``context`` has been removed due to a design flaw - see below for
        replacement options. (thanks to NeilGirdhar)
  * Improvements to existing itertools:
      * ``side_effect`` now supports ``before`` and ``after`` keyword
        arguments. (Thanks to yardsale8)
  * PyPy and PyPy3 are now supported.

  The major version change is due to the removal of the ``context`` function.
  Replace it with standard ``with`` statement context management:

  .. code-block:: python

      
      file_obj = StringIO()
      consume(print(x, file=f) for f in context(file_obj) for x in u'123')

      
      file_obj = StringIO()
      with file_obj as f:
          consume(print(x, file=f) for x in u'123')

  2.6.0
  -----

  * New itertools:
      * ``adjacent`` and ``groupby_transform`` (Thanks to diazona)
      * ``always_iterable`` (Thanks to jaraco)
      * (Removed in 3.0.0) ``context`` (Thanks to yardsale8)
      * ``divide`` (Thanks to mozbhearsum)
  * Improvements to existing itertools:
      * ``ilen`` is now slightly faster. (Thanks to wbolster)
      * ``peekable`` can now prepend items to an iterable. (Thanks to diazona)

  2.5.0
  -----

  * New itertools:
      * ``distribute`` (Thanks to mozbhearsum and coady)
      * ``sort_together`` (Thanks to clintval)
      * ``stagger`` and ``zip_offset`` (Thanks to joshbode)
      * ``padded``
  * Improvements to existing itertools:
      * ``peekable`` now handles negative indexes and slices with negative
        components properly.
      * ``intersperse`` is now slightly faster. (Thanks to pylang)
      * ``windowed`` now accepts a ``step`` keyword argument.
        (Thanks to pylang)
  * Python 3.6 is now supported.

  2.4.1
  -----

  * Move docs 100% to readthedocs.io.

  2.4
  -----

  * New itertools:
      * ``accumulate``, ``all_equal``, ``first_true``, ``partition``, and
        ``tail`` from the itertools documentation.
      * ``bucket`` (Thanks to Rosuav and cvrebert)
      * ``collapse`` (Thanks to abarnet)
      * ``interleave`` and ``interleave_longest`` (Thanks to abarnet)
      * ``side_effect`` (Thanks to nvie)
      * ``sliced`` (Thanks to j4mie and coady)
      * ``split_before`` and ``split_after`` (Thanks to astronouth7303)
      * ``spy`` (Thanks to themiurgo and mathieulongtin)
  * Improvements to existing itertools:
      * ``chunked`` is now simpler and more friendly to garbage collection.
        (Contributed by coady, with thanks to piskvorky)
      * ``collate`` now delegates to ``heapq.merge`` when possible.
        (Thanks to kmike and julianpistorius)
      * ``peekable``-wrapped iterables are now indexable and sliceable.
        Iterating through ``peekable``-wrapped iterables is also faster.
      * ``one`` and ``unique_to_each`` have been simplified.
        (Thanks to coady)


  2.3
  -----

  * Added ``one`` from ``jaraco.util.itertools``. (Thanks, jaraco!)
  * Added ``distinct_permutations`` and ``unique_to_each``. (Contributed by
    bbayles)
  * Added ``windowed``. (Contributed by bbayles, with thanks to buchanae,
    jaraco, and abarnert)
  * Simplified the implementation of ``chunked``. (Thanks, nvie!)
  * Python 3.5 is now supported. Python 2.6 is no longer supported.
  * Python 3 is now supported directly; there is no 2to3 step.

  2.2
  -----

  * Added ``iterate`` and ``with_iter``. (Thanks, abarnert!)

  2.1
  -----

  * Added (tested!) implementations of the recipes from the itertools
    documentation. (Thanks, Chris Lonnen!)
  * Added ``ilen``. (Thanks for the inspiration, Matt Basta!)

  2.0
  -----

  * ``chunked`` now returns lists rather than tuples. After all, they're
    homogeneous. This slightly backward-incompatible change is the reason for
    the major version bump.
  * Added ``@consumer``.
  * Improved test machinery.

  1.1
  -----

  * Added ``first`` function.
  * Added Python 3 support.
  * Added a default arg to ``peekable.peek()``.
  * Noted how to easily test whether a peekable iterator is exhausted.
  * Rewrote documentation.

  1.0
  -----

  * Initial release, with ``collate``, ``peekable``, and ``chunked``. Could
    really use better docs.


pkgId: fc23c38eeb51242a30d788c3ef5d7750420b04d32071b84709f51d88623f4ede
name: python3-pyasn1-modules
arch: noarch
version: 0.2.4
epoch: 3
release: 7.fc32
summary: A collection of ASN.1-based protocols modules.
url: https://github.com/etingof/pyasn1-modules
rpm_license: BSD
rpm_vendor: Ilya Etingof <etingof@gmail.com> <etingof@gmail.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-pyasn1-modules-0.2.4-7.fc32.src.rpm
location_href: packages/python3-pyasn1-modules-0.2.4-7.fc32.noarch.rpm
checksum_type: sha256
description:
  A collection of ASN.1 modules expressed in form of pyasn1 classes. Includes protocols PDUs definition (SNMP, LDAP etc.) and various data structures (X.509, PKCS etc.).


pkgId: 127d4ec4421289d10ba167bcfa5ab6faed98126e538a5c3a61a363faf18d4cf4
name: python3-setuptools_scm_git_archive
arch: noarch
version: 1.0
epoch: 0
release: 10.fc32
summary: setuptools_scm plugin for git archives
url: https://github.com/Changaco/setuptools_scm_git_archive/
rpm_license: MIT
rpm_vendor: Changaco <changaco@changaco.oy.lc>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-setuptools_scm_git_archive-1.0-10.fc32.src.rpm
location_href: packages/python3-setuptools_scm_git_archive-1.0-10.fc32.noarch.rpm
checksum_type: sha256
description:
  This is a `setuptools_scm <https://pypi.python.org/pypi/setuptools_scm>`_ plugin
  that adds support for git archives (for example the ones GitHub automatically
  generates).

  Note that it only works for archives of tagged commits (because git currently
  lacks a format option equivalent to ``git describe --tags``).

  Usage
  -----

  Add ``'setuptools_scm_git_archive'`` to the ``setup_requires`` parameter in your
  project's ``setup.py`` file:

  .. code:: python

      setup(
          ...,
          use_scm_version=True,
          setup_requires=['setuptools_scm', 'setuptools_scm_git_archive'],
          ...,
      )

  Create a ``.git_archival.txt`` file with the following content::

      ref-names: $Format:%D$

  Then add this line to the ``.gitattributes`` file::

      .git_archival.txt  export-subst

  Finally, don't forget to commit these two files.


pkgId: 25e2d08e2c2fb20785b616be19e3b0d802d3fccec068177b3fb99a069ccba33c
name: python3-statsmodels
arch: src
version: 0.9.0
epoch: 0
release: 5.fc32
summary: Statistical computations and models for Python
url: http://www.statsmodels.org/
rpm_license: BSD License
rpm_vendor: Josef Perktold, Chad Fulton, Kerby Shedden <pystatsmodels@googlegroups.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
location_href: packages/python3-statsmodels-0.9.0-5.fc32.src.rpm
checksum_type: sha256
description:
  |Travis Build Status| |Appveyor Build Status| |Coveralls Coverage|

  About Statsmodels
  =================

  Statsmodels is a Python package that provides a complement to scipy for
  statistical computations including descriptive statistics and estimation
  and inference for statistical models.


  Documentation
  =============

  The documentation for the latest release is at

  http://www.statsmodels.org/stable/

  The documentation for the development version is at

  http://www.statsmodels.org/dev/

  Recent improvements are highlighted in the release notes

  http://www.statsmodels.org/stable/release/version0.9.html

  Backups of documentation are available at http://statsmodels.github.io/stable/
  and http://statsmodels.github.io/dev/.



  Main Features
  =============

  * Linear regression models:

    - Ordinary least squares
    - Generalized least squares
    - Weighted least squares
    - Least squares with autoregressive errors
    - Quantile regression
    - Recursive least squares

  * Mixed Linear Model with mixed effects and variance components
  * GLM: Generalized linear models with support for all of the one-parameter
    exponential family distributions
  * Bayesian Mixed GLM for Binomial and Poisson
  * GEE: Generalized Estimating Equations for one-way clustered or longitudinal data
  * Discrete models:

    - Logit and Probit
    - Multinomial logit (MNLogit)
    - Poisson and Generalized Poisson regression
    - Negative Binomial regression
    - Zero-Inflated Count models

  * RLM: Robust linear models with support for several M-estimators.
  * Time Series Analysis: models for time series analysis

    - Complete StateSpace modeling framework

      - Seasonal ARIMA and ARIMAX models
      - VARMA and VARMAX models
      - Dynamic Factor models
      - Unobserved Component models

    - Markov switching models (MSAR), also known as Hidden Markov Models (HMM)
    - Univariate time series analysis: AR, ARIMA
    - Vector autoregressive models, VAR and structural VAR
    - Vector error correction modle, VECM
    - exponential smoothing, Holt-Winters
    - Hypothesis tests for time series: unit root, cointegration and others
    - Descriptive statistics and process models for time series analysis

  * Survival analysis:

    - Proportional hazards regression (Cox models)
    - Survivor function estimation (Kaplan-Meier)
    - Cumulative incidence function estimation

  * Multivariate:

    - Principal Component Analysis with missing data
    - Factor Analysis with rotation
    - MANOVA
    - Canonical Correlation

  * Nonparametric statistics: Univariate and multivariate kernel density estimators
  * Datasets: Datasets used for examples and in testing
  * Statistics: a wide range of statistical tests

    - diagnostics and specification tests
    - goodness-of-fit and normality tests
    - functions for multiple testing
    - various additional statistical tests

  * Imputation with MICE, regression on order statistic and Gaussian imputation
  * Mediation analysis
  * Graphics includes plot functions for visual analysis of data and model results

  * I/O

    - Tools for reading Stata .dta files, but pandas has a more recent version
    - Table output to ascii, latex, and html

  * Miscellaneous models
  * Sandbox: statsmodels contains a sandbox folder with code in various stages of
    developement and testing which is not considered "production ready".  This covers
    among others

    - Generalized method of moments (GMM) estimators
    - Kernel regression
    - Various extensions to scipy.stats.distributions
    - Panel data models
    - Information theoretic measures

  How to get it
  =============
  The master branch on GitHub is the most up to date code

  https://www.github.com/statsmodels/statsmodels

  Source download of release tags are available on GitHub
  Patch0: numpy-buildrequires.unix2dos.diff

  https://github.com/statsmodels/statsmodels/tags

  Binaries and source distributions are available from PyPi

  http://pypi.python.org/pypi/statsmodels/

  Binaries can be installed in Anaconda

  conda install statsmodels


  Installing from sources
  =======================

  See INSTALL.txt for requirements or see the documentation

  http://statsmodels.github.io/dev/install.html

  License
  =======

  Modified BSD (3-clause)

  Discussion and Development
  ==========================

  Discussions take place on our mailing list.

  http://groups.google.com/group/pystatsmodels

  We are very interested in feedback about usability and suggestions for
  improvements.

  Bug Reports
  ===========

  Bug reports can be submitted to the issue tracker at

  https://github.com/statsmodels/statsmodels/issues

  .. |Travis Build Status| image:: https://travis-ci.org/statsmodels/statsmodels.svg?branch=master
     :target: https://travis-ci.org/statsmodels/statsmodels
  .. |Appveyor Build Status| image:: https://ci.appveyor.com/api/projects/status/gx18sd2wc63mfcuc/branch/master?svg=true
     :target: https://ci.appveyor.com/project/josef-pkt/statsmodels/branch/master
  .. |Coveralls Coverage| image:: https://coveralls.io/repos/github/statsmodels/statsmodels/badge.svg?branch=master
     :target: https://coveralls.io/github/statsmodels/statsmodels?branch=master


pkgId: 38d1301b5fa843dfaf2e80c94f688dd66184dd7e99dde284e348da371c3587da
name: python3-statsmodels-debuginfo
arch: x86_64
version: 0.9.0
epoch: 0
release: 5.fc32
summary: Debug information for package python3-statsmodels
url: http://www.statsmodels.org/
rpm_license: BSD License
rpm_vendor: Josef Perktold, Chad Fulton, Kerby Shedden <pystatsmodels@googlegroups.com>
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-statsmodels-0.9.0-5.fc32.src.rpm
location_href: packages/python3-statsmodels-debuginfo-0.9.0-5.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package python3-statsmodels.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: e7d17f6bf4327909f3b4205d240241cb86a0633877ed586ccd42215baa440306
name: python3-statsmodels-debugsource
arch: x86_64
version: 0.9.0
epoch: 0
release: 5.fc32
summary: Debug sources for package python3-statsmodels
url: http://www.statsmodels.org/
rpm_license: BSD License
rpm_vendor: Josef Perktold, Chad Fulton, Kerby Shedden <pystatsmodels@googlegroups.com>
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-statsmodels-0.9.0-5.fc32.src.rpm
location_href: packages/python3-statsmodels-debugsource-0.9.0-5.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug sources for package python3-statsmodels.
  Debug sources are useful when developing applications that use this
  package or when debugging this package.


pkgId: 212dcab4ac88d66d3d822421b11dea8b177e15f581b2400abaedeb5088ccadf7
name: python3-werkzeug
arch: noarch
version: 0.14.1
epoch: 0
release: 5.fc32
summary: The comprehensive WSGI web application library.
url: https://www.palletsprojects.org/p/werkzeug/
rpm_license: BSD
rpm_vendor: Armin Ronacher <armin.ronacher@active-4.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-werkzeug-0.14.1-5.fc32.src.rpm
location_href: packages/python3-werkzeug-0.14.1-5.fc32.noarch.rpm
checksum_type: sha256
description:
  Werkzeug
  ========

  Werkzeug is a comprehensive `WSGI`_ web application library. It began as
  a simple collection of various utilities for WSGI applications and has
  become one of the most advanced WSGI utility libraries.

  It includes:

  * An interactive debugger that allows inspecting stack traces and source
    code in the browser with an interactive interpreter for any frame in
    the stack.
  * A full-featured request object with objects to interact with headers,
    query args, form data, files, and cookies.
  * A response object that can wrap other WSGI applications and handle
    streaming data.
  * A routing system for matching URLs to endpoints and generating URLs
    for endpoints, with an extensible system for capturing variables from
    URLs.
  * HTTP utilities to handle entity tags, cache control, dates, user
    agents, cookies, files, and more.
  * A threaded WSGI server for use while developing applications locally.
  * A test client for simulating HTTP requests during testing without
    requiring running a server.

  Werkzeug is Unicode aware and doesn't enforce any dependencies. It is up
  to the developer to choose a template engine, database adapter, and even
  how to handle requests. It can be used to build all sorts of end user
  applications such as blogs, wikis, or bulletin boards.

  `Flask`_ wraps Werkzeug, using it to handle the details of WSGI while
  providing more structure and patterns for defining powerful
  applications.


  Installing
  ----------

  Install and update using `pip`_:

  .. code-block:: text

      pip install -U Werkzeug


  A Simple Example
  ----------------

  .. code-block:: python

      from werkzeug.wrappers import Request, Response

      @Request.application
      def application(request):
          return Response('Hello, World!')

      if __name__ == '__main__':
          from werkzeug.serving import run_simple
          run_simple('localhost', 4000, application)


  Links
  -----

  * Website: https://www.palletsprojects.com/p/werkzeug/
  * Releases: https://pypi.org/project/Werkzeug/
  * Code: https://github.com/pallets/werkzeug
  * Issue tracker: https://github.com/pallets/werkzeug/issues
  * Test status:

    * Linux, Mac: https://travis-ci.org/pallets/werkzeug
    * Windows: https://ci.appveyor.com/project/davidism/werkzeug

  * Test coverage: https://codecov.io/gh/pallets/werkzeug

  .. _WSGI: https://wsgi.readthedocs.io/en/latest/
  .. _Flask: https://www.palletsprojects.com/p/flask/
  .. _pip: https://pip.pypa.io/en/stable/quickstart/


pkgId: 154bed6baf91e56a4b92eb538c37fdd3915ebe9696888102ac8b4a047fe5db44
name: python3-widgetsnbextension
arch: noarch
version: 3.4.2
epoch: 0
release: 8.fc32
summary: IPython HTML widgets for Jupyter
url: http://ipython.org
rpm_license: BSD
rpm_vendor: IPython Development Team <ipython-dev@scipy.org>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: python3-widgetsnbextension-3.4.2-8.fc32.src.rpm
location_href: packages/python3-widgetsnbextension-3.4.2-8.fc32.noarch.rpm
checksum_type: sha256
description:
  .. image:: https://img.shields.io/pypi/v/widgetsnbextension.svg
     :target: https://pypi.python.org/pypi/widgetsnbextension/
     :alt: Version Number

  .. image:: https://img.shields.io/pypi/dm/widgetsnbextension.svg
     :target: https://pypi.python.org/pypi/widgetsnbextension/
     :alt: Number of PyPI downloads

  Interactive HTML Widgets
  ========================

  Interactive HTML widgets for Jupyter notebooks.

  Usage
  =====

  Install the corresponding package for your kernel.  i.e. Python users would also
  install `ipywidgets`.  Refer to that package's documentation for usage
  instructions.


pkgId: 3686b4cc4e2e0141b61656a5b2b852090cd0adecf79603c56380f0f99473b7d1
name: qubes-arbitrary-network-topology
arch: noarch
version: 0.0.19
epoch: 0
release: 1.fc32
summary: Turn your Qubes OS into an arbitrary network topology host
url: https://github.com/Rudd-O/qubes-arbitrary-network-topology
rpm_license: GPLv2+
rpm_group: Unspecified
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: qubes-arbitrary-network-topology-0.0.19-1.fc32.src.rpm
location_href: packages/qubes-arbitrary-network-topology-0.0.19-1.fc32.noarch.rpm
checksum_type: sha256
description:
  This package lets you create arbitrary network topologies in your
  Qubes OS system.  Install this in the TemplateVM of your AppVMs
  that will participate of the network topology.  Then install the
  companion qubes-core-admin-addon-arbitrary-network-topology package
  in your dom0.

  Please see README.md enclosed in the package for instructions on how to use
  this software.


pkgId: 97c1708223a2ce11a36055ebe98100ec3b2baef65c0f9837ffbfa3f29c9838ca
name: qubes-core-admin-addon-arbitrary-network-topology
arch: noarch
version: 0.0.19
epoch: 0
release: 1.fc32
summary: dom0 administrative extension for Qubes arbitrary network topology
url: https://github.com/Rudd-O/qubes-arbitrary-network-topology
rpm_license: GPLv2+
rpm_group: Unspecified
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: qubes-arbitrary-network-topology-0.0.19-1.fc32.src.rpm
location_href: packages/qubes-core-admin-addon-arbitrary-network-topology-0.0.19-1.fc32.noarch.rpm
checksum_type: sha256
description:
  This package lets you create arbitrary network topologies in your
  Qubes OS system.  Install this in your dom0.  Then install the
  companion qubes-arbitrary-network-topology package in the TemplateVM
  of your AppVMs that will participate of the network topology.

  Please see README.md enclosed in the package for instructions on how to use
  this software.


pkgId: 14532c641275d51e72ca1e65e94716c32ffd3fc28617a8e678e6dd33dc30a86c
name: qubes-core-admin-addon-network-server
arch: noarch
version: 0.0.11
epoch: 0
release: 18.fc32
summary: dom0 administrative extension for Qubes network server
url: https://github.com/Rudd-O/qubes-network-server
rpm_license: GPLv2+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
rpm_sourcerpm: qubes-network-server-0.0.11-18.fc32.src.rpm
location_href: packages/qubes-core-admin-addon-network-server-0.0.11-18.fc32.noarch.rpm
checksum_type: sha256
description:
  This package lets you turn your Qubes OS into a network server.  Install this
  in your dom0.  Then install the companion qubes-network-server package in the
  TemplateVM of your NetVM.

  Please see README.md enclosed in the package for instructions on how to use
  this software.


pkgId: 1a31828fa2e8a6c60cf81a2edf11fc9f43cd5425a105954f1e29997493febceb
name: qubes-network-server
arch: noarch
version: 0.0.11
epoch: 0
release: 18.fc32
summary: Turn your Qubes OS into a network server
url: https://github.com/Rudd-O/qubes-network-server
rpm_license: GPLv2+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
rpm_sourcerpm: qubes-network-server-0.0.11-18.fc32.src.rpm
location_href: packages/qubes-network-server-0.0.11-18.fc32.noarch.rpm
checksum_type: sha256
description:
  This package lets you turn your Qubes OS into a network server.  Install this
  in the TemplateVM of your NetVM.  Then install the companion
  qubes-core-admin-addon-network-server package in your dom0.

  Please see README.md enclosed in the package for instructions on how to use
  this software.


pkgId: 433d9ef3e75e80fee5fda42086bc2c47799f5062553712cdf9c5d94c23e7b80e
name: qubes-pass
arch: noarch
version: 0.0.21
epoch: 0
release: 17.fc32
summary: Inter-VM pass password management for Qubes OS AppVMs and StandaloneVMs
url: https://github.com/Rudd-O/qubes-pass
rpm_license: GPLv3+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
rpm_sourcerpm: qubes-pass-0.0.21-17.fc32.src.rpm
location_href: packages/qubes-pass-0.0.21-17.fc32.noarch.rpm
checksum_type: sha256
description:
  This package lets you setup a safe password management VM and then
  manage the password store remotely from other VMs.  You are meant to
  install this package on the VM or template where you want to access
  and manage your password store.


pkgId: b9b0c5a6a56815cc3d9a002df82c25ee2ad448f78133887146634881fa38cefa
name: qubes-pass-dom0
arch: noarch
version: 0.0.21
epoch: 0
release: 17.fc32
summary: Policy package for Qubes OS dom0s that arbitrates qubes-pass
url: https://github.com/Rudd-O/qubes-pass
rpm_license: GPLv3+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
rpm_sourcerpm: qubes-pass-0.0.21-17.fc32.src.rpm
location_href: packages/qubes-pass-dom0-0.0.21-17.fc32.noarch.rpm
checksum_type: sha256
description:
  This package contains the Qubes OS execution policy for the qubes-pass package.
  You are meant to install this package on the dom0 of the machine where you
  have VMs that have the qubes-pass package installed.


pkgId: 4c30054dfd8d6f3d497fc8c7dbd402285cf6dcdc9dd551cf7be09c9331d4b3a7
name: qubes-pass-service
arch: noarch
version: 0.0.21
epoch: 0
release: 17.fc32
summary: Service package for Qubes OS dom0s that services qubes-pass
url: https://github.com/Rudd-O/qubes-pass
rpm_license: GPLv3+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
rpm_sourcerpm: qubes-pass-0.0.21-17.fc32.src.rpm
location_href: packages/qubes-pass-service-0.0.21-17.fc32.noarch.rpm
checksum_type: sha256
description:
  This package lets you serve a safe password store to other VMs.
  You are meant to install this package on the VM or template where
  you want to keep your password store safe.


pkgId: e15e8c77f77fd2b4bdca359996aa073b0cad52e3c114bf27bc363e7b64ef9b0a
name: qubes-shared-folders
arch: noarch
version: 0.0.1
epoch: 0
release: 1.fc32
summary: Inter-VM folder sharing via Plan 9 filesystem
url: https://github.com/Rudd-O/qubes-shared-folders
rpm_license: GPLv2+
rpm_group: Unspecified
rpm_buildhost: jenkins-chroot.local
rpm_sourcerpm: qubes-shared-folders-0.0.1-1.fc32.src.rpm
location_href: packages/qubes-shared-folders-0.0.1-1.fc32.noarch.rpm
checksum_type: sha256
description:
  This package offers a collection of programs that allow users to
  securely mount folders from one qube into another qube.


pkgId: 8dc615be0dfb46c7a094938e934054dc515e4a3d2bd0d0271544e168f14d7cc8
name: qubes-shared-folders-dom0
arch: noarch
version: 0.0.1
epoch: 0
release: 1.fc32
summary: Policy package for Qubes OS dom0s that arbitrates qubes-shared-folders
url: https://github.com/Rudd-O/qubes-shared-folders
rpm_license: GPLv2+
rpm_group: Unspecified
rpm_buildhost: jenkins-chroot.local
rpm_sourcerpm: qubes-shared-folders-0.0.1-1.fc32.src.rpm
location_href: packages/qubes-shared-folders-dom0-0.0.1-1.fc32.noarch.rpm
checksum_type: sha256
description:
  This package contains the Qubes OS execution policy for the qubes-shared-folders package.
  You are meant to install this package on the dom0, if you installed the
  qubes-shared-folders package installed on any of your qubes.


pkgId: e7c2bc4591d3a75c5aaba5a96e74ddeb73fd845b51a8da1e737b402485c609be
name: run-in-gui
arch: noarch
version: 0.0.9
epoch: 0
release: 1.fc32
summary: Tools to run (possibly graphical) programs in logged-in user sessions on modern Linux distributions
url: http://github.com/Rudd-O/run-in-gui
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: run-in-gui-0.0.9-1.fc32.src.rpm
location_href: packages/run-in-gui-0.0.9-1.fc32.noarch.rpm
checksum_type: sha256
description:
  Run in GUI (run-in-gui)
  ============================

  | Donate to support this free software |
  |:------------------------------------:|
  | <img width="164" height="164" title="" alt="" src="doc/bitcoin.png" /> |
  | [1DmVQkuY1zjP6ZiPi1QJgSowHtR8afBDMS](bitcoin:1DmVQkuY1zjP6ZiPi1QJgSowHtR8afBDMS) |

  This project contains two programs that assist you in executing programs
  in a separate desktop session (defined by the environment variables of any
  program executing in that session), and then switching to the session in
  real-time as the program executes.  It's useful to start GUI programs from
  cron that need a graphical display and/or audio access.

  Why is this necessary?
  ----------------------

  Lots of people ask me why this is useful, or some other variant of the same
  question, such as "Can't I just `DISPLAY=:0` in my crontab?"

  Well, because of the way that Linux has evolved, nowadays it's very hard to
  get certain computer programs to do things that were trivial in the past.
  Lots of GUI programs now depend on a wide array of session daemons and
  other services, such as:

  * X11 authentication,
  * D-Bus,
  * KWallet,
  * GnuPG agents,
  * SSH agents,
  * KIO services,
  * PulseAudio.

  These services are normally set up properly at the start of (and solely
  in the context of) your GUI session, but entirely unavailable for use in
  crontabs and other non-GUI shells, nominally disassociated with your
  desktop session.

  For example: getting your music player to play a list of songs to wake you
  up -- unless you're running the program straight from a terminal in your
  desktop session's GUI, it won't actually work; either the program just
  won't run, or the audio will be corked.

  How this works
  --------------

  So what we do in `run-in-gui` is simple: ''we cheat'' by stealing the
  necessary information from other programs running in your desktop session,
  and using it to recreate an environment in which we run your program.

  Caveat: of course, this program ''still'' requires you to be logged in. If
  your session isn't active, `run-in-gui` will take the liberty to switch to
  your inactive session, activating -- but, if locked, not unlocking -- it,
  and then running your program.

  Tools included in this set
  --------------------------

  This package contains several tools:

  1. `run-in-env-of`: a tool that runs the command of your choice in the
      environment of the PID of your choice.  If run as root, it can
     `setuid()` to the user and group of that PID.
  2. `run-in-gui`: a tool that sorts out a desktop session you're running
     then uses run-in-env-of to execute the command on your choice under
     that desktop session.  Prior to the execution of that program, it
     switches to the selected desktop session, to enable hardware access
     to devices that would otherwise be blocked (e.g. audio).

  What you need to have before using this package
  -----------------------------------------------

  * Python 2.7 on your local machine
  * `loginctl` fully operational
  * `/proc` mounted

  Installation
  ------------

  You will need to install this package on your local machine.

  You can install this package directly from PyPI using pip::

      pip install run-in-gui

  If you are on an RPM-based distribution, build an RPM from the source package
  and install the resulting RPM::

      python setup.py bdist_rpm

  Otherwise, just use the standard Python installation system::

      python setup.py install

  You can also run it directly from the unpacked source directory::

      export PYTHONPATH="$PWD"/src
      ./<program> <parameters>

  Usage
  -----

  Say, for example, you want to run Amarok from a crontab, but you want Amarok
  to start on your logged-in desktop session.  No problem: you can stick this
  into your crontab:

      20 4 * * * /usr/local/run-in-gui/bin/run-in-gui amarok -p Toke\ up.m3u

  As you can see, at exactly 4:20 AM, Amarok will be executed in your desktop
  session, and will start playing the playlist `Toke up.m3u` in your home
  directory.

  You can also do the exact same thing from an `at` job:

      echo /path/to/run-in-gui amarok -p Matanga.m3u | at 5:45

  If, for some reason, the program won't start, check your mail folder in
  `/var/mail/$USERNAME`, where cron traditionally deposits crontab output.


pkgId: 0df8674adce56993d707c51e7b4c8d59b5f242b6b932599750fe3add5bb9284a
name: seedboxtools
arch: noarch
version: 1.4.10
epoch: 0
release: 1.fc32
summary: A tool to automate downloading finished torrents from a seedbox
url: http://github.com/Rudd-O/seedboxtools
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: seedboxtools-1.4.10-1.fc32.src.rpm
location_href: packages/seedboxtools-1.4.10-1.fc32.noarch.rpm
checksum_type: sha256
description:
  Seedbox tools (seedboxtools)
  ============================

  | Donate to support this free software |
  |:------------------------------------:|
  | <img width="164" height="164" title="" alt="" src="doc/bitcoin.png" /> |
  | [12cXnYY3wabbPmLpS7ZgACh4mBawrXdndk](bitcoin:12cXnYY3wabbPmLpS7ZgACh4mBawrXdndk) |

  The seedbox tools will help you download all those Linux ISOs that you
  downloaded on your remote seedbox (whether it's a Transmission Web, or
  TorrentFlux-b4rt, or a PulsedMedia seedbox) 100% automatically, without any
  manual intervention on your part.

  With this program installed on your home computer, all you need to do is
  simply start a torrent in your seedbox, from anywhere you are; then, when
  you get back home, all your downloads will be fully downloaded at home,
  ready to use and enjoy.

  Tools included in this set
  --------------------------

  This package contains several tools:

      1. leechtorrents: a tool that leeches finished downloads from a torrent
         seedbox to your local computer.
      2. configleecher: a configuration wizard to set up the clients to work
         properly against your seedbox.
      3. uploadtorrents: a tool that lets you queue up a torrent or magnet link
         for download on your seedbox.

  What you need to have before using this package
  -----------------------------------------------

      - Python 2.7 on your local machine
      - Python iniparse installed there
      - Python requests installed there, version 0.11.1 or higher (with SSL support)
      - a seedbox running TorrentFlux-b4rt or Transmission Web + API, or
        a PulsedMedia ruTorrent seedbox from PulsedMedia.com
      - an SSH server on your seedbox
      - an SSH client on your local machine
      - a public key-authenticated user account in the seedbox, so that your user
        can log in without passwords and can read the torrents and downloads
        directories in the seedbox
      - rsync installed on both machines
      - if you are using TorrentFlux-b4rt on your seedbox:
          * the command torrentinfo-console from the BitTorrent package, installed
            on the seedbox
          * the command fluxcli installed and operational on the seedbox
      - if you are using Transmission on your seedbox:
          * the command transmission-remote from the Transmission package,
            installed on your local machine
          * the API server port open so that transmission-remote can query it
      - if you are using a PulsedMedia seedbox, you don't need to do anything

  Installation
  ------------

  You will need to install this package on your local machine.

  You can install this package directly from PyPI using pip::

      pip install seedboxtools

  If you are on an RPM-based distribution, build an RPM from the source package
  and install the resulting RPM::

      python setup.py bdist_rpm

  Otherwise, just use the standard Python installation system::

      python setup.py install

  You can also run it directly from the unpacked source directory::

      export PYTHONPATH=src
      bin/leechtorrents --help

  Configuration
  -------------

  The tools require some configuration after installation.  There is a nifty
  configuration wizard that will set the configuration file up.  Run it and
  answer a few questions::

      configleecher

  The script will ask you for the necessary configuration values before you can
  run the tools here.  You should run this wizard on the machine where you'll
  be running `leechtorrents` (see below).

  Note: Both TorrentFlux and Transmission protect their download and torrent
  directories using permissions.  You should become part of the UNIX group
  they use to protect those directories, and change the permissions
  accordingly so you have at least read and list permissions (rx).

  Downloading finished torrents with the leecher tool
  ---------------------------------------------------

  The leecher tool will contact your seedbox and ask for a listing of finished
  torrents, then download them locally to the directory you chose during
  configuration.  There are various ways to run the script:

  * manually on a terminal window
  * with cron
  * in a systemd unit file as a service

  In all cases, the leecher tool will figure out finished torrents, download
  them to the download folder you configured during the `configleecher` stage,
  then create a file named `.<downloaded file>.done` within the download folder,
  to indicate that the torrent has finished downloading.  This marker helps the
  leecher tool remember which torrents were fully downloaded, so that it doesn't
  attempt to download them yet again.

  Manually
  ________

  In your terminal program of choice, just run the command::

      leechtorrents

  There are various options you can supply to the program to change its
  behavior, such as enabling periodic checks and logging to a file. Run
  `leechtorrents -h` to see the options.

  With cron
  ~~~~~~~~~

  Put this in your crontab to run it every minute::

      * * * * * leechtorrents -Dql

  `leechtorrents` will daemonize itself, write to its default log file (which
  you could change with another command line option), and be quiet if no work
  needs to be done.  Locking prevents multiple `leechtorrents` processes from
  running simultaneously.

  With systemd
  ~~~~~~~~~~~~

  Create a unit file::

      
      

      [Unit]
      Description=Torrentleecher
      After=network.target

      [Service]
      Type=simple
      ExecStart=/usr/bin/leechtorrents -g .torrentleecher.log -ql -t 30
      User=<YOUR_USERNAME_GOES_HERE>
      Restart=always

      [Install]
      WantedBy=network.target

  Then run as root::

      systemctl daemon-reload
      systemctl enable leechtorrents.service
      systemctl start leechtorrents.service

  Removing completed torrents once they have been fully downloaded
  ----------------------------------------------------------------

  The leecher tool has the ability to remove completed downloads that aren't
  seeding from your seedbox.  Just pass the command line option `-r` to the
  leecher tool `leechtorrents`, and it will automatically remove from the
  seedbox each torrent it successfully downloads, so long as the torrent
  is not seeding anymore.  This feature helps conserve disk space in your
  seedbox.  Note that, once a torrent has been removed from the seedbox,
  its corresponding `.<downloaded file>.done` file on the download folder
  will be eliminated, to clear up clutter in the download folder.

  Example::

      leechtorrents -r

  Running a program after a torrent is finished downloading
  ---------------------------------------------------------

  The leecher tool has the capacity to run a program (non-interactively) right
  after a download is completed, and will also pass the full path to the file
  or directory that was downloaded to the program.  This program will be run
  right after the download is done, and (if you have enabled said option)
  before the torrent is removed from the seedbox, and its marker file removed
  from the download folder.

  To activate the running of the post-download program, pass the option `-s`
  followed by the path to the program you want to run.

  Here is an example that runs a particular program to process downloads::

      leechtorrents -s /usr/local/bin/blend-linux-distributions

  In this example, right after your favorite Linux distribution torrent
  (which surely is `Fedora-22.iso`) is done and saved to your download folder
  `/srv/seedbox`, `leechtorrents` will execute the following command line::

      /usr/local/bin/blend-linux-distributions /srv/seedbox/Fedora-22.iso

  The standard output and standard error of the program are passed to the
  standard output and standard error of `leechtorrents`, which may be your
  terminal, a logging service, or the log file set aside for logging purposes
  by the `leechtorrents` command line parameter `-l`.  Standard input will
  be nullified, so no option for interacting with the program will exist.

  Note that your program will only ever execute once per downloaded torrent.
  Also note that the return value of your program will be ignored.  Finally,
  please note that if your program doesn't finish, this will block further
  downloads, so make sure to equip your program with a timeout (perhaps using
  `SIGALRM` or such mechanisms).

  If you want to run a shell or other language script against the downloaded
  file or directory, you are advised to write a script file and pass that as
  the argument to `-s`, then use the first argument to the script file as
  the path to the downloaded file (it's usually `$1` in sh-like languages,
  like it is `sys.argv[1]` in Python).

  How to upload torrents to your seedbox
  --------------------------------------

  The `uploadtorrents` command-line tool included in this package will upload the
  provided torrent files or magnet links to your seedbox::

      uploadtorrents TORRENT [TORRENT ...]

  This tool currently only supports PulsedMedia clients.


pkgId: 629629a0fafb56f6e85d9f5ae07e988fb171fbab1a9dfa93e89b9d4adb7f9999
name: simplegtd
arch: noarch
version: 0.0.22
epoch: 0
release: 1.fc32
summary: Manage your to-do list using the Getting Things Done system.
url: https://pypi.org/project/simplegtd/
rpm_license: GPLv3+
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: simplegtd-0.0.22-1.fc32.src.rpm
location_href: packages/simplegtd-0.0.22-1.fc32.noarch.rpm
checksum_type: sha256
description:
  Simple GTD: manage your TODO.txt
  ================================

  Simple GTD lets you manage your to-do list using the Getting Things Done system.

  Skip below for usage and installation instructions.

  Features
  --------

  **Sync-ready and sync-friendly**

  While Simple GTD does not have any built-in sync features -- and has no plans to gain them -- it supports any sync tool you want to use, from Git to Syncthing to Dropbox.  Incoming changes to your to-do file are reflected in the user interface immediately.  The author has verified that syncing `todo.txt` to and from Simpletask Cloudless works perfectly (using Syncthing as the sync mechanism).

  The algorithm used to persist and detect state changes in the to-do file is robust and efficient.  When Simple GTD detects external changes to your to-do file, only the portions of the file that changed are reloaded.  When you make changes to your to-do file in Simple GTD, Simple GTD saves the changes immediately, letting your sync program do its job right away.

  **Keyboard- and mouse-friendly**

  Entering new tasks and managing existing tasks with Simple GTD is quick and easy -- a single keystroke to add a task, and a single keystroke to edit an existing task.  Most of the standard shortcut keys you've learned work exactly as intended.

  **Fast**

  The program is consciously developed to reduce the overhead of common operations like inserting / rearranging / filtering your to-do lists.

  **Multi-lists**

  Unlike most to-do apps, you can manage multiple lists with Simple GTD.  Exiting the app and reopening the app again will open all lists you had open before.  Even window sizes are remembered per list, so short and long lists won't be a chore to manage.

  Usage
  -----

  The application is fairly simple to use.  When you start it, an empty window will pop up.  Click on the *Help* icon in the header bar to see the shortcut keys you can use to manage your tasks.  The standard keyboard shortcuts will work well.

  By default, the application will store your `todo.txt` file in its hidden data directory (on Linux, `~/.local/share/simplegtd/`) within your home folder.  You can, however, change that -- use the header bar Open icon to select / create a to-do file of your choice anywhere you want.  Simple GTD will then open a new window with the file.  Now close the other window -- Simple GTD will now remember which files you have opened.

  The application will remember multiple windows with different files open as well.  If you quit the application (using Quit in the toolbar or the keyboard combination) instead of closing windows one-by-one, next time you run it, Simple GTD will reopen the files you'd had open first.

  Installation
  ------------

  Ensure your system has the necessary requirements:

  * Python 3
  * GTK+ 3
  * the GTK+ Python 3 bindings (pygobject3)
  * the PyXDG Python 3 module (pyxdg)
  * libhandy 0.x

  * Install from PyPI: `pip3 install --user simplegtd`
  * Install as RPM: download / unpack the source and run `python3 setup.py bdist_rpm` in the source-unpacked folder, then install the RPM from the `dist/` folder.
  * Install on your system: download / unpack the source and run `python3 setup.py install` in the source-unpacked folder.
  * Run directly from the source: download / unpack the source and run `bin/simplegtd` from the source-unpacked folder.

  All methods work equally well, but only the RPM installation method is guaranteed to install a desktop menu icon for the application.


pkgId: fc4490bf0fa899229eea97194d2460c061a3498d5fb715b2c689fa2a1009d8d5
name: snmp_exporter
arch: src
version: 0.17.0
epoch: 0
release: 2.fc32
summary: Prometheus SNMP exporter.
url: https://github.com/prometheus/snmp_exporter
rpm_license: ASL 2.0
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
location_href: packages/snmp_exporter-0.17.0-2.fc32.src.rpm
checksum_type: sha256
description:
  This is an exporter that exposes information gathered from SNMP for use by the Prometheus monitoring system.


pkgId: c4d375cc5ea66a86668be8bf764dbfb22274ddba3bad4965db34e5c2a3b8a0e0
name: ssconverter
arch: noarch
version: 0.1.2
epoch: 0
release: 1.fc32
summary: A program to convert to CSV specific sheets of an OpenOffice / LibreOffice spreadsheet
url: http://github.com/Rudd-O/ssconverter
rpm_license: LGPLv2.1+
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: ssconverter-0.1.2-1.fc32.src.rpm
location_href: packages/ssconverter-0.1.2-1.fc32.noarch.rpm
checksum_type: sha256
description:
  ssconverter
  ============================

  This is a very small program, maintained and ported to Python 3, that
  converts specific sheets of OpenOffice / LibreOffice spreadsheets
  to CSV.

  Its name is ssconverter.  Its original  and current  purpose is to batch-convert any number of spreadsheets from OpenOffice or LibreOffice into CSV files, with a twist: unlike unoconv, it lets you specify which sheet of the many possible sheets in the spreadsheet file you want to convert.  It's invaluable to speed up batch conversion of CSV files.

  Another feature not present in the original is the ability to enable macros and recalculate the spreadsheet right before exporting it to CSV.  This is useful for people who have macro-based formulas in their spreadsheets, which would otherwise export with #VALUE! in every cell position where a macro-based formula was entered.

  Installation
  ------------

  Clone the source into a directory on your computer.

  Open a terminal and navigate to that directory.

  Make an RPM package which you can install by running

  ```
  python3 setup.py bdist_rpm
  ```

  in a terminal window.

  Tnstall the created `noarch` RPM inside the `dist/` folder.

  Alternatively, you can install it using `python setup.py install`.

  Usage
  -----

  Run the program `ssconverter` without options to get help.

  Credits
  -------

  This program [originated on Linux Journal](https://www.linuxjournal.com/content/convert-spreadsheets-csv-files-python-and-pyuno-part-1v2).


pkgId: 826e826a007ea454b67496211308ed1f01037ed63fe3f6e520af190b7867d3de
name: takeown
arch: src
version: 0.0.11
epoch: 0
release: 1.fc32
summary: A tool to delegate file ownership to non-administrators
url: https://github.com/Rudd-O/takeown
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O)
rpm_group: System administration tools
rpm_buildhost: qubes-chroot
location_href: packages/takeown-0.0.11-1.fc32.src.rpm
checksum_type: sha256
description:
  takeown is a simple command-line tool that allows non-administrators to take
  ownership of files they do not own, so long as the administrator has set
  appropriate policy to allow that.


pkgId: 9bdae79c7f28e5c0cc454958820ad83b77d94b5b435e1bd20b7b8b5b10fd60d3
name: takeown-debuginfo
arch: x86_64
version: 0.0.11
epoch: 0
release: 1.fc32
summary: Debug information for package takeown
url: https://github.com/Rudd-O/takeown
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O)
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: takeown-0.0.11-1.fc32.src.rpm
location_href: packages/takeown-debuginfo-0.0.11-1.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package takeown.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: 64760ff103d8fd7dcce955268521b4ed00ec14d743d650941c87d6c222a7aad5
name: takeown-debugsource
arch: x86_64
version: 0.0.11
epoch: 0
release: 1.fc32
summary: Debug sources for package takeown
url: https://github.com/Rudd-O/takeown
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O)
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: takeown-0.0.11-1.fc32.src.rpm
location_href: packages/takeown-debugsource-0.0.11-1.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug sources for package takeown.
  Debug sources are useful when developing applications that use this
  package or when debugging this package.


pkgId: ce346f46527eea6525c464b7206db970a2478d69ace6b4a19f1614cacfa1ce5c
name: wol-monitor
arch: noarch
version: 0.0.1
epoch: 0
release: 1.fc32
summary: Monitor for Wake-on-LAN packets.
url: https://github.com/Rudd-O/wol-monitor
rpm_license: GPLv2+
rpm_group: Unspecified
rpm_buildhost: qubes-chroot
rpm_sourcerpm: wol-monitor-0.0.1-1.fc32.src.rpm
location_href: packages/wol-monitor-0.0.1-1.fc32.noarch.rpm
checksum_type: sha256
description:
  This program runs as a service listening on ports 9 and 40000 (UDP), then
  when a message arrives on any of those ports (traditionally Wake-on-LAN
  messages), it reacts by writing to a well-known socket in the local
  file system.


pkgId: 942f3acb931d005f63f83c5c22e8fb1b72bb17a171b17fcf84bba75371bb622e
name: youtube-dl-helper
arch: noarch
version: 0.0.10
epoch: 0
release: 12.fc32
summary: A tool to automate YouTube downloads via drag and drop
url: http://github.com/Rudd-O/youtube-dl-helper
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: youtube-dl-helper-0.0.10-12.fc32.src.rpm
location_href: packages/youtube-dl-helper-0.0.10-12.fc32.noarch.rpm
checksum_type: sha256
description:
  YouTube download helper
  =======================

  Drag and drop URLs from your browser to this application to download YouTube
  videos using `youtube-dl`.

  Requires `youtube-dl` installed in your system, as well as GNOME terminal,
  or Konsole.

  To build a package you can install on your system: `python3 setup.py bdist_rpm`.


pkgId: 48d1e055f6851ca6c3423888bd7858551a0970d1eaf65bdea3ec39292c9fae4d
name: youtube-dl-helper
arch: noarch
version: 0.0.12
epoch: 0
release: 14.fc32
summary: A tool to automate YouTube downloads via drag and drop
url: http://github.com/Rudd-O/youtube-dl-helper
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: youtube-dl-helper-0.0.12-14.fc32.src.rpm
location_href: packages/youtube-dl-helper-0.0.12-14.fc32.noarch.rpm
checksum_type: sha256
description:
  YouTube download helper
  =======================

  Drag and drop URLs from your browser to this application to download YouTube
  videos using `youtube-dl`.

  Requires `youtube-dl` installed in your system and in your `PATH`, as well as GNOME
  terminal, or Konsole5.

  To build a package you can install on your system: `python3 setup.py bdist_rpm`.


pkgId: 69e9b8c9c1807646d2bd163711d59c589ba065f52c4d24c7e51b14c9e3e12070
name: zfs-debuginfo
arch: x86_64
version: 0.8.0
epoch: 0
release: 0.132.80437a04d.fc32
summary: Debug information for package zfs
url: https://zfsonlinux.org/
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-0.8.0-0.132.80437a04d.fc32.src.rpm
location_href: packages/zfs-debuginfo-0.8.0-0.132.80437a04d.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package zfs.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: a81e72cd44ebd22ad36a47389fa35d86d3c181f58ea6bea62250eb5bb5b9d914
name: zfs-debugsource
arch: x86_64
version: 0.8.0
epoch: 0
release: 0.132.80437a04d.fc32
summary: Debug sources for package zfs
url: https://zfsonlinux.org/
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-0.8.0-0.132.80437a04d.fc32.src.rpm
location_href: packages/zfs-debugsource-0.8.0-0.132.80437a04d.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug sources for package zfs.
  Debug sources are useful when developing applications that use this
  package or when debugging this package.


pkgId: 3b081d3aa693db2e02ce89bc101830f152750196846afaa978a0873876d485d4
name: zfs-test-debuginfo
arch: x86_64
version: 0.8.0
epoch: 0
release: 0.132.80437a04d.fc32
summary: Debug information for package zfs-test
url: https://zfsonlinux.org/
rpm_license: CDDL
rpm_group: Development/Debug
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-0.8.0-0.132.80437a04d.fc32.src.rpm
location_href: packages/zfs-test-debuginfo-0.8.0-0.132.80437a04d.fc32.x86_64.rpm
checksum_type: sha256
description:
  This package provides debug information for package zfs-test.
  Debug information is useful when developing applications that use this
  package or when debugging this package.


pkgId: 0bfb2fdca7edb834b016c185625fb46f5d666a69e431ac138b754dbba53a2eda
name: zfs-tools
arch: noarch
version: 0.5.1
epoch: 0
release: 1.fc32
summary: ZFS synchronization and snapshotting tools
url: http://github.com/Rudd-O/zfs-tools
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: qubes-chroot
rpm_sourcerpm: zfs-tools-0.5.1-1.fc32.src.rpm
location_href: packages/zfs-tools-0.5.1-1.fc32.noarch.rpm
checksum_type: sha256
description:
  | Donate to support this free software |
  |:------------------------------------:|
  | <img width="164" height="164" title="" alt="" src="doc/bitcoin.png" /> |
  | [1Cw9nZu9ygknussPofMWCzmSMveusTbQvN](bitcoin:1Cw9nZu9ygknussPofMWCzmSMveusTbQvN) |

  The ZFS backup tools will help you graft an entire ZFS pool as a filesystem
  into a backup machine, without having to screw around snapshot names or
  complicated shell commands or crontabs.

  The utilities let you do this:

  1. zfs-shell:
     a shell that allows remote ZFS administration and nothing more

  3. zsnap:
     a command that snapshots a dataset or pool, then deletes old snapshots

  4. zreplicate
     a command that replicates an entire dataset tree using ZFS replication
     streams.  Best used in combination with zsnap as in:

     - zsnap on the local machine
     - zreplicate from the local machine to the destination machine

     Obsolete snapshots deleted by zsnap will be automatically purged on
     the destination machine by zreplicate, as a side effect of using
     replication streams.  To inhibit this, use the
     --no-replication-stream option.

     Run `zreplicate --help` for a compendium of options you may use.

  5. zbackup:
     a command to snapshot and replicate filesystems according to their user properties.
     This uses zsnap and zreplicate to do the work, which is all driven by properties.
     For details, see this [further description of zbackup](doc/README-zbackup.md).

  The repository, bug tracker and Web site for this tool is at [http://github.com/Rudd-O/zfs-tools](http://github.com/Rudd-O/zfs-tools).  Comments to me through rudd-o@rudd-o.com.



  Setup is rather complicated.  It assumes that you already have ZFS running
  and vaults on both the machine you're going to back up and the machine that
  will be receiving the backup.



  - Install the zfs-shell command
    `cp zfs-shell /usr/local/sbin`
    `chmod 755 /usr/local/sbin/zfs-shell`
    `chown root.root /usr/local/sbin/zfs-shell`

  - Create a user with a home directory and shell `zfs-shell`
    `useradd -rUm -b /var/lib -s /usr/local/sbin/zfs-shell zfs`

  - Let `sudo` know that the new user can run the zfs command
    `zfs ALL = NOPASSWD: /usr/local/sbin/zfs`
    (ensure you remove the `requiretty` default on `/etc/sudoers`)
    (check `sudoers.zfs-tools` in `contrib/` for an example)

  - Set up a cron job to run `zsnap` as frequently as you want to,
    snapshotting the dataset you intend to replicate.



  - Set up public key authentication for SSH so the backup machine
    may log as the user `zfs` (as laid out above) in the machine to
    be backed up.

  - Create a dataset to receive the backup stream.

  - Set up a cron job to fetch the dataset snapshotted by zsnap
    from the remote machine into the newly created dataset.  You
    will use `zreplicate` for that (see below for examples).

  - After the first replication, you may want to set the `mountpoint`
    attributes on the received datasets so they do not automount
    on the backup machine.



  If all went well, you should be able to do this without issue:

  (on the machine to back up)

      [root@peter]
      zsnap senderpool

  (on the machine to receive)

      [root@paul]
      zfs create receiverpool/senderpool # <--- run this ONLY ONCE
      zreplicate -o zfs@paul:senderpool receiverpool/senderpool
      
      

  (on the machine to back up)

      [root@peter]
      zsnap senderpool

  (on the machine to receive)

      [root@paul]
      zreplicate -o zfs@paul:senderpool receiverpool/senderpool
      
      

  And that's it, really.


pkgId: ecac97d8a5a4fe4cb0c6f89fd9caa45c4906c6223790e425856ef7c25e1d56c3
name: zfs-tools
arch: noarch
version: 0.6.3
epoch: 0
release: 1.fc32
summary: ZFS synchronization and snapshotting tools
url: http://github.com/Rudd-O/zfs-tools
rpm_license: GPL
rpm_vendor: Manuel Amador (Rudd-O) <rudd-o@rudd-o.com>
rpm_group: Development/Libraries
rpm_buildhost: jenkins-chroot
rpm_sourcerpm: zfs-tools-0.6.3-1.fc32.src.rpm
location_href: packages/zfs-tools-0.6.3-1.fc32.noarch.rpm
checksum_type: sha256
description:
  | Donate to support this free software |
  |:------------------------------------:|
  | <img width="164" height="164" title="" alt="" src="doc/bitcoin.png" /> |
  | [1Cw9nZu9ygknussPofMWCzmSMveusTbQvN](bitcoin:1Cw9nZu9ygknussPofMWCzmSMveusTbQvN) |

  The ZFS backup tools will help you graft an entire ZFS pool as a filesystem
  into a backup machine, without having to screw around snapshot names or
  complicated shell commands or crontabs.

  The utilities let you do this:

  1. zfs-shell:
     a shell that allows remote ZFS administration and nothing more

  3. zsnap:
     a command that snapshots a dataset or pool, then deletes old snapshots

  4. zreplicate
     a command that replicates an entire dataset tree using ZFS replication
     streams.  Best used in combination with zsnap as in:

     - zsnap on the local machine
     - zreplicate from the local machine to the destination machine

     Obsolete snapshots deleted by zsnap will be automatically purged on
     the destination machine by zreplicate, as a side effect of using
     replication streams.  To inhibit this, use the
     --no-replication-stream option.

     Run `zreplicate --help` for a compendium of options you may use.

  5. zbackup:
     a command to snapshot and replicate filesystems according to their user properties.
     This uses zsnap and zreplicate to do the work, which is all driven by properties.
     For details, see this [further description of zbackup](doc/README-zbackup.md).

  6. zflock:
     a command to lock a filesystem against replication by zbackup.
     For details, see this [further description of zbackup](doc/README-zbackup.md).

  The repository, bug tracker and Web site for this tool is at [http://github.com/Rudd-O/zfs-tools](http://github.com/Rudd-O/zfs-tools).  Comments to me through rudd-o@rudd-o.com.



  Setup is rather complicated.  It assumes that you already have ZFS running
  and vaults on both the machine you're going to back up and the machine that
  will be receiving the backup.



  - Install the zfs-shell command
    `cp zfs-shell /usr/local/sbin`
    `chmod 755 /usr/local/sbin/zfs-shell`
    `chown root.root /usr/local/sbin/zfs-shell`

  - Create a user with a home directory and shell `zfs-shell`
    `useradd -rUm -b /var/lib -s /usr/local/sbin/zfs-shell zfs`

  - Let `sudo` know that the new user can run the zfs command
    `zfs ALL = NOPASSWD: /usr/local/sbin/zfs`
    (ensure you remove the `requiretty` default on `/etc/sudoers`)
    (check `sudoers.zfs-tools` in `contrib/` for an example)

  - Set up a cron job to run `zsnap` as frequently as you want to,
    snapshotting the dataset you intend to replicate.



  - Set up public key authentication for SSH so the backup machine
    may log as the user `zfs` (as laid out above) in the machine to
    be backed up.

  - Create a dataset to receive the backup stream.

  - Set up a cron job to fetch the dataset snapshotted by zsnap
    from the remote machine into the newly created dataset.  You
    will use `zreplicate` for that (see below for examples).

  - After the first replication, you may want to set the `mountpoint`
    attributes on the received datasets so they do not automount
    on the backup machine.



  If all went well, you should be able to do this without issue:

  (on the machine to back up)

      [root@peter]
      zsnap senderpool

  (on the machine to receive)

      [root@paul]
      zfs create receiverpool/senderpool # <--- run this ONLY ONCE
      zreplicate -o zfs@paul:senderpool receiverpool/senderpool
      
      

  (on the machine to back up)

      [root@peter]
      zsnap senderpool

  (on the machine to receive)

      [root@paul]
      zreplicate -o zfs@paul:senderpool receiverpool/senderpool
      
      

  And that's it, really.


