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

Use install_only_stripped by default in certain cases

Abierto
#4,218 2 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
28/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python

Línea de trabajo

This is a design discussion about when rules_python should default to install_only_stripped runtimes (opt-in today). Read the issue thread for the tradeoff: smaller binaries (~26MB vs up to ~77MB) versus debug symbols needed by tests, especially C++-heavy projects. Suggested scopes include -c opt, py_zipapp in opt mode, and exec mode. Done means maintainers agree on defaults and the flag/runtime selection is updated accordingly; do not implement until that is decided.

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

Descripción

We added the install_only_stripped runtimes to the default set of runtimes and made using them an opt-in choice with a flag.

Using them by default was brought up, but the discussion fizzled, so it was left as opt-in. For reference, a stripped runtime is about 26MB. Unstripped varies, but the largest is the 3.15 free threaded ones, which are 77MB.

Ignas suggested to have -c opt use install_only_stripped. I'm generally +1 on this.

My main reservation with enabling it by default is that tests benefit from having debug symbols, especially for projects that use a lot of C++ code. If we could use stripped runtimes for binaries, but not tests, when in opt mode, that'd be ideal, I think.

Maybe, at the least, we have py_zipapp default to stripped runtimes when in opt mode? That would help address the originating issue of zipapps being too large.

I'll suggest: enable it for exec mode by default. Exec tools are unlikely to need debug symbols and would benefit from a smaller runtime.

cc @gfrankliu @aignas

Lenguaje dominante
Starlark
Estrellas
688
Forks
724
Merge medio
1 d 18 h
PR fusionados (30 d)
46

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 bazel-contrib/rules_python

Todos los issues de bazel-contrib/rules_python

Issues similares

Más issues de Build System

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.