Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Errors, missing code/links in Workers section

Aperta
#179 7 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
javascript, python
Ambito
documentation

Direzione di ricerca

Start with the Workers documentation page at https://docs.pyscript.net/2025.3.1/user-guide/workers/ and inspect the Worker interactions and Common use case sections. Verify the broken PyScript.com link and identify missing code or unclear dependencies between examples. Done means the examples are complete or clearly cross-referenced, the link works or is replaced, and the worker startup patterns are understandable.

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

Descrizione

In one place where workers are mentioned:

There are several pieces of code with code elements missing.
Also the two ways workers can be started are confusing because of this missing code.
Also the link to a working example is 404

The only problem with this is that people who are NOT Javascript experts may not be able to work out all the usecases that are legitimate from the code available. (I know I can't.)

  1. Missing link:
  • In this section of the page is a link:
The values passed between the main thread and the worker must be serializable. Try the example given above via [this project on PyScript.com](https://pyscript.com/@ntoll/tiny-silence/latest).
  • this link is 404
  1. In the Section Common use case the code refers to greeting which is defined in the previous section Worker interactions but not in this code. Its not clear which code should be carried forward from example to example and which is standalone. Ideally all the code for main and worker should (IMHO) be standalone and complete - or point to an example which works.

IMHO - It would be nice if the sections showed:

  • starting a worker from index.html
    • that does one job and has one function (from pyscript import workers)?
    • same but can be called multiple times with multiple functions (__export__ = ["fname1", "fname2"])?
    • some of which update the dom directly and some of which pass data back to main.
  • starting from python using Pyworker (from pyscript import PyWorker)
    • defining multiple functions that can be called,
    • setting a config so a package can be loaded,
    • some of which update the dom directly and some of which pass data back to main.
  • whatever is required for the donkey to:
    • send new code to the donkey for it to operate with,
    • see results like donkey's main use case - running code and seeing the results in a textarea,
    • see results where it can do the jobs defined for the previous two cases (sending data back).

IMHO this would make it easier for people to work out how to use workers in pyscript.
Any examples that could be generated for the docs would also be great and it would be nice if they followed the categories indicated above.
(I'd happily contribute a demo if I could work out how to make it ALL work.)

Lingua principale
Python
Stelle
17
Fork
20
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Guida per i contributori

Apri la guida per i contributori

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 pyscript/docs

Tutte le issue di pyscript/docs

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.