Incompatibility with httpx 0.28.0

[decaz]

Since version 0.28.0 of httpx The deprecated proxies argument has now been removed.:

python-zeep/src/zeep/transports.py

Lines 186 to 195 in 41a5115

	self.wsdl_client = wsdl_client or httpx.Client(
	verify=verify_ssl,
	proxies=proxy,
	timeout=timeout,
	)
	self.client = client or httpx.AsyncClient(
	verify=verify_ssl,
	proxies=proxy,
	timeout=operation_timeout,
	)

[TB99930]

If anyone is experiencing this problem, simply fix your version of httpx, using an exact version pre-0.28 or the qualifier <0.28 until the attached PR is merged.

For example: httpx>=0.26,<0.28 or httpx==0.27.2

[ba1dr]

If anyone is experiencing this problem, simply fix your version of httpx, using an exact version pre-0.28 or the qualifier <0.28 until the attached PR is merged.

For example: httpx>=0.26,<0.28 or httpx==0.27.2

I think this is a bad solution, as other libraries may require newer version or have another constraint.
Perhaps we can just initialize clients outside and pass to the Transport's constructor:

wsdl_client = httpx.Client(
    verify=sslcontext,
    timeout=HTTP_TIMEOUT,
)
httpx_client = httpx.AsyncClient(verify=sslcontext,
                                 timeout=HTTP_TIMEOUT)
transport = AsyncTransport(client=httpx_client, wsdl_client=wsdl_client)
zclient = ZeepClient(
    wsdl_file, transport=transport,
    service_name=bind_soap_service, port_name=bind_soap_port
)

[kostyaten]

When will the update be?

[PrieJos]

Hi @ba1dr

Could you please at least tell us whether there is any plan to fix this incompatibility issue or not?

Thanks
Jose M. Prieto

[ba1dr]

Hi @ba1dr

Could you please at least tell us whether there is any plan to fix this incompatibility issue or not?

Thanks Jose M. Prieto

I literally have no idea, as I am just the same user of this library as you. Looking at the past releases timeline I can only conclude that the author is busy and this library is semi-abandoned.

Perhaps eventually this will be fixed, but at the moment the best we can do is either override this issue with one of the examples above or make a fork and fix it for yourself.

[PrieJos]

Hi @ba1dr

Oops, sorry for that. I don’t know why I came to the conclusion you were the developer. My apologies.

Perhaps eventually this will be fixed, but at the moment the best we can do is either override this issue with one of the examples above or make a fork and fix it for yourself.

Fully agree with you. Let’s see.

Cheers
José M Prieto

[K3str3l]

If anyone is experiencing this problem, simply fix your version of httpx, using an exact version pre-0.28 or the qualifier <0.28 until the attached PR is merged.

For example: httpx>=0.26,<0.28 or httpx==0.27.2

If I understand correctly, I tried both of the above suggestions in the manifest.json in the \config\custom_components\kingspan_watchman_sensit folder, but each time I restarted after the change the intergration I receive an error.
Do I need to download a file from "somewhere"?

thanks in advance for any direction

[masaccio]

If anyone is experiencing this problem, simply fix your version of httpx, using an exact version pre-0.28 or the qualifier <0.28 until the attached PR is merged.

For example: httpx>=0.26,<0.28 or httpx==0.27.2

That doesn’t work for Home Assistant for example which requires latest httpx. The code from @ba1dr works well and it’s what I am doing in my HA integration.

[alexrohozneanu]

Are there any news on this?