[python-updates] python3Packages.gradio-client: 0.5.0 -> 0.7.3

[pbsds]

Description of changes

context: #273538 (comment)

Can't test due to an eval error.

@mweinelt: do you prefer PRs or is it more normal/preferred to push directly to python-updates?

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[mweinelt]

google-cloud-cpp = disable-warnings-if-gcc13 (callPackage ../development/libraries/google-cloud-cpp { });

This is due to disable-warninigs-if-gcc13 settings env.NIX_CFLAGS_COMPILE, as well as the derivation itself. #268097 (comment)

do you prefer PRs or is it more normal/preferred to push directly to python-updates?

If you are confident about the change, you can push it there.

[pbsds]

@mweinelt gradio now builds with all the fixes added. Feel free to merge or rebase as you see fit

I ended up cherry-picking a bump from #273538, i assume it won't cause a merge conflict