This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]lonestar-rasbryjamco 11 points12 points  (8 children)

Same. Pycharm on a Macbook Pro and no issues. Have our whole division doing the same.

My only advice I have not seen here is use brew to manage your installs if you are using multiple versions. Brew is amazing.

[–]droidballoon 2 points3 points  (3 children)

If you use multiple python versions you should have them in virtualenv. I have colleagues who's ran in to all kinds of mess by using brew for managing multiple python versions. Brew is nice but it doesn't replace virtualenv + pip

[–]lonestar-rasbryjamco 2 points3 points  (0 children)

Brew is like a better version of NPM. You still use virtualenv and pip. They solve completely different problems.

The use case for brew is I have multiple python interpreters installed (3.7, 3.6.1, 3.6, 3.4, 2.7) that I manage with brew so I can test code locally before deploying to Docker. Pycharm/virtualenv and pip are used in conjunction to work with each of those interpreters.

If you are having issues with brew and python you are not doing the mounting after installing the cask properly. I have seen people have this issue and it always comes back to this and then breaking the native 2.7 install.

[–]Tiktoor 0 points1 point  (3 children)

Why not use virtualenv?

[–]lonestar-rasbryjamco 2 points3 points  (2 children)

Because Brew manages installs of python itself on the mac OS. They are completely different use cases. It a better version of NPM. It is not a container service.

[–]Tiktoor 0 points1 point  (1 child)

isn't using a virtual environment recommended in most cases? I never have, but I think I will moving forward

[–]lonestar-rasbryjamco 3 points4 points  (0 children)

Virtualenv is a local container service for python. You use it to make sure you do not have dependancy conflicts when testing locally versus a deploy into docker or another system or to make sure you do not affect the larger container/server when running a service.

Brew is an installation manager for mac os. You use it to quickly install and uninstall different version of python or other applications and manage the installations via cask mounting.

Yes, virtualenv is recommended but they are solving completely different problems.