Front end: set a machine up for a development build from the window

Abierto
  • ¿Algo no está bien?
#575 0 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python
Área
backend, desktop

Línea de trabajo

Read gui/src/solprop_gui/ui/setup_dialog.py and src/solprop/service/install.py (setup_script, copy_wheels), then inspect native/scripts/fetch_wheel.py and the Linux wheel constraints from #570. Trace how the dialog prepares and shows the setup script before it runs. Done means a development build can prepare a fresh Linux machine from the dialog, explain when no matching native wheel exists, and complete a run; the issue says this is recorded manually.

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

Descripción

area: gui enhancement priority: low
What is missing

Run → Machines… → Set up solprop there… (from #571, solprop.service.install) installs solprop at the window's version from PyPI, or from wheels the user adds. A release works. A development build does not: PyPI has no 0.2.1.devN+g…, so the dialog refuses it unless wheels are added, and the user has no easy way to get wheels that work on the machine. The window's own solprop wheel can be built anywhere (pure Python), but solprop-native must be a Linux wheel for the machine, and the one CI builds per commit needs glibc 2.35 and a system FFTW (#570).

Why it matters

Testing the front end's remote machines against a branch needs a hand-made environment on each machine today (a checkout, a light sync and a borrowed FFTW). A developer, or a user on a pre-release, cannot set a machine up from the window.

Context
  • src/solprop/service/install.py (setup_script, copy_wheels), gui/src/solprop_gui/ui/setup_dialog.py.
  • #570, CI's Linux native wheel.
  • native/scripts/fetch_wheel.py, which finds a CI wheel for a commit.
To do
  • After #570, let the setup dialog fetch the right wheels for a development build itself: solprop's, built from the checkout, and solprop-native's for the machine's platform from CI, as fetch_wheel.py finds them.
  • Say in the dialog when no matching native wheel exists (native changed and CI has not built it), and how to proceed.
  • Must not change: a release installs from PyPI with no wheels; nothing runs on the machine before the user has seen the script.
Done when

A window running a development build sets up a fresh Linux machine (glibc 2.28+, no system FFTW, no compiler) from the dialog alone, and a run started there finishes; recorded by hand on a workstation, since no CI lane has one.

🤖 Generated with Claude Code

Lenguaje dominante
Python
Estrellas
3
Forks
3
Merge medio
8 h 37 min
PR fusionados (30 d)
159

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 LupoLab/solprop

Todos los issues de LupoLab/solprop

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.