Skip to content

Small documentation fixes #1516

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

Merged
merged 3 commits into from
Aug 25, 2017
Merged

Small documentation fixes #1516

merged 3 commits into from
Aug 25, 2017

Conversation

leezu
Copy link
Contributor

@leezu leezu commented Aug 23, 2017

  • Clarify in documentation that inferring DataArray dimensions from dictionary like coords has been deprecated.
  • DataArray docstring

@@ -48,7 +48,7 @@ The :py:class:`~xarray.DataArray` constructor takes:
:py:class:`~pandas.Series`, :py:class:`~pandas.DataFrame` or :py:class:`~pandas.Panel`)
- ``coords``: a list or dictionary of coordinates
- ``dims``: a list of dimension names. If omitted, dimension names are
taken from ``coords`` if possible.
taken from ``coords`` if possible (deprecated).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would vote to remove the deprecated behavior from the docs

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rather than "if possible" I would say "if coords was provided as a list"

(I think that's the only case where it's supported now.)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@shoyer when speaking of list, do you mean a list of tuples (name, [coordinates..])?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, exactly

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great. I have updated the PR accordingly. It seems the format of the list was previously not documented.

@shoyer shoyer merged commit bcd6081 into pydata:master Aug 25, 2017
@shoyer
Copy link
Member

shoyer commented Aug 25, 2017

Thanks

shoyer pushed a commit that referenced this pull request Sep 1, 2017
* Add pathlib support

* Loop over tmpfile functions

* Added show_commit_url to asv.conf (#1515)

* Added show_commit_url to asv.conf

This should setup the proper links from the published output to the commit on Github.

FYI the benchmarks should be running stably now, and posted to http://pandas.pydata.org/speed/xarray. http://pandas.pydata.org/speed/xarray/regressions.xml has an RSS feed to the regressions.

* Update asv.conf.json

* Small documentation fixes (#1516)

* Clarify in docs that inferring DataArray dimensions is deprecated

* Fix DataArray docstring

* Clarify DataArray coords documentation

* Condense pathlib handling for open_mf_dataset

* Add and test pathlib support for backends

* Add pathlib2 for python < 3

* Use pathlib backport if available.

This follows
<jazzband/pathlib2#8 (comment)>
who argues for sticking to pathlib2.

* Use pathlib w DataArray.to_netcdf

* Handle case of completely missing pathlib

* Remove pathlib requirement

* Drop pathlib from minimal test env

* Add what's-new entry on pathlib support

* Prefer stdlib pathlib

* Suppress ImportError's for pathlib

* Acutally get suppress function

* Add decorator for tests requiring pathlib(2)

* Move path_type to central submodule

* Remove unnecessary parens

* Revert "Added show_commit_url to asv.conf (#1515)"

This reverts commit 02023ed.

* Revert "Small documentation fixes (#1516)"

This reverts commit 4276bb8.

* Fix typo in docstring and fallback-module name

* Tweak what's new for pathlib support
@leezu leezu deleted the doc_fix1 branch May 1, 2020 01:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants