Skip to content

Conversation

xordoquy
Copy link
Contributor

@xordoquy xordoquy commented Oct 6, 2015

Taking over #3404. Fixes #3372

@carltongibson
Copy link
Collaborator

👍🏽

@xordoquy
Copy link
Contributor Author

xordoquy commented Oct 6, 2015

@carltongibson sorry for the delay

@carltongibson
Copy link
Collaborator

No worries. 😃

@xordoquy xordoquy mentioned this pull request Oct 22, 2015
),
DeprecationWarning,
)
deprecated((3, 0, 0),
Copy link
Member

Choose a reason for hiding this comment

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

The version against this looks wrong, no?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

looks like, will fix that one and the one under.

@xordoquy
Copy link
Contributor Author

PR updated

@xordoquy
Copy link
Contributor Author

Do we really need some coverage or can we merge this ?

@jpadilla
Copy link
Contributor

LGTM although not sure we might want to take care of #3478 (comment) first.

@xordoquy
Copy link
Contributor Author

@lovelydinosaur
Copy link
Member

Are there currently any places where this should be used as part of the PR?

@xordoquy
Copy link
Contributor Author

@tomchristie Not sure it's a good thing to make it part of this PR.

@lovelydinosaur
Copy link
Member

@xordoquy Possibly, but be helpful to enumerate 'em either way.

@lovelydinosaur
Copy link
Member

lovelydinosaur commented Oct 11, 2016

On revisiting this, I'm not convinced we need this wrapper. Managing deprecations hasn't been a pain point for us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants