On Wed, 21 Oct 2026 at 11:06, <[email protected]> wrote: > Send lxml - The Python XML Toolkit mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.python.org/mailman3/lists/lxml.python.org/ > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of lxml - The Python XML Toolkit digest..." > > Today's Topics: > > 1. lxml 6.1.2 Windows wheel - native build provenance and LGPL > relinking materials > (Kontakt ScheuerWerk) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 21 Oct 2026 08:47:19 +0200 > From: "Kontakt ScheuerWerk" <[email protected]> > Subject: [lxml] lxml 6.1.2 Windows wheel - native build provenance and > LGPL relinking materials > To: <[email protected]> > Message-ID: <[email protected]> > Content-Type: multipart/related; > boundary="----=_NextPart_000_0029_01DD6138.C9012060" > > Hello lxml maintainers, > > > > We are preparing the redistribution of a Windows desktop application that > includes the official lxml 6.1.2 wheel for CPython 3.13 x64. > > > > Wheel: lxml-6.1.2-cp313-cp313-win_amd64.whl > > > > SHA-256: 6cb0c87421946030b92b558be416852780a912454e3dcba0998e4497c9c588d5 > > > > We would like to establish a reproducible compliance and replacement > procedure for the statically linked GNU libiconv dependency. > > Could you please help us identify: > > > > 1. The exact native source commits, patches, headers and library > artifacts used to build this wheel. > 2. Whether the artifacts from lxml/libxml2-win-binaries, release > 2026.05.17, were used unchanged. > 3. The compiler, Windows SDK and linker settings used. > 4. Any existing reproducible build or relinking instructions for > rebuilding the native extensions with a modified LGPL library. > > > > We have already identified the relevant upstream sources and build > materials, but would appreciate confirmation of their relationship to this > particular wheel. > > We are not reporting a defect. Our goal is to provide the appropriate LGPL > materials and a technically workable replacement procedure when > distributing > the application. > > Thank you for your assistance. > > > > Mit freundlichen Grüßen > > Martin Radoy > ScheuerWerk > > E-Mail: <mailto:[email protected]> [email protected] > Web: <https://scheuerwerk.de> https://scheuerwerk.de > > Wenn ihr das Projekt freiwillig unterstützen möchtet: > <https://scheuerwerk.de/support/> https://scheuerwerk.de/support/ > > > > _____ > I have seen these messages on the NumPy and scipy-openblas issue trackers. > The author does not respond to requests for clarification. I can’t work out > what they are after.
Matti > > > > > > > > -------------- next part -------------- > A message part incompatible with plain text digests has been removed ... > Name: not available > Type: text/html > Size: 6724 bytes > Desc: not available > -------------- next part -------------- > A message part incompatible with plain text digests has been removed ... > Name: image001.png > Type: image/png > Size: 294600 bytes > Desc: not available > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > lxml - The Python XML Toolkit mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3//lists/lxml.python.org > > > ------------------------------ > > End of lxml - The Python XML Toolkit Digest, Vol 171, Issue 3 > ************************************************************* >
_______________________________________________ lxml - The Python XML Toolkit mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3//lists/lxml.python.org Member address: [email protected]
