Fixes #229: Pinning xarray to avoid issues with underlying call to pa…

[JimCircadian]

…necessary to fix the broken operational forecasts. Already dealt with in 0.3 dev

[bnubald]

Pinning xarray version still causes error.

Cause of #229 was Pandas >= 2.0.0 (see #229 (comment))

Also, not strictly necessary, but would prefer if if pinning was set specifically just for 3.8, to not be too restrictive for future versions.

pandas<2; python_version == '3.8'
xarray[io]<2023.2.0; python_version == '3.8'
xarray[io]; python_version > '3.8'

[JimCircadian]

Pinning xarray version still causes error.

Cause of #229 was Pandas >= 2.0.0 (see #229 (comment))

Also, not strictly necessary, but would prefer if if pinning was set specifically just for 3.8, to not be too restrictive for future versions.

pandas<2; python_version == '3.8'
xarray[io]<2023.2.0; python_version == '3.8'
xarray[io]; python_version > '3.8'

Updated the changes, though I'm not keen on pinning solely for specific python versions as it makes it more likely we develop against newer features.

I think this makes the case for eventual dropping of 3.8, but let's pick that up for the 0.3 branch if that's OK?

[bnubald]

Still a typo.

[bnubald]

Pinning xarray version still causes error.
Cause of #229 was Pandas >= 2.0.0 (see #229 (comment))
Also, not strictly necessary, but would prefer if if pinning was set specifically just for 3.8, to not be too restrictive for future versions.

pandas<2; python_version == '3.8'
xarray[io]<2023.2.0; python_version == '3.8'
xarray[io]; python_version > '3.8'

Updated the changes, though I'm not keen on pinning solely for specific python versions as it makes it more likely we develop against newer features.

I think this makes the case for eventual dropping of 3.8, but let's pick that up for the 0.3 branch if that's OK?

👍🏼