@@ -197,7 +197,7 @@ distributions aren't compatible with
197197stipulates that Python and extension modules are linked against a
198198dynamic musl. This is what you'll find in Alpine Linux, for example.
199199
200- See https://github.com/indygreg /python-build-standalone/issues/86 for
200+ See https://github.com/astral-sh /python-build-standalone/issues/86 for
201201a tracking issue to improve the state of musl distributions.
202202
203203.. _quirk_linux_libx11 :
@@ -249,7 +249,7 @@ The static linking of ``libX11`` and other libraries can cause problems when
249249loaded into the process. For example, extension modules associated with ``PyQt ``
250250are known to link against a shared ``libX11.so.6 ``. If multiple versions of
251251``libX11 `` are loaded into the same process, run-time crashes / segfaults can
252- occur. See e.g. https://github.com/indygreg /python-build-standalone/issues/95.
252+ occur. See e.g. https://github.com/astral-sh /python-build-standalone/issues/95.
253253
254254The conceptual workaround is to not statically link ``libX11 `` and similar
255255libraries into ``libpython ``. However, this requires re-linking a custom
@@ -289,8 +289,8 @@ on ``libcrypt.so.1`` and don't want to upgrade, you can instruct end-users
289289to install a ``libxcrypt-compat `` (or comparable) package to provide the
290290missing ``libcrypt.so.1 ``.
291291
292- See https://github.com/indygreg /python-build-standalone/issues/113 and
293- https://github.com/indygreg /python-build-standalone/issues/173 for additional
292+ See https://github.com/astral-sh /python-build-standalone/issues/113 and
293+ https://github.com/astral-sh /python-build-standalone/issues/173 for additional
294294context on this matter.
295295
296296.. _quirk_references_to_build_paths :
0 commit comments