Build and publish using github-ci (#42)

Author: ahothan

.github/workflows/python-publish.yml

@@ -0,0 +1,40 @@
+# This workflow will upload a Python Package using Twine when a release is created
+# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#publishing-to-package-registries
+
+# This workflow uses actions that are not certified by GitHub.
+# They are provided by a third-party and are governed by
+# separate terms of service, privacy policy, and support
+# documentation.
+
+name: Upload Python Package
+
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: read
+
+jobs:
+  deploy:
+
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v3
+    - name: Set up Python
+      uses: actions/setup-python@v3
+      with:
+        python-version: '3.x'
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip
+        pip install build
+    - name: Build package
+      run: python -m build
+    - name: Publish package
+      uses: pypa/gh-action-pypi-publish@27b31702a0e7fc50959f5ad993c78deac1bdfc29
+      with:
+        user: __token__
+        password: ${{ secrets.PYPI_API_TOKEN }}
+

.github/workflows/pylint.yml renamed to .github/workflows/tox.yml

@@ -1,4 +1,4 @@
-name: Pylint
+name: Tox
 
 on: [push]
 
@@ -7,7 +7,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        python-version: ["3.8", "3.9", "3.10"]
+        python-version: ["3.7", "3.8", "3.9", "3.10", "3.11"]
     steps:
     - uses: actions/checkout@v3
     - name: Set up Python ${{ matrix.python-version }}
@@ -17,7 +17,7 @@ jobs:
     - name: Install dependencies
       run: |
         python -m pip install --upgrade pip
-        pip install pylint
-    - name: Analysing the code with pylint
+        pip install tox
+    - name: Running tox
       run: |
-        pylint --rcfile pylint.rc $(git ls-files '*.py')
+        tox

.travis.yml

@@ -482,16 +482,9 @@ small pbr python package which takes care of the versioning (among other things)
 
 Publishing a New Release to PyPI
 --------------------------------
-This requires twine to be installed and the API token to publish to PyPI.
-After applying a new tag, build the new distribution on a Linux server then upload using twine:
 
-.. code::
-
-   rm -f dist/*
-   python setup.py sdist bdist_wheel
-   twine upload dist/*
-
-For username, use "__token__", then provide the api token (see  https://packaging.python.org/en/latest/tutorials/packaging-projects/)
+To create a new release, apply a new release tag then create a new Release using github (this requires right permission). 
+The github CI will build the distributions and push to PyPI.
 
 
 Licensing

README.rst

@@ -1,32 +1,13 @@
 '''
 Setup
 '''
-import sys
 from setuptools import setup
 from setuptools import Extension
-from setuptools.command.test import test
-
-
-class Tox(test):
-    def initialize_options(self):
-        test.initialize_options(self)
-        self.tox_args = None # pylint: disable=attribute-defined-outside-init
-
-    def finalize_options(self):
-        test.finalize_options(self)
-        self.test_args = []
-        self.test_suite = True # pylint: disable=attribute-defined-outside-init
-
-    def run_tests(self):
-        import tox # pylint: disable=import-outside-toplevel
-        sys.exit(tox.cmdline())
 
 
 if __name__ == '__main__':
     setup(setup_requires=['pbr'], pbr=True,
           keywords='hdrhistogram hdr histogram high dynamic range',
-          tests_require=['tox'],
-          cmdclass={'test': Tox},
           ext_modules=[Extension('pyhdrh',
                                  sources=['src/python-codec.c'])]
           )