add win probability feature to awpy2

.github/workflows/build.yml

@@ -5,8 +5,16 @@ name: build
 on:
   push:
     branches: [main, dev]
+    paths:
+      - 'awpy/**'
+      - 'tests/**'
+      - 'pyproject.toml'
   pull_request:
     branches: [main]
+    paths:
+      - 'awpy/**'
+      - 'tests/**'
+      - 'pyproject.toml'
 
 jobs:
   build:
@@ -15,15 +23,14 @@ jobs:
       fail-fast: false
       matrix:
         os: [ubuntu-latest, macos-latest, windows-latest]
-        python-version: ["3.11"] #, "3.12-dev"]
-        go-version: ["1.18", "1.19", "1.20"]
+        python-version: ["3.9", "3.10", "3.11", "3.12"]
     steps:
       - name: Checkout awpy library
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
       - name: Cache test demos
         id: cache-demos
-        uses: actions/cache@v3
+        uses: actions/cache@v4
         env:
           cache-name: cache-demos
         with:
@@ -38,14 +45,8 @@ jobs:
           # So do not do that!
           restore-keys: cache-test-demos-
 
-      - name: Set up Go
-        uses: actions/setup-go@v4
-        with:
-          go-version: ${{ matrix.go-version }}
-          cache-dependency-path: awpy/parser/go.sum
-
       - name: Set up Python
-        uses: actions/setup-python@v4
+        uses: actions/setup-python@v5
         with:
           python-version: ${{ matrix.python-version }}
           cache: "pip"
@@ -64,13 +65,9 @@ jobs:
 
       - name: Lint with ruff
         uses: chartboost/ruff-action@v1
-        with:
-          version: 0.0.291
 
       - name: Typecheck with pyright
-        uses: jakebailey/pyright-action@v1
-        with:
-          version: 1.1.329
+        uses: jakebailey/pyright-action@v2
 
       - name: Thorough check with pylint
         run: pylint awpy

.github/workflows/release-test.yml

@@ -0,0 +1,36 @@
+name: Build and Publish to Test PyPI
+
+on: workflow_dispatch
+
+jobs:
+  build-and-release:
+    runs-on: ubuntu-latest
+    environment:
+      name: test-release-pypi
+    permissions:
+      id-token: write
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.9"
+
+
+      - name: Build release distributions
+        run: |
+          python -m pip install --upgrade pip build
+          python -m build
+
+      - name: Publish package distribution to TestPyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/
+          user: __token__
+          password: ${{ secrets.PYPI_API_TOKEN }}
+
+      - name: Install package from TestPyPI
+        run: |
+          python -m pip install --index-url https://test.pypi.org/simple/ --no-deps awpy

.github/workflows/release.yml

@@ -0,0 +1,38 @@
+name: release
+
+on:
+  push:
+    tags:
+      - "release-v*.*.*"
+
+jobs:
+  build-and-release:
+    runs-on: ubuntu-latest
+    environment:
+      name: prod-release-pypi
+    permissions:
+      id-token: write
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.9"
+
+      - name: Install Poetry
+        uses: abatilo/actions-poetry@v2
+      - name: Setup a local virtual environment for poetry
+        run: |
+          poetry config virtualenvs.create true --local
+          poetry config virtualenvs.in-project true --local
+          poetry config repositories.testpypi https://test.pypi.org/legacy/
+
+      - name: Install awpy
+        run: |
+          poetry install --no-interaction
+
+      - name: Publish to PyPI
+        run: |
+          poetry publish --build --username __token__ --password ${{ secrets.PYPI_API_TOKEN }} -vvv

.pre-commit-config.yaml

@@ -63,8 +63,3 @@ repos:
             "-rn", # Only display messages
             "-sn", # Don't display the score
           ]
-  - repo: https://github.com/golangci/golangci-lint
-    rev: v1.54.2
-    hooks:
-      - id: golangci-lint
-        entry: bash -c 'cd awpy/parser && golangci-lint run --new-from-rev HEAD --fix'

.readthedocs.yaml

@@ -7,7 +7,7 @@ version: 2
 
 # Set the version of Python and other tools you might need
 build:
-  os: ubuntu-20.04
+  os: ubuntu-22.04
   tools:
     python: "3.11"
     # You can also specify other tool versions:

CONTRIBUTING.md

@@ -1,18 +1,18 @@
-# Contributing to awpy
+# Contributing to Awpy
 
-Hi! We're happy to have you here. Thank you in advance for your contribution to awpy.
+Hi! We're happy to have you here. Thank you in advance for your contribution to Awpy.
 
 ## Python code
 
-To make sure that awpy code stays readable and works correctly, we are making use of a variety of helpful tools.
+To make sure that Awpy code stays readable and works correctly, we are making use of a variety of helpful tools.
 
 We use the following tools:
 
 - [black](https://github.com/psf/black): An uncompromising Python code formatter.
 - [ruff](https://github.com/astral-sh/ruff): An extremely fast Python linter, written in Rust.
 - [pyright](https://github.com/microsoft/pyright): A static type checker for Python.
 - [pylint](https://github.com/pylint-dev/pylint): A static code analyser for Python.
-- [pytest](https://docs.pytest.org/en/7.4.x/): A mature full-featured Python testing tool.
+- [pytest](https://docs.pytest.org): A mature full-featured Python testing tool.
 - [pre-commit](https://pre-commit.com/): A framework for managing and maintaining multi-language pre-commit hooks.
 
 Please install these tools before you open a pull request to ensure that your contributions are easy to review.
@@ -26,7 +26,7 @@ pre-commit install --install-hooks
 After you have made your changes locally, use these tools to surface bugs or code smells by running the following:
 
 ```shell
-pre-commit run --all-files --show-diff-on-failure  # ruff, black, typos, pyright, pylint, golangci-lint
+pre-commit run --all-files --show-diff-on-failure  # ruff, black, typos, pyright, pylint
 coverage run -m pytest --durations=10  # python tests
 coverage report -m  # produces text-based coverage report
 ```
@@ -37,40 +37,12 @@ If you do not have the time or bandwidth, you can omit running the test command
 
 ### Testing/Coverage
 
-If you are fixing a bug or adding a new feature make sure to also add [unit tests](https://en.wikipedia.org/wiki/Unit_testing)
-that cover the original bug or your new functionality.
-If you are new to writing unit tests, look at the aforementioned link, or check out the [tests](tests) directory in awpy to see how our existing tests are built.
-
-## Go code
-
-If you are making changes or additions to the Go code then a look at and run
-[golangci-lint](https://github.com/golangci/golangci-lint).
-
-To install it, simply follow the [instructions](https://golangci-lint.run/usage/install/#local-installation) on their website.
-To run it do the following:
-
-```
-cd awpy/parser  # Change into the directory containing the go files
-golangci-lint run  # Run the linters
-```
-
-Additionally, run the Go code tests with:
-```
-go test -covermode=count -coverprofile=coverage.out
-go tool cover -html=coverage.out -o coverage.html
-go test -fuzz=FuzzConvertRank -fuzztime 30s
-go test -fuzz=FuzzDetermineSecond -fuzztime 30s
-go test -fuzz=FuzzParseTeamBuy -fuzztime 30s
-```
-
-Don't forget to run the Python tests as explained above -- changes in the Go code likely change the JSON output!
-
-If you are adding functionality aim to also add go tests to avoid bug and future regressions.
+If you are fixing a bug or adding a new feature make sure to also add [unit tests](https://en.wikipedia.org/wiki/Unit_testing) that cover the original bug or your new functionality. If you are new to writing unit tests, look at the aforementioned link, or check out the [tests](tests) directory in Awpy to see how our existing tests are built.
 
 If you are adding a test that requires a specific demo, please let us know so that we can include them in our set of testing demos.
 While developing, you can also edit the [test_data.json](/tests/test_data.json) file to include wherever you are hosting the test demo file.
 
 
 ## Thanks
 
-With all this you are now ready to make contributions to awpy. We are looking forward to them!
+With all this you are now ready to make contributions to Awpy. We look forward to your contributions!