I'd like to get a review/merge some form of this PR before releasing 1.8.0: #818

@b-butler Can you help me understand what all the refactoring commits are doing? Are there warnings that you're trying to suppress? Are there tasks we missed that should be reviewed and merged into master as separate PRs? (Typically "release" PRs are trivial and only involve version bumps.)

I worked through the deprecations with @b-butler and @mikemhenry on #820 in real time.

Codecov Report

Merging #819 (52a365d) into master (c9a48fc) will decrease coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #819      +/-   ##
==========================================
- Coverage   78.46%   78.42%   -0.05%     
==========================================
  Files          64       64              
  Lines        7230     7230              
  Branches     1465     1465              
==========================================
- Hits         5673     5670       -3     
  Misses       1244     1244              
- Partials      313      316       +3     

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Before this is ready to release, we need a new GitHub Action to deploy to the test PyPI server (and the real PyPI when we merge/tag).

Before this is ready to release, we need a new GitHub Action to deploy to the test PyPI server (and the real PyPI when we merge/tag).

@bdice @b-butler I handled this in #821.

The package now builds wheels and publishes to TestPyPI correctly, so I think it should be good to merge.

Agreed! This is ready to go. @b-butler You can merge and finalize the GitHub release.