Warn about future changes to adaptive defaults

[svank]

(One new commit on top of the boundary-handling PR, will rebase later)

This warns the user if the default filter kernel or boundary handling mode is being used.

In [3]: reproject.reproject_adaptive((data, w), w, data.shape)
<ipython-input-3-6fbe9b99ba1d>:1: FutureWarning: The default kernel will change from 'Hann' to  'Gaussian' in a future release. To suppress this warning, explicitly select a kernel with the 'kernel' argument.
  reproject.reproject_adaptive((data, w), w, data.shape)
<ipython-input-3-6fbe9b99ba1d>:1: FutureWarning: The default boundary mode will change from 'ignore' to  'strict' in a future release. To suppress this warning, explicitly select a mode with the 'boundary_mode' argument.
  reproject.reproject_adaptive((data, w), w, data.shape)
Out[3]: 
...

In [4]: reproject.reproject_adaptive((data, w), w, data.shape, kernel='hann', boundary_mode='strict')
Out[4]: 
...

I set the default values for these two kwargs to 'default' so we can tell whether the user is relying on the default behavior or explicitly requesting the old behavior. I haven't mentioned the literal value of default in the docs and intend to stop recognizing it in the same commit that changes the defaults, and I hope this temporarily-valid value of default doesn't itself need a deprecation period. LMK if there's a better way.

[codecov]

Codecov Report

Merging #302 (95a95c0) into main (bc88deb) will increase coverage by 0.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #302      +/-   ##
==========================================
+ Coverage   94.30%   94.36%   +0.05%     
==========================================
  Files          23       23              
  Lines         720      727       +7     
==========================================
+ Hits          679      686       +7     
  Misses         41       41              

Impacted Files	Coverage Δ
reproject/adaptive/high_level.py	100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[astrofrog]

@svank - could you rebase this again? Thanks!

[svank]

@astrofrog Done

[astrofrog]

Looks good but could you change 'default' to None as mentioned below?

[astrofrog]

The usual way to deal with this is to actually have kernel=None rather than have 'default' as a special string

[svank]

Ooh, yes, I like that better. Done

[astrofrog]

Looks good to me assuming CI passes. Thanks! Do you have any more PRs that should be considered before I go ahead and do a release? (after which we can finalize/merge the ones to actually change the defaults). I was thinking we could perhaps plan to wait a couple of months before the next release (which would change the defaults) just to make sure we give some time for users to see the warnings.

[svank]

Nope, I'm fresh out of PRs for this next release. Sounds like a plan!