I was building a conda environment with unpinned packages:
aiohttp
erddapy
fsspec
netCDF4
packaging
scipy
toolz
xarray
pandas
numpy
When conda/mamba solve this, it peaks the Pandas version 2.0
from which erddapy is trying to import parse_time_string from pandas._libs.tslibs.parsing
but the parse_time_string function is not longer available there (apparently it was removed after v2.0.0.dev0)
following the function signature, it looks to have been replaced by: parse_datetime_string_with_reso, which was in fact called by parse_time_string code.
I was building a conda environment with unpinned packages:
When conda/mamba solve this, it peaks the Pandas version 2.0 from which erddapy is trying to import
parse_time_string
frompandas._libs.tslibs.parsing
but theparse_time_string
function is not longer available there (apparently it was removed after v2.0.0.dev0)following the function signature, it looks to have been replaced by: parse_datetime_string_with_reso, which was in fact called by
parse_time_string
code.May be erddapy could simply rely on py_parse_datetime_string in here ?
this looks like a recurrent issue for erddapy (#128 #34 #240 )