python-abseil: remove

[cho-m]

See #157500

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

[clason]

Note that arxiv_latex_cleaner depends on this. (Nvm, I see that the dependency resolution isn't updated unless you reinstall the formula after the change.)

[cho-m]

Note that arxiv_latex_cleaner depends on this. (Nvm, I see that the dependency resolution isn't updated unless you reinstall the formula after the change.)

We could revision bump to force #163115. I am not sure how well brew handles this situation.

[clason]

It doesn't, is how ;) Hence my comment.

(Something to keep in mind during the Great Python Yeeting.)

[timsutton]

My interpretation of this then, is if we:

• have a python-* formula which was depended on by a relatively small number of formulas (say, 1-4), and
• those formulas are unlikely to be updated in the time between vendoring and removal of said python-* formulae

then, we should proactively revision-bump the formulas that depended on them, or at least those which aren't updated very frequently. It may make sense to just to just do a revision bump at the same time as vendoring if we'd expect to need to circle back to them anyway later just to revision-bump.