Update to pyodide 0.27.2

[bollwyvl]

changes

• update to pyodide 0.27.2

  • not seeing anything super-relevant other than some vendored package bumps...
    but this includes things like pydantic and httpx that are... less disciplined about API stability, of late

[github-actions]

👈 Try it on ReadTheDocs

[bollwyvl]

Seemed fine on RTD. Guess if it looks alright, we can punch it through as another alpha, take a look on some downstreams, and then do a backport for 0.5.x.

[jtpio]

Thanks!

[jtpio]

@meeseeksdev please backport to 0.5.x

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout 0.5.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 37d011a1f9f068bb938e3eff80e8a497ac27618a

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #163: Update to pyodide 0.27.2'

4. Push to a named branch:

git push YOURFORK 0.5.x:auto-backport-of-pr-163-on-0.5.x

5. Create a PR against branch 0.5.x, I would have named this PR:

"Backport PR #163 on branch 0.5.x (Update to pyodide 0.27.2)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.