> bizarrely it seems to pass on CI too …
pipenv test failed locally and succeeded on the next run. WTF. Anyway I'm bumping it.
> not from virtualenv itself.
Yeah, virtualenv itself should be happy as long as there's still a `python3.6` in the same place as when you first created the virtualenv.
> removed the old python3 from your Cellar
Good point. That should affect all packages using `Language::Python::Virtualenv`.
@ilovezfs sip needing a revision bump shouldn't be too surprising; I would do it for safety even. But why pre-commit and pipenv? They are just pure python packages and shouldn't be affected by a patch release. Tests work fine too. How should they fail? That should probably be written into tests.
python3 3.6.4
=============
Created with `brew bump-formula-pr`.
Add CPython 3.6.4 and remove 3.6.4rc1
=====================================
https://www.python.org/downloads/release/python-364/