pull_requests: 248922709

This data as json

id node_id number state locked title user body created_at updated_at closed_at merged_at merge_commit_sha assignee milestone draft head base author_association auto_merge repo url merged_by
248922709 MDExOlB1bGxSZXF1ZXN0MjQ4OTIyNzA5 2727 closed 0 silence a couple of warnings in tests 5635139 The only other warning is: ``` xarray/tests/test_dataset.py::TestDataset::test_convert_dataframe_with_many_types_and_multiindex /Users/maximilian/workspace/xarray/xarray/core/dataset.py:3146: FutureWarning: Converting timezone-aware DatetimeArray to timezone-naive ndarray with 'datetime64[ns]' dtype. In the future, this will return an ndarray with 'object' dtype where each element is a 'pandas.Timestamp' with the correct 'tz'. To accept the future behavior, pass 'dtype=object'. To keep the old behavior, pass 'dtype="datetime64[ns]"'. data = np.asarray(series).reshape(shape) /usr/local/lib/python3.7/site-packages/pandas/core/apply.py:286: FutureWarning: Converting timezone-aware DatetimeArray to timezone-naive ndarray with 'datetime64[ns]' dtype. In the future, this will return an ndarray with 'object' dtype where each element is a 'pandas.Timestamp' with the correct 'tz'. To accept the future behavior, pass 'dtype=object'. To keep the old behavior, pass 'dtype="datetime64[ns]"'. results[i] = self.f(v) ``` I'm not sure what we want to do here - potentially we should make a choice between: - the worse behavior of `object` - accepting the coercing to naive datetimes - supporting pandas extension arrays 2019-01-30T15:37:41Z 2019-01-30T19:06:37Z 2019-01-30T19:06:34Z 2019-01-30T19:06:34Z 5527f693fc0a39cd04db7aa6b4fd95edbe722921     0 1cbdb98d3988cefd6dfe24a2c42bb296c8f4b36d e8bf4bf9a744148f1f6586cabe7f5c5ef6e9bf26 MEMBER   13221727 https://github.com/pydata/xarray/pull/2727  

Links from other tables