semvec/pypi-packages huggingface dataset:
py3status-pewpew 0.2
py3status module to control i3wm with the PewPew

[![Travis CI status](https://api.travis-ci.org/obestwalter/py3status-pewpew.png)](https://travis-ci.org/obestwalter/py3status-pewpew)
[![PyPI version](https://badge.fury.io/py/py3status-pewpew.svg)](https://pypi.org/project/py3status-pewpew/)

# py3status-pewpew

A [py3status](https://github.com/ultrabug/py3status) module turning the [PewPew](https://pewpew.readthedocs.io) into a controller and external workspace display for the [i3wm](https://i3wm.org/) tiling window manager.

[![Watch a short demo video](http://img.youtube.com/vi/0Oy2CE2GZ7s/0.jpg)](http://www.youtube.com/watch?v=0Oy2CE2GZ7s "py3status-pewpew status controller")

Extend i3 with your PewPew. Use the buttons to send messages to i3 (or do whatever else you like) and always see which workspace you are on.

## install

```text
pip install py3status-pewpew
```

See install-ubuntu16.04.md for specific instructions on that distribution.

# testing

run the tests with tox:

```console
$ cd </path/to/this/repo>
$ tox
```

## development

install a development environment:

```console
$ cd </path/to/this/repo>
$ tox -e dev
```

... and activate it e.g via `source .tox/dev/bin/activate`. Then run tests with `pytest`.

Debugging hint - use screen to get direct access and run commands in the REPL:

    $ screen /dev/ttyACM0

This will open a screen session. Ctrl+C and Enter is useful to soft reboot pewpew in there.


# CHANGELOG

This project uses [smeantic versioning](https://semver.org/).

## [0.2] - 2019-08-09
## Added

* dependency to py3status >= 3.20 (we need the entry point discovery support) - thanks @objarni

## Fixed

* Adjust changelog format to use https://keepachangelog.com style

## [0.1.post1] - 2019-08-08
## Fixed 

* missing long description and homepage link for PyPI

## [0.1]  - 2019-08-08
## Added

* minimal implementation of a controller module for py3status using the PewPew

---

# About this Changelog

https://keepachangelog.com suggests:

Guiding Principles

* Changelogs are for humans, not machines.
* There should be an entry for every single version.
* The same types of changes should be grouped.
* Versions and sections should be linkable.
* The latest version comes first.
* The release date of each version is displayed.
* Mention whether you follow Semantic Versioning.

Types of changes

* **Added for new features.
* **Changed for changes in existing functionality.
* **Deprecated for soon-to-be removed features.
* **Removed for now removed features.
* **Fixed for any bug fixes.
* **Security in case of vulnerabilities.