simple proposed fix for #289

[pochedls]

Description

This PR represents a simple proposed fix for #289. We just need to use .load() when handling time_lengths (used to make temporal weights. We had to do this for spatial averaging, too (e.g., here).

• Closes [Bug]: TypeError for temporal averaging with multifile datasets #289.

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

If applicable:

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass with my changes (locally and CI/CD build)
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have noted that this is a breaking change for a major release (fix or feature that would cause existing functionality to not work as expected)

[codecov-commenter]

Codecov Report

Merging #291 (a164325) into main (16b3b06) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #291   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           14        14           
  Lines         1143      1146    +3     
=========================================
+ Hits          1143      1146    +3     

Impacted Files	Coverage Δ
xcdat/temporal.py	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 16b3b06...a164325. Read the comment docs.

[tomvothecoder]

One comment then it is good to go, thanks!

[pochedls]

@tomvothecoder - I think the code is fine, but I somehow re-based this in a way that makes it look like Paul's changes are on this PR (I was getting git push errors, but later realized my commits were actually reflected on origin)...

[tomvothecoder]

@tomvothecoder - I think the code is fine, but I somehow re-based this in a way that makes it look like Paul's changes are on this PR (I was getting git push errors, but later realized my commits were actually reflected on origin)...

It could have been a merge pull that placed Paul's changes on top of your's, although I'm not exactly sure why a diff still shows. I squashed your branch and rebased on the latest main, so this doesn't happen anymore.

You can merge this PR now.