![[BACK]](/icons/back.gif){kind=icon}
Up to [cvs.NetBSD.org] / pkgsrc / net / py-suds
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
py-suds: removed
Add SHA512 digests for distfiles for net category Problems found with existing digests: Package haproxy distfile haproxy-1.5.14.tar.gz 159f5beb8fdc6b8059ae51b53dc935d91c0fb51f [recorded] da39a3ee5e6b4b0d3255bfef95601890afd80709 [calculated] Problems found locating distfiles: Package bsddip: missing distfile bsddip-1.02.tar.Z Package citrix_ica: missing distfile citrix_ica-10.6.115659/en.linuxx86.tar.gz Package djbdns: missing distfile djbdns-1.05-test25.diff.bz2 Package djbdns: missing distfile djbdns-cachestats.patch Package djbdns: missing distfile 0002-dnscache-cache-soa-records.patch Package gated: missing distfile gated-3-5-11.tar.gz Package owncloudclient: missing distfile owncloudclient-2.0.2.tar.xz Package poink: missing distfile poink-1.6.tar.gz Package ra-rtsp-proxy: missing distfile rtspd-src-1.0.0.0.tar.gz Package ucspi-ssl: missing distfile ucspi-ssl-0.70-ucspitls-0.1.patch Package waste: missing distfile waste-source.tar.gz Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
The Suds web services client is a lightweight soap-based client for python the
is licensed under LGPL. Basic features:
* No class generation
* Provides an object-like API.
* Reads wsdl at runtime for encoding/decoding
* Provides for the following SOAP (style) binding/encoding:
- Document/Literal
- RPC/Literal
- RPC/Encoded (section 5)
The goal of suds is to present an RPC-like interface into soap-based web
services. This means that in most cases, users do not need to be concerned with
the complexities of the WSDL and referenced schemas. Regardless of which soap
message style is specified, the signature of the service methods remain the
same. Uses that do examine the WSDL will notice that even with the document
soap message style, the signature of each method resembles an RPC. The method
signature contains the contents of the document defined for the message instead
of the document itself.
Initial revision