Python: conda environment.yml is a dependency declaration; a docs-site static-analysis FAIL should not outweigh the product's PASS

Aperta
  • Qualcosa non va?
#281 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
55/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
anaconda, python
Ambito
documentation, tooling

Direzione di ricerca

The bug is in the dependency-management check and the documentation static-analysis check of project_validator, which the payload does not name by file. Start by grepping the Python sources for requirements.txt to find the dependency message, then reproduce with a repo that contains only environment.yml. Done when the message names the conda file and the docs sub-result WARNs instead of FAILing when the product check passes.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

handson-ml3 and PythonDataScienceHandbook declare their environment in environment.yml (conda) but the message pretends only requirements.txt exists ("declared in requirements.txt but not locked"). Every Sphinx/MkDocs Python project FAILs static-analysis "Documentation site: no static analyzer runs; Python: ruff check runs" — with the product passing, the docs sub-result should at most WARN, and the hint should name an rst/markdown linter.

Evidence from the corpus audit

ageron/handson-ml3, jakevdp/PythonDataScienceHandbook / dependency-management
  • kind: UNSUPPORTED
  • actual: handson-ml3 WARN: dependencies are declared in requirements.txt (Python packages) but not locked; PDSH WARN: ... declared in requirements.txt (Python packages) but not locked
  • expected: the conda environment should be named as a declaration (and judged: environment.yml pins are not a lock file either, but the message should not pretend only requirements.txt exists)
  • evidence: handson-ml3 environment.yml:1-4: name: homl3 / channels: / - conda-forge / dependencies:; environment.yml:26: - python=3.10 # your beloved programming language! :); PDSH environment.yml (117 bytes); grep -rn -i "conda\|environment.yml" project_validator --include=*.py → nothing
  • repro: a repo with environment.yml only
  • confidence: high (conda is the dominant dependency tool of the Jupyter/data-science ecosystem)

Found by the regression-corpus audit (235 real repositories, one or more per ecosystem profile; corpus and expected results in corpus/). Evidence is quoted from the audited checkouts at the commits pinned in corpus/projects.toml; <checkouts>/<owner>__<repo> is such a checkout.

🤖 Generated with Claude Code

https://claude.ai/code/session_01ByTXNqDWdM7HzezrFtEvQt

Lingua principale
Python
Stelle
4
Fork
1
Merge medio
10h 41m
PR unite (30g)
79

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cpp-best-practices/project_validator

Tutte le issue di cpp-best-practices/project_validator

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.