René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"macOS wheels get wrongly tagged as universal2","articleBody":"On macOS when building a wheel of python-ldap, I get one that carries the universal2 tag, which marks it as working on both x86 and ARM: `python_ldap-3.4.4-cp313-cp313-macosx_10_13_universal2.whl`\n\nUnfortunately, it is not, and when a package installer caches the built wheel, it poisons its own cache and installing it on the wrong architecture creates a rather opaque error:\n\n```\n.venv/lib/python3.13/site-packages/ldap/__init__.py:34: in \u003cmodule\u003e\n    import _ldap\nE   ImportError: dynamic module does not define module export function (PyInit__ldap)\n```\n\nThis means I have to clear the cache for python-ldap whenever I switch projects that use a different architecture (e.g., if I want to run `uv lock --upgrade` on both).\n\nThe uv folks [told me](https://github.com/astral-sh/uv/issues/13984) this is a packaging problem that has to be fixed within the project itself.\n\n---\n\nI have attached the build log, because it's too long for inline copy-paste: [build.log](https://github.com/user-attachments/files/20723157/build.log)\n\nNote the linker warnings: `ld: warning: ignoring file 'build/temp.macosx-10.13-universal2-cpython-313/Modules/common.o': found architecture 'arm64', required architecture 'x86_64'`\n\nI ran the build with `uvx --from build pyproject-build`, i.e. the official PyPA builder.","author":{"url":"https://github.com/hynek","@type":"Person","name":"hynek"},"datePublished":"2025-06-13T08:57:41.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/586/python-ldap/issues/586"}