Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Use install_only_stripped by default in certain cases

Aberta
#4,218 2 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
28/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
python
Domínio
build-system, tooling

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
Starlark
Estrelas
688
Forks
724
Merge médio
1d 18h
PRs com merge (30d)
46

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de bazel-contrib/rules_python

Todas as issues de bazel-contrib/rules_python

Issues semelhantes

Mais issues de Build System

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.