---------- Forwarded message --------- From: Dennis Alo <[email protected]> Date: Sat, Oct 31, 2026 at 3:47 PM Subject: lxml 6.1.3 Windows CPython 3.14 — GNU libiconv LGPL Redistribution and Relinking Guidance To: <[email protected]>
Dear lxml Development Team, Greetings from the Philippines. I am preparing the commercial distribution of HAL Parish Records Management System, a Windows desktop application developed in Python that includes lxml 6.1.3. We are reviewing third-party licensing compliance, particularly the GNU libiconv dependency under LGPL 2.1. *Our environment:* - lxml: 6.1.3 - Python: CPython 3.14, Windows x86-64 - Extension: etree.cp314-win_amd64.pyd - SHA-256: 191EEE78B34979C31BA08D952CA3CAFABAFE2F86D81ADEF19F0BCD44AD2EA53C9 - Compiled libxml2: 2.11.9 - Compiled libxslt: 1.1.45 Our inspection found a reference to libiconv in the extension binary, but no separately imported iconv DLL. We have already collected the lxml license files, including LICENSE.txt and LICENSES.txt. Could you kindly clarify: 1. Whether the official lxml 6.1.3 Windows CPython 3.14 x64 wheel statically links GNU libiconv. 2. Which exact libiconv source version, patches, and native-library archives were used. 3. Whether the corresponding build configuration, object files, or other relinking materials are publicly available. 4. What reproducible rebuilding or relinking procedure you recommend for distributors seeking to satisfy LGPL 2.1 requirements. We are not reporting a software defect. Our objective is to comply with the applicable licenses while distributing our application commercially. Thank you very much for your time and for maintaining lxml. Respectfully, *Dennis Alibangbang Alo* Developer — HAL Parish Records Management System HAL Digital Solutions Philippines
_______________________________________________ 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]
