Open davclark opened 9 years ago
That seems to be the recommend method, but it'd be cleaner if we could automate it.
Manually adding the miniconda interpreter causes PyCharm to update a database of python skeletons which takes a while.
I'd lean towards having the update happen at build time... even if it adds 15 minutes. Otherwise, this is the kind of thing that slows down a 1 hour workshop!
I don't know exactly how to do this without the GUI, but I can probably figure it out. The best interpreter link would be ~oski/miniconda/envs/py34/bin/python3.4