RFS python-mcp

--e1ec4c9ee72bdb4ff29dee1235187656c9d1fe3d9d5fb02013b78c37b539
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8

Dear Python team,

I've packaged anthropics MCP python SDK because it is a dependency for home
assistant.

Package is at https://salsa.debian.org/python-team/packages/python-mcp

There was an ITP bug at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
=3D1115742

Can someone please review my work? If its fine, upload it or give me upload
rights? Not sure if that can work on new packages?

Two questions I have:
1. I added a man page. I created that from markdown, but to keep pandoc out=
 of the
build process I manually converted the md to troff and kept both in the deb=
ian
dir. Is that fine or should I build the troff file from my markdown source?

2. I now have the second package that uses network calls during tests. They
break in gbp buildpackage because I use auto-apt-proxy. I work around that =
with
a fixture unsetting HTTPS?_PROXY env vars. Is that the way to go? I doubt w=
e
want to bother all upstream packages to unset HTTPS?_PROXY vars like that?

Thanks in advance,

Pieter

--e1ec4c9ee72bdb4ff29dee1235187656c9d1fe3d9d5fb02013b78c37b539
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iIkEABYKADEWIQQrLg4/tS9aUxZMq8oFuPKwcqDg6wUCakDZnxMccGxlbmFlQGRp
c3Jvb3Qub3JnAAoJEAW48rByoODr8U0BAII4HNYlbXwBTZIL5CHN+U+dVYE1jkml
WnCNpBd034gNAP981OZ4w2PVDjOZzyJ+13WDtJqv5pmlNSCK8wzH4yJECg==
=RQET
-----END PGP SIGNATURE-----

--e1ec4c9ee72bdb4ff29dee1235187656c9d1fe3d9d5fb02013b78c37b539--