astral-sh/python-build-standalone

Update validation to check that all symbols are available in object files

Open

#459 opened on Dec 30, 2024

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Python (293 forks)github user discovery
help wanted

Repository metrics

Stars
 (4,135 stars)
PR merge metrics
 (Avg merge 6d 14h) (12 merged PRs in 30d)

Description

As described in https://github.com/astral-sh/python-build-standalone/issues/378

It'd be nice to prevent this class of bug by asserting that all libpython symbols are available in the distribution object files.

Contributor guide

Research direction
Look at the build scripts in the repository, specifically how libpython is built. Use tools like `nm` or `objdump` to list exported symbols from object files and compare against expected symbols from the Python shared library. Write a script that runs during CI to assert all symbols are present.
Tech stack
python
Domain
build system
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
PythonBasic understanding of object files (ELF/COFF/Mach O)
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55