[add] Python 3.10 support

.codecov.yml

@@ -0,0 +1 @@
+comment: off

.editorconfig

@@ -0,0 +1,16 @@
+[*]
+insert_final_newline = true
+trim_trailing_whitespace = true
+end_of_line = lf
+charset = utf-8
+indent_style = space
+
+[*.py]
+indent_size = 4
+max_line_length = 88
+
+[*.{json,yml,html}]
+indent_size = 2
+
+[Makefile]
+indent_style = tab

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @daniel-ruiz @EmilioCarrion @mgarcia0094 @AdamjGoddard

.github/pull_request_template.md

@@ -0,0 +1,11 @@
+### :tophat: What?
+
+Provide a description of what has been implemented.
+
+### :thinking: Why?
+
+Give an explanation of why.
+
+### :link: Related issue
+
+Add related issue's number. Example: Fix #1

.gitignore

@@ -10,9 +10,13 @@
 /dist/
 /*.egg-info/
 /env/
+/venv/
 MANIFEST
 coverage.*
+docs/_build
 
 !.gitignore
 !.travis.yml
-!.isort.cfg
+!.editorconfig
+!.github
+!.codecov.yml

.readthedocs.yml

@@ -0,0 +1,21 @@
+# .readthedocs.yml
+# Read the Docs configuration file
+# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
+
+# Required
+version: 2
+
+# Build documentation in the docs/ directory with Sphinx
+sphinx:
+  configuration: docs/conf.py
+
+# Build documentation with MkDocs
+#mkdocs:
+#  configuration: mkdocs.yml
+
+# Optionally build your docs in additional formats such as PDF and ePub
+formats: all
+
+python:
+  install:
+    - requirements: requirements/base.txt

.travis.yml

@@ -0,0 +1,28 @@
+dist: bionic
+sudo: false
+notifications:
+  email: false
+
+services:
+  - postgresql
+addons:
+  postgresql: "9.6"
+
+language: python
+python:
+  - "3.6"
+  - "3.10"
+
+install:
+  - make install-requirements
+  - make install-django-requirements
+  - make install-test-requirements
+
+before_script:
+  - make lint
+  - psql -c 'create database travis_ci_test;' -U postgres
+
+script:
+  - make coverage
+  - codecov
+

AUTHORS.md

@@ -0,0 +1,18 @@
+Thank you to all the contributors to Relé!
+
+* Andrew Graham-Yooll (@andrewgy8)
+* Miquel Torres Barcelo (@tobami)
+* Edgar Latorre (@edgarlatorre)
+* Lluis Guirado (@LluisGuiVi)
+* Daniel Ruiz (@dani-ruiz)
+* Juanjo Ponz (@jjponz)
+* Jose Antonio Navarro (@jonasae)
+* Antonio Bustos Rodriguez (@antoniobusrod)
+* David de la Iglesia (@ddelaiglesia) for the Logo!
+* Santiago Lanús (@sanntt)
+* Craig Mulligan (@hobochild)
+* Daniel Demmel (@daaain)
+* Luis Garcia Cuesta (@luisgc93)
+* Chirag Jain (@chirgjin-les)
+* Jordi Chulia (@jorchube)
+* Emilio Carrión (@EmilioCarrion)

CHANGELOG.rst

@@ -0,0 +1,193 @@
+Changelog
+=========
+
+1.6.0 (2022-08-03)
+-------------------
+* [Added] Implement auto restart of the consumption when futures are done or cancelled. (#226)
+
+1.5.0 (2022-04-20)
+-------------------
+* [Added] Add filter expressions to subscriptions. (#207)
+
+1.4.1 (2022-04-19)
+-------------------
+* [Modified] Fixed bug in the post-publish-failure VerboseLoggingMiddleware hook. (#220)
+
+1.4.0 (2022-04-13)
+-------------------
+* [Added] Added a VerboseLoggingMiddleware that does not truncate mesage payload. (#218)
+
+1.3.0 (2022-04-04)
+-------------------
+* GC Project Id & Windows support (#215)
+
+1.2.0 (2021-12-10)
+-------------------
+* [CHANGED] TimeotError from publisher (#212)
+* Added filter_subs_by setting in documentation (#208)
+* Automatic topic creation (#206)
+* Log post publish success (#204)
+
+1.1.1 (2021-6-28)
+-------------------
+* Do not define default_app_config, it's deprecated (#199)
+* Do not implement deprecated middlewares in the base class (#200)
+
+1.1.0 (2021-3-10)
+-------------------
+* Google Pubsub 2.0 Compat (#192)
+* Add validations to the sub decorator (#189)
+* Add new post_publish_hook and deprecate the old one (#190)
+* Discover and load settings when publishing (#188)
+* Fix #180: Raise error when the config loads a repeated subscription (#187)
+
+1.0.0 (2020-9-25)
+-------------------
+* BREAKING: Remove GC_PROJECT_ID (#183)
+
+0.14.0 (2020-8-5)
+-------------------
+* BREAKING: Remove GC_CREDENTIALS (#174)
+* Add changelog to the docs site (#179)
+* Catch TimeoutError and run post_publish_failure when blocking (#172)
+* Deprecate GC_PROJECT_ID setting (#178)
+
+0.13.0 (2020-7-9)
+-------------------
+* Add documentation for class based subscriptions (#169)
+* Deprecate GC_CREDENTIALS setting (#173)
+* GC_CREDENTIALS_PATH setting option (#170)
+
+0.13.dev0 (2020-6-16)
+---------------------
+* Traverse all packages to autodiscover all subs.py modules (#167)
+* Auto-discovery of class based subscriptions (#168)
+
+0.12.0 (2020-6-12)
+-------------------
+* Added ``--settings`` path option in CLI (#166)
+* Added isort linting (#164)
+
+0.11.0 (2020-6-4)
+-------------------
+* CLI feature (#160)
+* Documentation Enhancements (#158, #155, #162)
+* Testing Improvements (#154, #157)
+
+0.10.0 (2020-2-4)
+-------------------
+* Adjust default THREADS_PER_SUBSCRIPTION (#152)
+* Add unrecoverable_middleware (#150)
+* Allow multiple filters (#148)
+* Configure timeout from .publish() (#143)
+* Dont crash when subscription topic does not exist (#142)
+
+0.9.1 (2020-1-2)
+-------------------
+* Ack messages when data not json serializable (#141)
+* Use ThreadScheduler instead of ThreadPoolExecutor (#145)
+
+0.9.0 (2019-12-20)
+-------------------
+* Flask support via middleware (#127)
+* Add message attributes to metrics log (#128)
+* Specify number of threads per subscriber with Subscription ThreadPoolExecutor (#139)
+* Publishing timeout while blocking (#137)
+* Clean up rele.config.setup + Worker() init (#132)
+
+0.8.1 (2019-11-25)
+-------------------
+* Fix runrele command
+
+0.8.0 (2019-11-22)
+-------------------
+* Worker run method (#118)
+* Add kwargs to setup method passed through to middleware (#123)
+* Add missing worker middleware hooks (#121)
+* Add 3.8 support
+* More Documentation
+
+0.7.0 (2019-10-21)
+-------------------
+* BREAKING: Remove Django as a dependency (#95)
+* More documentation
+
+0.6.0 (2019-09-21)
+-------------------
+* BREAKING: Remove drf as a dependency (#91)
+* Add message as a parameter for middleware hooks (#99)
+* Check setting.CONN_MAX_AGE and warn when not 0 (#97)
+* More documentation
+
+0.5.0 (2019-08-08)
+-------------------
+* ``python manage.py showsubscriptions`` command
+* Configurable ENCODER setting
+* Move DEFAULT_ACK_DEADLINE to the RELE config
+* More documentation
+
+0.4.1 (2019-06-18)
+-------------------
+* Ability to install app only with rele
+* Define default filter_by in settings.RELE
+
+0.4.0 (2019-06-17)
+-------------------
+
+* Set ``DEFAULT_ACK_DEADLINE`` (#49)
+* Filter by message attributes (#66)
+* BREAKING: All Relé settings are defined in a dict (#60)
+
+Old structure:
+
+.. code:: python
+
+    from google.oauth2 import service_account
+    RELE_GC_CREDENTIALS = service_account.Credentials.from_service_account_file(
+        'rele/settings/dummy-credentials.json'
+    )
+    RELE_GC_PROJECT_ID = 'dummy-project-id'
+
+New structure:
+
+.. code:: python
+
+    from google.oauth2 import service_account
+    RELE = {
+        'GC_CREDENTIALS': service_account.Credentials.from_service_account_file(
+            'rele/settings/dummy-credentials.json'
+        ),
+        'GC_PROJECT_ID': 'dummy-project-id',
+        'MIDDLEWARE': [
+            'rele.contrib.LoggingMiddleware',
+            'rele.contrib.DjangoDBMiddleware',
+        ],
+        'SUB_PREFIX': 'mysubprefix',
+        'APP_NAME': 'myappname',
+    }
+
+* ``rele.contrib.middleware`` (#55)
+* Prefix argument in sub decorator (#47)
+* Add timestamp to the published message (#42)
+* BREAKING: Explicit publisher and subscriber configuration (#43)
+* Sphinx documentation (#27, #34, #40, #41)
+* Contributing guidelines (#32)
+
+0.3.1 (2019-06-04)
+-------------------
+
+* Add prometheus metrics key to logs (#16 - #20, #22, #23)
+* Fix JSON serialization when publishing (#25)
+
+0.3.0 (2019-05-14)
+-------------------
+
+* Ability to run in emulator mode (#12)
+* Add Travis-CI builds (#10)
+* More friendly global publish (#11)
+* Non-blocking behaviour when publishing by default (#6)
+
+0.2.0 (2019-05-09)
+-------------------
+
+* Initial version

CODE_OF_CONDUCT.md

@@ -0,0 +1,77 @@
+# Contributor Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, 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.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers 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, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq
+