> On Dec 13, 2016, at 8:37 AM, Christopher Barker <python...@gmail.com> wrote:
>
> Personally, I have avoided all this mess the last couple years by using conda
> (miniconda install). It does a nice job of keeping entirely separate from the
> system ( or any other) python, and it can manage non-python libs as well, so
> you don't need Brew. And it has environments that are like virtualenv, but
> with the C libs isolated as well.
>
> Between the default channel, conda-forge, and pip for pure python packages,
> there is a lot available.
>
> If we were to add s PyObjC build to conda-forge, the full stack should "just
> work".
>
> And conda forge has s CI system set up to auto build for various python
> versions....
>
> http://conda-forge.github.io/#add_recipe
> <http://conda-forge.github.io/#add_recipe>
Why would this be necessary? Can't conda just install the wheels from PyPI?
-glyph
_______________________________________________
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
https://mail.python.org/mailman/listinfo/pythonmac-sig
unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG
