Incompatibility with guzzle 5 about webapiextension HOT 7 CLOSED

No, it should not be changed to suggest, as it is a hard requirement. But we could change the constraint to allow both 4 and 5

from webapiextension.

That's right. I'm going to run the tests with 5, to see if the extension uses a part of the api that would have changed.

from webapiextension.

What is the status of this ticket? The actual guzzle requirement conflicts with some of my projects.
This merge could help.

from webapiextension.

I this discussed with @stof, and I think it will get merged, but not right now. If you are stuck, use my fork in an inline alias.

from webapiextension.

Thanks ... I will do that

from webapiextension.

This is also conflicting with dependencies in my project also. Thanks for all the help.

from webapiextension.

Any movement on this or are we all using the forked version?

from webapiextension.