FWIWI I think if we have a pyscript module in pip that should reflect pyscript and not pyscript-cli ... but on the other hand, I find pyscript-stubs an explicit solution, although I still find current pyscript module confusing for new comers.

I have finally gotten around to start working on a package for stubs.
https://github.com/gregersn/pyscript-stubs

There is also Micropython-webassembly-stubs on pypi , that has both pyscript stubs , and MicroPython.

Available for MicroPython 1.24.1 and preview.
https://github.com/Josverl/micropython-stubs/tree/main/publish%2Fmicropython-v1_25_0_preview-webassembly-stubs

Perhaps it would be good to see how these can be joined up ?

I maintain both the stubs, as well as the stubbier tool to merge type annotations between different stubs,
So would be happy to collaborate

Simplest would be to add to the pyscript 'reference stub' that I have generated through script , and manually updated from the various doc pages.

That could be used both as a stand-alone, but probably more useful with a complete MicroPython package as I now publish it.
But there may be use-cases I have not considered, so please let me know if I miss the point

Also happy to move that reference part into the pyscript org,
That is the reason I abstract the reference from the publication as I'm planning a similar move for the MicroPython reference stubs to the MicroPython repo.

@Josverl I would be happy to help work on whatever, instead. I just really want to be able to have some typing while writing client side pyscript for webbrowsers. I do not feel strongly about my started project. I will look at the links you provided.

My issue with basing the typing on the source, is that a lot of the class names are not matching the class names used in the MDN documentation, which makes it a lot easier to actually look up and figure out how stuff works when writing the code.

I assume you are referring to accessing the HTML DOM elements, is that correct ?
as I understand these originate from polyscript

    window = polyscript.xworker.window
    document = window.document
    sync = polyscript.xworker.sync

This part I have not yet looked into - It should be possible to generate a basic stub for the polyscript module as well ( assuming there is some refection working)
But pretty sure it would require manual updates.

On matching the class names between MDN / Python.
Should be simple to generate docpages that allow searching on either by using the templating and combining actual documentation and indexes , with the info from the docstrings.

Can you give an example snippet of code that you would like a stub for ?

How about a new "stubs" repos under the PyScript org on GitHub?

That would work, I think it would also be good to add some goals & guidelines on what to include, and how to handle any differences between CPython and MicroPython, license etc etc. but can build that as we go along

Possibly a simpler way would have been to move the existing repo, as now there is an unclear fork.

There is an option in repo >Settings to detach from the fork network ( Greger;s original repo).

its a bit of a hassle now , but would make ownership clearer.

I just merged it, before I read here. Looks good

a few points :

Im confused by the location of the license.

• if the root repo is Gregers, who is the licenser ?

• my current work is MIT licensed,
  It would be silly for me to submit a major body of work, that uses a license that requires me to use your license rather than MIT
  in short :

Derivative works of the software will need to comply with the more detailed requirements of the Apache License 2.0, such as preserving NOTICE files and providing attribution for changes.

I need to think this over, I love to collaborate, and MIT and Apache 2.0 are not that different. The intents are the same.

But it would have a potential ripple effect on my own software the several thousands of downloads of the stubs each month , and the various typing tools that already use the micropython-stubs under a MIT license. Also it feels like signing over my work to someone else , without a proper dialog on how to do this.

I'd love to find a way to work together, and for me to keep using the MIT license for the parts that I create, and apply the other licenses just to the parts created and shared by others.

The _typeshed module defines the Incomplete type specific for partial typing.

By using Incomplete instead of Any, it clarifies that the argument types still need work. It communicates that improvements or more specific types should be made in the future, making it easier to spot areas for enhancement in stubs

python/typeshed#5613