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

Remove unused exception class. Closes #2102 #2162

Merged
merged 2 commits into from
Dec 8, 2019

Conversation

casconed
Copy link
Contributor

@casconed casconed commented Oct 4, 2018

No description provided.

Copy link
Contributor

@localheinz localheinz left a comment

Choose a reason for hiding this comment

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

👍

Copy link
Member

@gmponos gmponos left a comment

Choose a reason for hiding this comment

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

IMHO Just to be safe maybe a deprecation notice would be better?

@casconed
Copy link
Contributor Author

casconed commented Dec 8, 2019

@gmponos not sure I see the need for a deprecation notice for a heretofore-unused exception.

@gmponos
Copy link
Member

gmponos commented Dec 8, 2019

Anyway it does not matter anymore.. I think 6.5 will be the last version of v6 which was tagged yesterday. So this can be easily merged for v7.

@Nyholm
Copy link
Member

Nyholm commented Dec 8, 2019

Deprecation notices are the way to go, even if the class is never used.

But master is not targeting 7.0 so no need for that (as @gmponos says).

I've rebased your PR and waiting for the tests to pass.
Thank you!

@Nyholm Nyholm merged commit 4a10630 into guzzle:master Dec 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants