-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: Possible Regression in DatetimeIndex Slicing #35509
Comments
xref #26206 Also - confirming this is still an issue on master. Ouput of pd.show_versions()INSTALLED VERSIONScommit : 9cbc3e8 pandas : 1.2.0.dev0+17.g9cbc3e811 |
The assertion was added in #31938 cc @jbrockmendel can confirm expected output prior to that change.
|
As far as I can tell this assertion can be removed (the method works fine with lists and numpy arrays it seems). In which case are the annotations for this and related arguments not correct? |
Another fix is to add in
|
moved off 1.1.2 milestone (scheduled for this week) as no PRs to fix in the pipeline |
* Disable cell that raises exception * Fix Treebeard environment and config * Fix treebeard run (#3) * fixes * Update treebeard.yaml * Update treebeard.yaml Co-authored-by: alex-treebeard <alex@treebeard.io> * Migrate to treebeard action * Disable dockerhub usage for now * Add docker hub connection * Add VirES DISC token * Add initial AEBS LPL/PBL notebook * Fix typo * Fix typo #2 * Show EJ extents with shaded regions * Use LPL:Quality & PBL Flags in figure * Move notebooks to subdirectory * Add initial AUX_OBS demo * Clear notebook outputs * Set Treebeard on push & PR's to master & staging * Clear up README * Update nb naming * Tweak nb names * Switch to eoxmagmod master * Adjust spacepy install * Use pandas<1.1 due to pandas bug pandas-dev/pandas#35509 * Switch to staging.vires.services * Add AEBS:LPS nb * Add missing token config * Ignore 04c1 in Treebeard run Co-authored-by: alex-treebeard <alex@treebeard.io>
moved off 1.1.3 milestone (overdue) as no PRs to fix in the pipeline |
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pandas.
(optional) I have confirmed this bug exists on the master branch of pandas.
Note: Please read this guide detailing how to provide the necessary information for us to reproduce your bug.
Code Sample, a copy-pastable example
You now have to run
sort_index()
before slicing:Problem description
Before 1.1.0, you didn't have to sort the index before slicing. Now, you have to run
sort_index()
and the error message is not helpful at all.Expected Output
Output of
pd.show_versions()
INSTALLED VERSIONS
commit : d9fff27
python : 3.7.3.final.0
python-bits : 64
OS : Linux
OS-release : 5.4.40-04224-g891a6cce2d44
Version : #1 SMP PREEMPT Tue Jun 23 20:21:29 PDT 2020
machine : x86_64
processor :
byteorder : little
LC_ALL : None
LANG : en_US.UTF-8
LOCALE : en_US.UTF-8
pandas : 1.1.0
numpy : 1.19.1
pytz : 2020.1
dateutil : 2.8.1
pip : 18.1
setuptools : 40.8.0
Cython : None
pytest : None
hypothesis : None
sphinx : None
blosc : None
feather : None
xlsxwriter : None
lxml.etree : 4.5.2
html5lib : None
pymysql : None
psycopg2 : None
jinja2 : 2.11.2
IPython : 7.16.1
pandas_datareader: 0.9.0
bs4 : None
bottleneck : None
fsspec : None
fastparquet : None
gcsfs : None
matplotlib : 3.3.0
numexpr : None
odfpy : None
openpyxl : None
pandas_gbq : None
pyarrow : None
pytables : None
pyxlsb : None
s3fs : None
scipy : 1.5.2
sqlalchemy : 1.3.18
tables : None
tabulate : None
xarray : None
xlrd : None
xlwt : None
numba : None
The text was updated successfully, but these errors were encountered: