Finalizing v0.7

.github/workflows/build-wheels.yml

@@ -0,0 +1,65 @@
+name: Build-wheels
+
+# This workflow builds "wheels", which are the binary package installers hosted on PyPI.
+# GitHub Actions is super helpful here because each one needs to be compiled in its own
+# target environment. The wheel files are saved as artifacts, which you can download from
+# the GitHub website. Wheels should be uploaded manually to PyPI -- see CONTRIBUTING.md.
+
+# The Linux wheels cannot be generated using `ubuntu-latest` because they require a
+# special Docker image to provide cross-Linux compatibility. There are at least a couple
+# of third-party actions set up using the official image; we could switch to another if
+# this ever breaks.
+
+on:
+  # push:
+  pull_request:
+  release:
+  workflow_dispatch:
+
+jobs:
+
+  build-manylinux:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+#      with:
+#        ref: 'v0.6'  # enable to check out prior version of codebase
+    - name: Build wheels
+      uses: RalfG/[email protected]
+      with:
+        python-versions: 'cp38-cp38 cp39-cp39 cp310-cp310 cp311-cp311'
+    - name: Save artifacts
+      uses: actions/upload-artifact@v2
+      with:
+        name: wheels
+        path: dist/*-manylinux*.whl
+
+  build:
+    runs-on: ${{ matrix.os }}
+    defaults:
+      run:
+        shell: bash -l {0}  # needed for conda persistence
+    strategy:
+      matrix:
+        os: [macos-latest, windows-latest]
+        python-version: [3.8, 3.9, '3.10', '3.11']
+    steps:
+    - uses: actions/checkout@v2
+#      with:
+#        ref: 'v0.6'  # enable to check out prior version of codebase
+    - name: Set up Python ${{ matrix.python-version }}
+      uses: conda-incubator/setup-miniconda@v2
+      with:
+        python-version: ${{ matrix.python-version }}
+    - name: Set up environment
+      run: |
+        conda config --append channels conda-forge
+        conda install build clang llvm-openmp
+    - name: Build wheel
+      run: |
+        python -m build --sdist --wheel
+    - name: Save artifacts
+      uses: actions/upload-artifact@v2
+      with:
+        name: wheels
+        path: dist/*.whl

.github/workflows/code-style.yml

@@ -0,0 +1,21 @@
+name: Code style
+
+# This workflow runs code style checks.
+
+on:
+  push:
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Python
+      uses: actions/setup-python@v2
+      with:
+        python-version: '3.x'
+    - name: Check code style
+      run: |
+        pip install pycodestyle
+        pycodestyle pandana

.github/workflows/coverage.yml

@@ -0,0 +1,40 @@
+name: Coverage
+
+# This workflow generates a coverage report (how much of the codebase is covered by the
+# unit tests) and posts headline metrics to the PR thread.
+
+on:
+  # push:
+  pull_request:
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Python
+      uses: actions/setup-python@v2
+      with:
+        python-version: '3.10'
+    - name: Install Pandana
+      run: |
+        pip install .
+        pip install osmnet
+
+# `coverage run ...` is failing in GitHub Actions, but I'm not able to reproduce the
+# problem locally. We should look into this again another time. (11-May-2021)
+
+#    - name: Generate coverage report
+#      run: |
+#        pip install pytest coverage
+#        coverage run --source pandana --module pytest --verbose
+#        coverage report --show-missing
+#        echo "coverage=$(coverage report | grep '^TOTAL' | grep -oE '[^ ]+$')" >> $GITHUB_ENV
+#    - name: Post comment on PR
+#      uses: unsplash/comment-on-pr@master
+#      env: 
+#        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+#      with:
+#        msg: "Test coverage is ${{ env.coverage }}"
+#        check_for_duplicate_msg: true

.github/workflows/cross-compatibility.yml

@@ -0,0 +1,66 @@
+name: Cross-compatibility
+
+# This workflow runs the Pandana unit tests across a comprehensive range of Python
+# versions and operating systems. Windows needs conda in order to install geospatial
+# dependencies.
+
+on:
+  # push:
+  pull_request:
+  workflow_dispatch:
+
+jobs:
+  build-pip:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        python-version: [3.8, 3.9, '3.10', '3.11']
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Python ${{ matrix.python-version }}
+      uses: actions/setup-python@v2
+      with:
+        python-version: ${{ matrix.python-version }}
+    - name: Install Pandana
+      run: |
+        pip install .
+        pip install osmnet
+    - name: Run demo
+      run: |
+        python examples/simple_example.py
+    - name: Run unit tests
+      run: |
+        pip install pytest
+        pytest -s
+
+  build-conda:
+    runs-on: ${{ matrix.os }}
+    defaults:
+      run:
+        shell: bash -l {0}  # needed for conda persistence
+    strategy:
+      matrix:
+        os: [windows-latest]
+        python-version: [3.8, 3.9, '3.10', '3.11']
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Python ${{ matrix.python-version }}
+      uses: conda-incubator/setup-miniconda@v2
+      with:
+        python-version: ${{ matrix.python-version }}
+    - name: Install Pandana
+      run: |
+        pip install .
+
+# OSMNet is causing a version of Pandas to be installed that crashes in GitHub Actions.
+# Assume this will resolve itself on its own. (11-May-2021)
+
+#        conda install osmnet --channel conda-forge
+    - name: Run demo
+      run: |
+        python examples/simple_example.py
+#    - name: Run unit tests
+#      run: |
+#        pip install pytest
+#        pytest -s

.github/workflows/installation.yml

@@ -0,0 +1,58 @@
+name: Installation
+
+# This workflow installs Pandana from Pip and Conda across a range of Python versions and
+# operating systems. You can run this manually after a new release is posted to confirm
+# that it installs smoothly. This workflow also runs periodically in the background to
+# catch dependency updates that break Pandana.
+
+on:
+  # push:
+  # pull_request:
+  workflow_dispatch:
+  schedule:
+  - cron: '0 3 * * 1'  # every Monday at 3am UTC (Sunday evening Calif time)
+
+jobs:
+  build-pip:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest]
+        # Pip installation for Windows is not supported. Pip installation for Mac is
+        # broken in the GitHub Actions environment with Pandana v0.6 but should be fixed
+        # in the next Pandana release.
+        python-version: [3.8, 3.9, '3.10', '3.11']
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Python ${{ matrix.python-version }}
+      uses: actions/setup-python@v2
+      with:
+        python-version: ${{ matrix.python-version }}
+    - name: Install Pandana
+      run: |
+        pip install pandana
+    - name: Run demo
+      run: |
+        python examples/simple_example.py
+
+  build-conda:
+    runs-on: ${{ matrix.os }}
+    defaults:
+      run:
+        shell: bash -l {0}  # needed for conda persistence
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest, windows-latest]
+        python-version: [3.8, 3.9, '3.10', '3.11']
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Python ${{ matrix.python-version }}
+      uses: conda-incubator/setup-miniconda@v2
+      with:
+        python-version: ${{ matrix.python-version }}
+    - name: Install Pandana
+      run: |
+        conda install pandana --channel conda-forge
+    - name: Run demo
+      run: |
+        python examples/simple_example.py

.github/workflows/unit-tests.yml

@@ -0,0 +1,28 @@
+name: Unit tests
+
+# This workflow runs the Pandana unit tests in a single generic environment (recent but
+# stable Python version on recent but stable Ubuntu). The cross-compatibility.yml
+# workflow runs the same tests across multiple platforms.
+
+on:
+  push:
+  # pull_request:
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+    - name: Set up Python
+      uses: actions/setup-python@v2
+      with:
+        python-version: '3.10'
+    - name: Install Pandana
+      run: |
+        pip install .
+        pip install osmnet
+    - name: Run unit tests
+      run: |
+        pip install pytest
+        pytest -s

CHANGELOG.md

@@ -1,3 +1,26 @@
+v0.7
+====
+
+2023/07/26
+
+* Adds support for calculating accessibility isochrones: which nodes are within x network distance of a source node
+* Allows a maximum distance to be set for POIs
+* Adds a warning when a shortest path is requested between unconnected nodes
+* Supports PyTables 3.7+
+* Support Pandas 2.0
+* Switches to pyproject.toml packaging standards
+* Adds binaries on PyPI to support Python 3.10 and 3.11
+* Improves compilation in MacOS 12+
+
+v0.6.1
+======
+
+2021/03/17
+
+* Adds support for non-x86 CPUs, including ARM-based Macs
+* Removes accommodations for pre-C++11 compilers
+* Formally ends support for Python 2.7
+
 v0.6
 ====
 

CONTRIBUTING.md

@@ -9,7 +9,7 @@ You can contact Sam Maurer, the lead maintainer, at `[email protected]`.
 
 - Take a look at the [open issues](https://github.com/UDST/pandana/issues) and [closed issues](https://github.com/UDST/pandana/issues?q=is%3Aissue+is%3Aclosed) to see if there's already a related discussion
 
-- Open a new issue describing the problem -- if possible, include any error messages, the operating system and version of python you're using, and versions of any libraries that may be relevant
+- Open a new issue describing the problem -- if possible, include any error messages, a full reproducible example of the code that generated the error, the operating system and version of python you're using, and versions of any libraries that may be relevant
 
 
 ## Feature proposals:
@@ -25,7 +25,7 @@ You can contact Sam Maurer, the lead maintainer, at `[email protected]`.
 
 - Make your changes, following the existing styles for code and inline documentation
 
-- Add [tests](https://github.com/UDST/urbansim/tree/master/pandana/tests) if possible!
+- Add [tests](https://github.com/UDST/pandana/tree/master/pandana/tests) if possible!
 
 - Open a pull request to the `UDST/pandana` dev branch, including a writeup of your changes -- take a look at some of the closed PR's for examples
 
@@ -46,7 +46,8 @@ You can contact Sam Maurer, the lead maintainer, at `[email protected]`.
   - `setup.py`
   - `pandana/__init__.py`
   - `docs/source/index.rst`
-
+  - `docs/source/conf.py`
+
 - Make sure all the tests are passing, and check if updates are needed to `README.md` or to the documentation
 
 - Open a pull request to the master branch to finalize it
@@ -68,11 +69,19 @@ You can contact Sam Maurer, the lead maintainer, at `[email protected]`.
 
 - Check https://pypi.org/project/pandana/ for the new version
 
+The binary package installers or "wheels" are built using a GitHub Actions workflow, because each one needs to be compiled in its own target environment. This should run automatically when a PR is opened, to confirm nothing is broken, and again when a release is tagged in GitHub. You can download the resulting wheel files from the Action status page and then upload them to PyPI using the same command as above.
+
+How to create wheels for ARM Macs: As of 7/2023, GitHub Actions doesn't provide this environment yet. You'll need an ARM Mac to create the wheels. One at a time, set up a Conda environment with Python 3.8, 3.9, etc. Include cython, numpy, clang, llvm-openmp, and pytables. These need to be ARM-native Conda environments -- check that you're getting `osx-arm64` versions of libraries. Run `python setup.py bdist_wheel` to generate a wheel file. Once one is built for each Python version, upload them to PyPI using the command above.
+
 
 ## Distributing a release on Conda Forge (for conda installation):
 
-- The [conda-forge/pandana-feedstock](https://github.com/conda-forge/pandana-feedstock) repository controls the Conda Forge release
+- The [conda-forge/pandana-feedstock](https://github.com/conda-forge/pandana-feedstock) repository controls the Conda Forge release, including which GitHub users have maintainer status for the repo
 
 - Conda Forge bots usually detect new releases on PyPI and set in motion the appropriate feedstock updates, which a current maintainer will need to approve and merge
 
+- Maintainers can add on additional changes before merging the PR, for example to update the requirements or edit the list of maintainers
+
+- You can also fork the feedstock and open a PR manually. It seems like this must be done from a personal account (not a group account like UDST) so that the bots can be granted permission for automated cleanup
+
 - Check https://anaconda.org/conda-forge/pandana for the new version (may take a few minutes for it to appear)