-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
pd.cut fails on readonly arrays #18773
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
Labels
Milestone
Comments
hexgnu
added a commit
to hexgnu/pandas
that referenced
this issue
Dec 18, 2017
This problem was brought up in pandas-dev#18773 and effectively comes down to how Cython deals with readonly arrays. While it would be ideal for Cython to fix the underlying problem in the meantime we can rely on this.
hexgnu
added a commit
to hexgnu/pandas
that referenced
this issue
Dec 18, 2017
This problem was brought up in pandas-dev#18773 and effectively comes down to how Cython deals with readonly arrays. While it would be ideal for Cython to fix the underlying problem in the meantime we can rely on this.
hexgnu
added a commit
to hexgnu/pandas
that referenced
this issue
Dec 18, 2017
This problem was brought up in pandas-dev#18773 and effectively comes down to how Cython deals with readonly arrays. While it would be ideal for Cython to fix the underlying problem in the meantime we can rely on this.
hexgnu
added a commit
to hexgnu/pandas
that referenced
this issue
Dec 18, 2017
This problem was brought up in pandas-dev#18773 and effectively comes down to how Cython deals with readonly arrays. While it would be ideal for Cython to fix the underlying problem in the meantime we can rely on this.
4 tasks
Hey everybody, I submitted a pull request fixing this the best I can. Unfortunately it seems that Cython doesn't handle this super well so the running solution is to check whether something is writeable or not and then to fall back onto ndarray if needed. |
hexgnu
added a commit
to hexgnu/pandas
that referenced
this issue
Dec 18, 2017
This problem was brought up in pandas-dev#18773 and effectively comes down to how Cython deals with readonly arrays. While it would be ideal for Cython to fix the underlying problem in the meantime we can rely on this.
hexgnu
added a commit
to hexgnu/pandas
that referenced
this issue
Dec 22, 2017
This problem was brought up in pandas-dev#18773 and effectively comes down to how Cython deals with readonly arrays. While it would be ideal for Cython to fix the underlying problem in the meantime we can rely on this. fix: updates one_to_hundred for hundred_elements This is because arange(100) isn't actually 1 to 100... it's 0 to 99 docs: adds comment to fix using ndarray and fixes indenting test: parametrize test for test_readonly_cut doc: add new whatsnew entry for v0.23.0 fix: checkout existing upstream v0.22.0
FYI: It looks like Cython closed the source issue with const arrays in February. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Code Sample, a copy-pastable example if possible
Results in:
Problem description
This is essentially the same problem as #10043 and #17192, due to Cython issue cython/cython#1605
Expected Output
Should not error.
Output of
pd.show_versions()
In [73]: pd.show_versions()
INSTALLED VERSIONS
commit: None
python: 3.6.3.final.0
python-bits: 64
OS: Darwin
OS-release: 16.7.0
machine: x86_64
processor: i386
byteorder: little
LC_ALL: None
LANG: en_US.UTF-8
LOCALE: en_US.UTF-8
pandas: 0.20.3
pytest: 3.2.1
pip: 9.0.1
setuptools: 36.4.0
Cython: 0.26
numpy: 1.13.1
scipy: 0.19.1
xarray: 0.10.0
IPython: 6.1.0
sphinx: 1.6.3
patsy: None
dateutil: 2.6.1
pytz: 2017.2
blosc: None
bottleneck: 1.2.1
tables: None
numexpr: None
feather: None
matplotlib: 2.0.2
openpyxl: None
xlrd: None
xlwt: None
xlsxwriter: None
lxml: None
bs4: None
html5lib: 0.999
sqlalchemy: None
pymysql: None
psycopg2: None
jinja2: 2.9.6
s3fs: None
pandas_gbq: None
pandas_datareader: None
The text was updated successfully, but these errors were encountered: