Cleanup of files

.github/workflows/tests.yml

@@ -135,4 +135,4 @@ jobs:
           nox --force-color --session=coverage -- xml
 
       - name: Upload coverage report
-        uses: codecov/codecov-action@v1.0.13
+        uses: codecov/codecov-action@v1.0.13

.pre-commit-config.yaml

@@ -3,45 +3,45 @@ repos:
     hooks:
       - id: black
         name: black
-        entry: poetry run black
+        entry: black
         language: system
         types: [python]
         require_serial: true
       - id: check-added-large-files
         name: Check for added large files
-        entry: poetry run check-added-large-files
+        entry: check-added-large-files
         language: system
       - id: check-toml
         name: Check Toml
-        entry: poetry run check-toml
+        entry: check-toml
         language: system
         types: [toml]
       - id: check-yaml
         name: Check Yaml
-        entry: poetry run check-yaml
+        entry: check-yaml
         language: system
         types: [yaml]
       - id: end-of-file-fixer
         name: Fix End of Files
-        entry: poetry run end-of-file-fixer
+        entry: end-of-file-fixer
         language: system
         types: [text]
         stages: [commit, push, manual]
       - id: flake8
         name: flake8
-        entry: poetry run flake8
+        entry: flake8
         language: system
         types: [python]
         require_serial: true
       - id: reorder-python-imports
         name: Reorder python imports
-        entry: poetry run reorder-python-imports
+        entry: reorder-python-imports
         language: system
         types: [python]
         args: [--application-directories=src]
       - id: trailing-whitespace
         name: Trim Trailing Whitespace
-        entry: poetry run trailing-whitespace-fixer
+        entry: trailing-whitespace-fixer
         language: system
         types: [text]
         stages: [commit, push, manual]

.readthedocs.yml

@@ -6,4 +6,3 @@ python:
   version: 3.8
   install:
     - requirements: docs/requirements.txt
-    - path: .

CODE_OF_CONDUCT.rst

@@ -0,0 +1,105 @@
+Contributor Covenant Code of Conduct
+====================================
+
+Our Pledge
+----------
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+
+Our Standards
+-------------
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+Enforcement Responsibilities
+----------------------------
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+
+Scope
+-----
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+
+Enforcement
+-----------
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at leon@bowie-co.nz. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+
+Enforcement Guidelines
+----------------------
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+
+1. Correction
+~~~~~~~~~~~~~
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+
+2. Warning
+~~~~~~~~~~
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+
+3. Temporary Ban
+~~~~~~~~~~~~~~~~
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+
+4. Permanent Ban
+~~~~~~~~~~~~~~~~
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+
+Attribution
+-----------
+
+This Code of Conduct is adapted from the `Contributor Covenant <homepage_>`__, version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by `Mozilla’s code of conduct enforcement ladder <https://github.com/mozilla/diversity>`__.
+
+.. _homepage: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

CONTRIBUTING.rst

@@ -0,0 +1,113 @@
+# Contributor Guide
+
+Thank you for your interest in improving this project.
+This project is open-source under the `GPLv3 license`\_ and
+welcomes contributions in the form of bug reports, feature requests, and pull requests.
+
+Here is a list of important resources for contributors:
+
+- `Source Code`\_
+- `Documentation`\_
+- `Issue Tracker`\_
+- `Code of Conduct`\_
+
+.. \_GPLv3 license: https://opensource.org/licenses/GPL-3.0
+.. \_Source Code: https://github.com/Darkflame72/asyncpixel
+.. \_Documentation: https://asyncpixel.readthedocs.io/
+.. \_Issue Tracker: https://github.com/Darkflame72/asyncpixel/issues
+
+## How to report a bug
+
+Report bugs on the `Issue Tracker`\_.
+
+When filing an issue, make sure to answer these questions:
+
+- Which operating system and Python version are you using?
+- Which version of this project are you using?
+- What did you do?
+- What did you expect to see?
+- What did you see instead?
+
+The best way to get your bug fixed is to provide a test case,
+and/or steps to reproduce the issue.
+
+## How to request a feature
+
+Request features on the `Issue Tracker`\_.
+
+## How to set up your development environment
+
+You need Python 3.6+ and the following tools:
+
+- Poetry\_
+- Nox\_
+- nox-poetry\_
+
+Install the package with development requirements:
+
+.. code:: console
+
+$ poetry install
+
+You can now run an interactive Python session,
+or the command-line interface:
+
+.. code:: console
+
+$ poetry run python
+$ poetry run asyncpixel
+
+.. \_Poetry: https://python-poetry.org/
+.. \_Nox: https://nox.thea.codes/
+.. \_nox-poetry: https://nox-poetry.readthedocs.io/
+
+## How to test the project
+
+Run the full test suite:
+
+.. code:: console
+
+$ nox
+
+List the available Nox sessions:
+
+.. code:: console
+
+$ nox --list-sessions
+
+You can also run a specific Nox session.
+For example, invoke the unit test suite like this:
+
+.. code:: console
+
+$ nox --session=tests
+
+Unit tests are located in the `tests` directory,
+and are written using the pytest\_ testing framework.
+
+.. \_pytest: https://pytest.readthedocs.io/
+
+## How to submit changes
+
+Open a `pull request`\_ to submit changes to this project.
+
+Your pull request needs to meet the following guidelines for acceptance:
+
+- The Nox test suite must pass without errors and warnings.
+- Include unit tests. This project maintains 100% code coverage.
+- If your changes add functionality, update the documentation accordingly.
+
+Feel free to submit early, though—we can always iterate on this.
+
+To run linting and code formatting checks before commiting your change, you can install pre-commit as a Git hook by running the following command:
+
+.. code:: console
+
+$ nox --session=pre-commit -- install
+
+It is recommended to open an issue before starting work on anything.
+This will allow a chance to talk it over with the owners and validate your approach.
+
+.. \_pull request: https://github.com/Obsidion-dev/asyncpixel/pulls
+.. github-only
+.. \_Code of Conduct: CODE_OF_CONDUCT.rst

docs/codeofconduct.rst

@@ -0,0 +1 @@
+.. include:: ../CODE_OF_CONDUCT.rst

docs/conf.py

@@ -13,7 +13,7 @@
 import sys
 from datetime import datetime
 
-sys.path.insert(0, os.path.abspath("../asyncpixel"))
+sys.path.insert(0, os.path.abspath("../"))
 
 
 # -- Project information -----------------------------------------------------
@@ -37,6 +37,8 @@
     "sphinx.ext.napoleon",
     "sphinx.ext.viewcode",
     "sphinx.ext.intersphinx",
+    "recommonmark",
+    "sphinx_autodoc_typehints",
 ]
 
 intersphinx_mapping = {

docs/contributing.rst

@@ -0,0 +1,4 @@
+.. include:: ../CONTRIBUTING.rst
+   :end-before: github-only
+
+.. _Code of Conduct: codeofconduct.html