Skip to content

Conversation

@eric-wieser
Copy link
Member

@eric-wieser eric-wieser commented Apr 6, 2017

Now matches:

  • its own documentation
  • everything else

Fixes #8701


Should this be considered a breaking change? Do we want to go through a deprecation cycle that requires this argument to be specified explicitly when needed? Something like <snip> #8918

Continuing from a forgotten discussion with @juliantaylor at #8678 (comment)

@rgommers
Copy link
Member

Yeah, this is a breaking change. There's something to be said for Julian's position of "this ship has sailed", and also for making the user specify axis explicitly and keeping the FutureWarning in place for several releases. We can't just change the default.

@eric-wieser eric-wieser modified the milestone: 1.14.0 release Apr 10, 2017
@eric-wieser
Copy link
Member Author

Ok, I'll leave this as is for when that "several releases" time comes.

In the mean time, I've got a deprecating version at #8918

Only deprecated when this would be ambiguous.

Approaches numpy#8701
Now matches:
 * its own documentation
 * everything else

Fixes numpy#8701
@homu
Copy link
Contributor

homu commented Apr 28, 2017

☔ The latest upstream changes (presumably #8996) made this pull request unmergeable. Please resolve the merge conflicts.

@eric-wieser
Copy link
Member Author

Closing this, since it'll be easier just to make a new PR to remove this deprecation

@eric-wieser eric-wieser closed this May 6, 2017
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.

3 participants