Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
some warnings not being silenced #16306
Comments
|
likely a symptom of #13145, we do some |
chris-b1
added the
Error Reporting
label
May 9, 2017
chris-b1
added this to the
Next Major Release
milestone
May 9, 2017
|
@dsm054 always welcome to look into it, if you are interested. |
chris-b1
referenced
this issue
May 22, 2017
Merged
BUG: adding numpy errstate to dataframe/series broadcasting (GH16378) #16433
jreback
modified the milestone: 0.20.2, Next Major Release
May 22, 2017
TomAugspurger
referenced
this issue
in dask/dask
May 24, 2017
Open
Policy for RuntimeWarnings for dask.dataframe #2381
TomAugspurger
closed this
in #16433
May 25, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
dsm054 commentedMay 9, 2017
•
edited by jorisvandenbossche
Some comparison operations seem to escape the silencing of numpy RuntimeWarnings. For example:
all give
This is working with some timeseries data after some rolling operations, and so there are going to be lots of NaNs floating around. It'd be nice if I didn't need to suppress them myself.
Output of
pd.show_versions()INSTALLED VERSIONS
commit: None
python: 3.6.1.final.0
python-bits: 64
OS: Linux
OS-release: 4.4.0-77-generic
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: en_CA.UTF-8
LOCALE: en_CA.UTF-8
pandas: 0.20.1
pytest: 3.0.7
pip: 9.0.1
setuptools: 27.2.0
Cython: 0.25.2
numpy: 1.12.1
scipy: 0.19.0
xarray: 0.9.1
IPython: 5.3.0
sphinx: 1.5.1
patsy: 0.4.1
dateutil: 2.6.0
pytz: 2016.10
blosc: None
bottleneck: 1.2.0
tables: 3.3.0
numexpr: 2.6.2
feather: None
matplotlib: 2.0.0
openpyxl: 2.4.1
xlrd: 1.0.0
xlwt: 1.2.0
xlsxwriter: 0.9.6
lxml: 3.7.3
bs4: 4.5.3
html5lib: 0.999
sqlalchemy: 1.1.6
pymysql: None
psycopg2: None
jinja2: 2.9.5
s3fs: None
pandas_gbq: None
pandas_datareader: None