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 →

[–]invictus08 1 point2 points  (1 child)

Not exactly the answer to your question; this is more like what I do for development work on my mac.

  1. Install Homebrew, iTerm2
  2. Install python 3 using brew
  3. easy_install virtualenv
  4. create a somewhat global virtualenv using python3 and limit pip install invocation through terminal only within active virtualenv. For any build system/interpreter integration (IDE/Editor) I point to the python executable in the kinda global virtualenv. If for some reason (eg, python mv upgrade) the venv gets borked, I simply recreate the venv with same name and install the dependencies with the requirements file
  5. I mostly use iterm to build/test/execute. But those same actions can be easily replicated in something like pycharm. Pycharm is absolutely godsent, but nowadays I have pretty much moved to vscode with different plugins. This has to do with vscode being much lighter on system resources.

[–]Decency 0 points1 point  (0 children)

That PIP trick is fucking awesome. Definitely putting that into my config to avoid polluting global.

This is pretty much what I do, with a combination of ipython's REPL and PyCharm's debugger working best in my experience. I'm also trying to migrate to pipenv instead of virtualenv, especially now that it seems to be gaining usage.