I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandas.
I have confirmed this bug exists on the main branch of pandas.
df = pd.DataFrame({ 'ts': [], 'values': [] }).astype({'ts': 'datetime64[ns, Atlantic/Faroe]'}) df.resample('2MS', on='ts', closed='left', label='left', origin='start')['values'].sum().index
this prints
DatetimeIndex([], dtype='datetime64[ns]', name='ts', freq='2MS')
DatetimeIndex([], dtype='datetime64[ns, Atlantic/Faroe]', name='ts', freq='2MS')
note that this works fine if the series isn't empty
In [27]: df = pd.DataFrame({ ...: 'ts': [datetime(2020, 1, 1)], ...: 'values': [10] ...: }) ...: df['ts'] = df['ts'].dt.tz_localize('Atlantic/Faroe') ...: df.resample('2MS', on='ts', closed='left', label='left', origin='start')['values'].sum().index Out[27]: DatetimeIndex(['2020-01-01 00:00:00+00:00'], dtype='datetime64[ns, Atlantic/Faroe]', name='ts', freq='2MS')
commit : 965cecapython : 3.10.6.final.0python-bits : 64OS : LinuxOS-release : 5.10.102.1-microsoft-standard-WSL2Version : #1 SMP Wed Mar 2 00:30:59 UTC 2022machine : x86_64processor : x86_64byteorder : littleLC_ALL : NoneLANG : en_GB.UTF-8LOCALE : en_GB.UTF-8
pandas : 2.0.2numpy : 1.24.3pytz : 2023.3dateutil : 2.8.2setuptools : 67.6.1pip : 23.0.1Cython : Nonepytest : 7.3.1hypothesis : Nonesphinx : Noneblosc : Nonefeather : Nonexlsxwriter : Nonelxml.etree : Nonehtml5lib : Nonepymysql : Nonepsycopg2 : Nonejinja2 : 3.1.2IPython : 8.13.2pandas_datareader: Nonebs4 : 4.12.2bottleneck : Nonebrotli : Nonefastparquet : Nonefsspec : Nonegcsfs : Nonematplotlib : 3.7.1numba : Nonenumexpr : Noneodfpy : Noneopenpyxl : Nonepandas_gbq : Nonepyarrow : 12.0.0pyreadstat : Nonepyxlsb : Nones3fs : Nonescipy : Nonesnappy : Nonesqlalchemy : Nonetables : Nonetabulate : Nonexarray : Nonexlrd : Nonezstandard : Nonetzdata : 2023.3qtpy : Nonepyqt5 : None
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Pandas version checks
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandas.
I have confirmed this bug exists on the main branch of pandas.
Reproducible Example
Issue Description
this prints
Expected Behavior
note that this works fine if the series isn't empty
Installed Versions
INSTALLED VERSIONS
commit : 965ceca
python : 3.10.6.final.0
python-bits : 64
OS : Linux
OS-release : 5.10.102.1-microsoft-standard-WSL2
Version : #1 SMP Wed Mar 2 00:30:59 UTC 2022
machine : x86_64
processor : x86_64
byteorder : little
LC_ALL : None
LANG : en_GB.UTF-8
LOCALE : en_GB.UTF-8
pandas : 2.0.2
numpy : 1.24.3
pytz : 2023.3
dateutil : 2.8.2
setuptools : 67.6.1
pip : 23.0.1
Cython : None
pytest : 7.3.1
hypothesis : None
sphinx : None
blosc : None
feather : None
xlsxwriter : None
lxml.etree : None
html5lib : None
pymysql : None
psycopg2 : None
jinja2 : 3.1.2
IPython : 8.13.2
pandas_datareader: None
bs4 : 4.12.2
bottleneck : None
brotli : None
fastparquet : None
fsspec : None
gcsfs : None
matplotlib : 3.7.1
numba : None
numexpr : None
odfpy : None
openpyxl : None
pandas_gbq : None
pyarrow : 12.0.0
pyreadstat : None
pyxlsb : None
s3fs : None
scipy : None
snappy : None
sqlalchemy : None
tables : None
tabulate : None
xarray : None
xlrd : None
zstandard : None
tzdata : 2023.3
qtpy : None
pyqt5 : None
The text was updated successfully, but these errors were encountered: