Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Provide python executable compiled with enable-shared

Abierto
  • ¿Algo no está bien?
#595 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python, shell
Área
build-system

Línea de trabajo

Empieza leyendo la configuración de múltiples salidas de la receta, build_base.sh, build_shared y build_static. Comprueba cómo conda_build_config.yaml afecta a la compilación de macOS y revisa los fallos notificados de tkinter y de las bibliotecas compartidas. Se considera completado cuando un subpaquete compatible proporciona un ejecutable de Python compilado con enable-shared y supera las pruebas pertinentes del paquete.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

question
Comment:

Related: https://github.com/conda-forge/python-feedstock/issues/222#issuecomment-1309248101 .
My use-case: https://github.com/lammps/lammps/issues/3520

This could be provided as a subpackage, say python-shared, and install a python.VERSION_shared that the user could symlink or put in front of $PATH, as needed.

I would have built it myself but I am a bit lost since building this recipe with enable-shared is not being easy.

The usual ways of debugging a failing conda build do not work with this package: conda debug ends up giving me an environment where there's no script to activate the environment and no build script either, perhaps because the recipe has multiple outputs and conda debug does not know what to do with it.

So far had to remove the libpython-static output, make the recipe a single output recipe, move build_base.sh to build.sh, edit out script:build.sh, comment out rm .../libpython(...)$VERSION(...).a in build_shared, and add f to ln -sf ../../libpython${VERABI}.a libpython${VERABI}.a in build_static.

The last hurdle is that after building, conda build packages it, where it alters the paths that libraries/execs refer too ( I'm not very knowledgeable about this) and it fails with this message, which I guess has to do with signing in osx-arm64.
PS: fixed it by editing conda-builld/.../post.py https://github.com/conda/conda-build/issues/4392#issuecomment-1310893278

Tests do not pass (tkinter something), but I installed the package anyways and for my use-case it seems to function
PS: does not. conda_build_config.yaml included in the repo overrode the one I had in my home folder, so it did not pick up on the openssl==1.1 constraint and then when I replaced the python in my installation with the shared one it complained it could not find libssl.3.dylib.

After fixing that, for some reason 'libffi.7.dylib' was required by 'import _ctypes', which I fixed in the install environment by symlinking 'libffi.8.dylib' to 'libffi.7.dylib'.

Lenguaje dominante
Shell
Estrellas
47
Forks
114
Merge medio
7 d 6 h
PR fusionados (30 d)
14

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de conda-forge/python-feedstock

Todos los issues de conda-forge/python-feedstock

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.