Skip to content
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

Removals of all deprecated stuff #1286

Merged
merged 9 commits into from Jan 11, 2020
Merged

Conversation

dopplershift
Copy link
Member

Description Of Changes

Remove everything we said was going away in 1.0:

  • Everything in Removals/Deprecations in 1.0 #1127
  • XArray deprecated behavior--@jthielen can you review? The last test in test_xarray.py passes and that makes me nervous
  • Move functions from future.py into their home (leave future.py empty)
  • Fix current build failure due to more skewT tests failing with Pint10 (degC -> degrees_Celsius)
  • Remove some old Python 2 code

This DOES NOT remove dim_order which is something else that needs to die in 1.0.

Checklist

This really should have been done when we deprecated it. Oops.
More places where degC became degrees_Celsius. Since this isn't an
important part of the test, just set the label and be done.
@dopplershift dopplershift added Area: Calc Pertains to calculations Area: Docs Affects documentation Area: Examples Affects examples Type: API Change Changes to how existing functionality works Type: Maintenance Updates and clean ups (but not wrong) labels Jan 10, 2020
@dopplershift dopplershift added this to the 1.0 milestone Jan 10, 2020
Copy link
Collaborator

@jthielen jthielen left a comment

Choose a reason for hiding this comment

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

Here's the main thing you appeared to have missed in xarray.py:

require_1d_coord = ['time', 'vertical']  # TODO: Add 'y', 'x' in v1.0

should be updated to

require_1d_coord = ['time', 'vertical', 'y', 'x']

This should then allow you to modify that last test to check for AttributeError on accessing x or y, instead of actually accessing them according to the old behavior.

Also, could you update the docstrings for .y and .x?

@dopplershift
Copy link
Member Author

That make sense. I think I got it now.

…ta#1112)

This makes their behavior standard and eliminates the old behavior.
@dopplershift dopplershift merged commit f936150 into Unidata:master Jan 11, 2020
@dopplershift dopplershift deleted the break-stuff branch January 11, 2020 20:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Calc Pertains to calculations Area: Docs Affects documentation Area: Examples Affects examples Type: API Change Changes to how existing functionality works Type: Maintenance Updates and clean ups (but not wrong)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Removals/Deprecations in 1.0 ageostrophic_wind call signature
2 participants