Yeah, for a moment there I was thinking `opt_include` is Homebrew-specific and should be mentioned, but apparently users should just use `/usr/local/include/flint`. Will remove.
flint 2.5.2 (new formula)
=========================
- [x] Have you followed the [guidelines for contributing](https://github.com/Homebrew/homebrew-core/blob/master/CONTRIBUTING.md)?
- [x] Have you checked that there aren't other open [pull requests](https://github.com/Homebrew/homebrew-core/pulls) for the same formula update/change?
- [x] Have you built your formula locally with `brew install --build-from-source <formula>`, where `<formula>` is the name of the formula you're submitting?
- [x] Is your test running fine `brew test <formula>`, where `<formula>` is the name of the formula you're submitting?
- [x] Does your build pass `brew audit --strict <formula>` (after doing `brew install <formula>`)?
-----
FLINT is an important library for computational number theory. The formula was lost during the homebrew/science merger; I'm reviving it ([homebrew/science formula](https://github.com/Homebrew/homebrew-science/blob/d2b0623922184c0e8e47828a73fdea3b1dc9c70e/flint.rb)) — fixed it up and added a caveat.
Curiously, there was another attempt to revive flint just a few months ago: #43425 (it was eventually closed due to lack of activity). CC @alebcay since I'm not sure about the point of setting `DYLD_LIBRARY_PATH`.
In fact you can just copy the entire `lib/pythonx.y/site-packages` directory from the old installation to the new one, in theory it should work as long as it's the same Python version. Not completely sure if there would be subtle problems (other than outdated dynamic linkage, of course).
> gmail end to end from terminal
Any IMAP client, e.g. mutt.
> recompile in pyenv
```command
$ pyenv uninstall x.y.z
$ pyenv install x.y.z
```
If you want to preserve the exact dependencies,
```command
$ pyenv shell x.y.z
$ pip freeze > /tmp/x.y.z-requirements.txt
```
before uninstallation and
```command
$ pyenv shell x.y.z
$ pip install -r /tmp/x.y.z-requirements.txt
```
afterwards. Editable installs as well as local packages (whose frozen version) not published to PyPI can't be preserved this way; the replication should be otherwise faithful.
You can even install the same version under a different name without uninstalling the existing; I used to do this with pyenv in order to have a separate framework build (required for PyQt5). I don't remember if that's a manual process or a hidden feature though. Anyway, duplicating `plugins/python-build/share/python-build/x.y.z` to `plugins/python-build/share/python-build/<new_name>` is one manual way to do it.