Drop Python 3.6

[joshmoore]

see: #317
see: zarr-developers/zarr-python#765

• Unit tests and/or doctests in docstrings
• tox -e py39 passes locally
• Docstrings and API docs for any new/modified user-facing classes and functions
• Changes documented in docs/release.rst
• tox -e docs passes locally
• GitHub Actions CI passes
• Test coverage to 100% (Coveralls passes)

[joshmoore]

@jakirkham, thoughts or help on the feedstock front(s) welcome.

[joshmoore]

This change is likely debatable since we're not explicitly breaking compatibility.

[jakirkham]

Eh I think it is ok to drop. We are not testing it any more. So we really can't guarantee things work there.

[jakirkham]

Might be worth updating cibuildwheel. Also think we can skip certain builds. From their docs, this looks useful:

# Skip building on CPython 3.6 on all platforms
CIBW_SKIP: cp36-*

[joshmoore]

Changed 3.6 branch protection for master to 3.10. Closing and re-opening.

[joshmoore]

The hanging build (3.6) Expected — Waiting for status to be reported build apparently isn't going away, but the build will pass without.

[jakirkham]

May need to push another commit

[joshmoore]

Think the failure was just a temporary pypi access problem. Green now.

[joshmoore]

Good try, but I think it takes a new PR 😉

[jakirkham]

Yeah it may. Sorry pushed a couple more things. There was an old notebook that I reran. It has an issue we might need to follow up on ( #319 ). Also added a release note. Otherwise LGTM

Thanks for working on this Josh! 😄 🙏

[jakirkham]

Hmm..was hoping that would trigger RTD without having to restart all the builds. Doesn't seem to have, but won't push on that any further in this PR.

[jakirkham]

So the wheel job has actually completed, but the status is still showing pending. Going to merge anyways.

[jakirkham]

Still seeing the Python 3.6 status as pending in PR ( #320 ). Guessing we are missing something

[jakirkham]

Think I figured it out. Python 3.6 was still listed in the branch protection rules for master on GitHub. Removing it from that list seems to have fixed the issue.