it's probably a matter of queue when it comes to custom types ... polyscript handles non-custom types slightly differently so that this might still be a polyscript issue after all, as PyScript just uses its registry to define the type.

Multiple scripts of same type are still a not super common use case though, so let's see if we want to prioritize this before the coming RC.

/cc @fpliger @ntoll

Investigating a little more, I think this is PyScript specific. It seems the inline tags are always executed before any src tags, but that's not the case in Polyscript.

In PyScript, I can mix up the following tags in any order:

<script type="py" src="one.py"></script>         <!-- print('src one') -->
<script type="py">print('Inline one')</script>
<script type="py" src="two.py"></script>         <!-- print('src two') -->
<script type="py">print('Inline two')</script>
<script type="py" src="three.py"></script>       <!-- print('src three') -->
<script type="py">print('Inline three')</script>

And I always get:

Inline one
Inline two
Inline three
src one
src two
src three

But in PolyScript, they are executed in overall page order, regardless of whether they're inline or use src:

<script type="pyodide" src="one.py"></script>        <!-- print('src one') -->
<script type="pyodide">print('inline one')</script>
<script type="pyodide" src="two.py"></script>        <!-- print('src two') -->
<script type="pyodide">print('inline two')</script>
<script type="pyodide" src="three.py"></script>      <!-- print('src three') -->
<script type="pyodide">print('inline three')</script>

prints:

src one
inline one
src two
inline two
src two
inline three

I can solve this in PyScript but it's a polyscript custom type issue ... polyscript queue per interpreter all executing things:
https://github.com/pyscript/polyscript/blob/main/esm/script-handler.js#L160-L162

there's no such mechanism for custom types (IIRC) and I think if non custom type works like that, so should custom types too.

I'll try to fix this today, thanks for the investigation though!

@JeffersGlass this has been fixed and tested in polyscript so it will get in next time we update PyScript too ... which arguably could be today as well but ... you know, don't release on Friday and stuff 😄

plot twist ... it might be today: #1805

it's in and published to npm ... you should be able to grab either latest from npm or from our CDN and verify your expectations now are met.