You may want to merge master into this... you have like 117 broken builds on python-unstable, but I fixed at least 30 or so of them on master.

That won't work becuase aws-sam-translator here depends on jsonschema >= 3. The old version is in master https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/python-modules/jsonschema/default.nix

if someone has commit access, they go rebase it on top of master, probably would be a fair amount of conflicts, but then the changes in python-unstable would be applied on top of master.

@costrouc I think @jonringer mean't merge master into python-unstable to pickup python fixes that landed in master. But I don't think we'll get a clear picture of the failures if we do that.

Please don't use python-unstable. It has not been touched in quite a while.
I'll see if I can cherry-pick your existing changes or rebase them onto master.

Actually, better, open a new PR with the changes that went into python-unstable.

So I should move these changes and the previous PR into master?

Yes, master or staging depending on the amount of rebuilds.

I will close this issue. Using #65023 instead