Skip to content

docs(pypi): plan pure-Python packages on GCCcore as EESSI does - #48

Merged
HaoZeke merged 1 commit into
mainfrom
fix/pypi-gcccore
Nov 16, 2026
Merged

HaoZeke merged 1 commit into
mainfrom
fix/pypi-gcccore

Conversation

@HaoZeke

@HaoZeke HaoZeke commented Nov 16, 2026

Copy link
Copy Markdown
Collaborator

The PyPI how-to and the package-plan skill plan the pure-Python beautifulsoup4 example on GCCcore/15.2.0, with a GCCcore policy and a real GCCcore-15.2.0 fixture robot.

  • The page inspected and planned beautifulsoup4 on foss/2026.1. EESSI 2026.06 installs Python, Python-bundle-PyPI and BeautifulSoup on GCCcore-15.2.0. A module built on foss/2026.1 loads foss, and with it OpenMPI and FlexiBLAS, for a package that uses neither. The fixture robot's files were named GCCcore-14.2.0 but declared foss/2026.1, so a plan at GCCcore/15.2.0 found no Python.
  • The fixture robot now holds Python 3.14.2 and Python-bundle-PyPI 2026.04 on GCCcore-15.2.0. examples/stacks/eessi-python-gcccore.toml is the matching policy. The numpy example stays on foss/2026.1, because SciPy-bundle is never on GCCcore.

foreign_plan_howtos_use_the_fixture_robots runs the bs4 plan at GCCcore/15.2.0 and checks that the page and the skill show that command. The commit has a towncrier fragment. Main has no towncrier yet; #26 (fix/towncrier) adds it.

The PyPI how-to inspected and planned beautifulsoup4 on foss/2026.1,
and the package-plan skill did the same. EESSI 2026.06 installs
Python, Python-bundle-PyPI and BeautifulSoup on GCCcore-15.2.0. A
module built on foss/2026.1 loads foss, and with it OpenMPI and
FlexiBLAS, for a package that uses neither. The fixture robot could
not show the right toolchain either: its files were named
GCCcore-14.2.0 but declared foss/2026.1, so a plan at GCCcore/15.2.0
found no Python.

The fixture robot now holds Python 3.14.2 and Python-bundle-PyPI
2026.04 on GCCcore-15.2.0, as EESSI 2026.06 does. Its bundle still
provides soupsieve, standing in for the real tree, where BeautifulSoup
carries it. examples/stacks/eessi-python-gcccore.toml is the matching
policy, since a stack policy's toolchain must be the plan's. The page
says which to pick: numpy comes from SciPy-bundle, which EESSI installs
on gfbf/2026.1, so the numpy example stays on foss/2026.1 with
eessi-python-extras.toml.

foreign_plan_howtos_use_the_fixture_robots runs the bs4 plan at
GCCcore/15.2.0 and checks that the page and the skill show that
command and the recipe's dependencies. It fails without the fixture
change.
@HaoZeke
HaoZeke merged commit 96d7fa3 into main Nov 16, 2026
21 checks passed
@HaoZeke
HaoZeke deleted the fix/pypi-gcccore branch November 16, 2026 05:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant