As discussed in #1706. I think a deprecation warning in 3.0 is the way to go.
As discussed in #1706.
I think a deprecation warning in 3.0 is the way to go.