This is trickier to test than normal, as as far as I can tell Github actions are only run from the master branch (and I've renamed master to main in my fork). There might be some other bug or subtlety I've missed, but in my fork's main branch I've got the same build.yml file, only targetting the branch from which this PR is coming (in which build.yml targets master).
Drop actions/setup-python, move the matrix strategy forward, pin to the specific patch versions below, and use the matrix to run the action in Python Slim containers (versions 2.7.18, 3.5.10, 3.6.15, 3.7.17, 3.8.18, and 3.9.18)
Bump actions/checkout from v2 to v3
Reformat PyShp usage example with undefined variable in readme.md from >>> to Markdown code literal block, so doctest skips it, as for PR # 265.
This is trickier to test than normal, as as far as I can tell Github actions are only run from the master branch (and I've renamed master to main in my fork). There might be some other bug or subtlety I've missed, but in my fork's main branch I've got the same build.yml file, only targetting the branch from which this PR is coming (in which build.yml targets master).
This PR is from a branch based on the branch from which I raised my previous PR, #265 so it includes the blocking out of the failing Doctest. the test results for PyShp are all green on Pythons 2.7, 3.5, ..., 3.9.
https://github.com/JamesParrott/IronPyShp/actions/runs/7545262680/job/20540473529
Summary of changes: