Kevin Anderson

Thanks @roger-lcc! Can you take a look at addressing the [Stickler CI](https://github.com/pvlib/pvlib-python/pull/1443/files) comments about code formatting?

Ah, sorry for the confusion. It's okay to ignore the `Test` checks for this PR. What's happening is that pvlib has some functions to make internet requests to external servers...

A bit of relevant discussion here: https://github.com/pvlib/pvlib-python/discussions/1310

@mikofski Solcast and Engerer don't seem related to me, what's the connection? Or maybe you meant another issue?

Ha, of course! I think #1366 does not supercede this one: decomposition function in `pvlib.irradiance` vs data fetching function in `pvlib.iotools`.

I think it is just the annoying but secure behavior of `pull-request-target` not respecting `yml` changes in the PR -- your update to include the SA key in the environment...

Well the `pvlib._deprecation.deprecated` has `since` and `removal` parameters and inserts that `.. deprecated::` directive into the docstring too. But it inserts the directive at the top of the docstring so...

@wholmgren said in https://github.com/pvlib/pvlib-python/issues/1214#issuecomment-902819052 that we should think through how xarray and dask are used in pvlib, and now that 0.9.0 is out I guess we can do that. This...

Ready for review. I guess the long and the short of it is that we should have been listing all packages (including sub-packages and even `pvlib.data`) all along, and until...

After merging master and updating the `MANIFEST.in` `prune` and `exclude` entries, the difference in `tar.gz` contents between v0.9.1 and 70c9ab3e looks as expected: ```diff 13a14 > docs/examples/bifacial/plot_pvfactors_fixed_tilt.py 133a135 > docs/sphinx/source/whatsnew/v0.9.2.rst...