Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Installing and setting up OS X Mavericks for Python development

blog.kristian.io

Post reply on HN
Print view View original

21–30 of 65 posts

Re: Installing and setting up OS X Mavericks for Python development

#21

Post by microtonal »

privong wrote: post #7

From the post: "Homebrew helps you compile different kinds of software on your mac, making it feel almost as easy as apt-get'ing a package on e.g. ubuntu. " (emphasis added) This is something I've noticed from using both OSX and Linux for the past few years — unless software is available as a drop-and-install package, it's universally _easier_ to install in Linux* than it is in OSX. Given the market for OSX and the a…

it's universally _easier_ to install in Linux than it is in OSX*

Unless the package is not in the repositories or you want to have an instance with some different flags. One of the really nice things of Homebrew is that besides being a package manager, it is a great /usr/local manager.

For instance, installing something that is not in Homebrew is as simple as setting the prefix to /usr/local/Cellar/whatever/version and then running brew link whatever and it puts symbolic links in /usr/local. Want to make it 'invisible'? Just do a brew unlink whatever

It's also much easier to maintain your own Homebrew repos (taps) than e.g. maintaining an Ubuntu PPA.

Re: Installing and setting up OS X Mavericks for Python development

#23

Post by recuter »

vivab0rg wrote: post #20
adamors wrote: post #4

Why are people still using powerline when there's a pure Vimscript implementation? https://github.com/bling/vim-airline

Or even better, lightline? https://github.com/itchyny/lightline.vim

Why is it even better?

Re: Installing and setting up OS X Mavericks for Python development

#24

Post by forgotAgain »

I've also decided to do a clean install of Mavericks on my mini. This time I'm going to try to limit the number of different ways I use to install software. Each standard way of installing seems to handle things differently. Over time the system becomes unknowable and a clean install is needed.

Re: Installing and setting up OS X Mavericks for Python development

#25

Post by driggs »

Always install an upstream Python in parallel to the OS X provided version if you're doing Python development. Apple custom compiles theirs, and it's always out of date. In fact, there are Mavericks specific bugs in both latest upstream and in the version included with Mavericks; look for a new Python release in the next few days.

See: http://code.activestate.com/lists/python-dev/125760/

And don't forget to `brew install python`!

Re: Installing and setting up OS X Mavericks for Python development

#26

Post by nwh »

taude wrote: post #14
HugoDias wrote: post #6

I dont code in Phyton, but i think that you should add xcode commands line tools in this tutorial. http://www.computersnyou.com/2025/2013/06/install-command-li...

I think Homebrew requires this? Or at least some of the basic packages I installed with it did....

Homebrew certainly requires the Xcode tools.

Re: Installing and setting up OS X Mavericks for Python development

#27

Post by maaku »

rb2k_ wrote: post #17

I wouldn't do the "Enabling apps from everywhere" step. If you have an unsigned app, just right click on it and select open. OSX will ask you once and be fine with it from then on.

If you develop your own applications, that can get very annoying very fast...

Re: Installing and setting up OS X Mavericks for Python development

#28

Post by workbench »

> I have chosen to re-format my OS X disk as a case sensitive file system

Utterly terrible advice.

Sorry but if someone is suggesting that then they have very shallow experience with OS X and you should not be following a blog post about anything technical from such a person.

Re: Installing and setting up OS X Mavericks for Python development

#29

Post by koffiezet »

workhere-io wrote: post #18
kayoone wrote: post #10

just use a vm (eg vagrant) or a remote server and be platform independent!

Why use extra RAM on Vagrant when your Mac OS X is a full-featured Unix OS? Don't get me wrong, I know that the more complicated your setup gets, the more it would make sense to use Vagrant - but if you're just developing a CRUD Flask / Django app with PostgreSQL, you might as well just install Postgres.app and develop locally.

I prefer vagrant for most development projects for the simple reason that I can automate the VM + development environment generation AND commit it to a revision control system (git/svn).

Once set, I don't have to worry about re-installing my development environment - and can just let anyone check out my sources, who then has to do a simple "vagrant up", wait a few minutes, and he's up & running. No worrying about which things he specifically has to install and configure, my vagrant config takes care of that.

Also - the memory requirements are very limited imho, I run most of my vagrant Ubuntu 12.04 server VM's with with 128 or 256mb...

Re: Installing and setting up OS X Mavericks for Python development

#30

Post by archgrove »

maaku wrote: post #27
rb2k_ wrote: post #17

I wouldn't do the "Enabling apps from everywhere" step. If you have an unsigned app, just right click on it and select open. OSX will ask you once and be fine with it from then on.

If you develop your own applications, that can get very annoying very fast...

It never asks for locally created applications. It's purely for things downloaded over the Internet. In essence, it's a more advanced version of the original "You just downloaded this, are you sure you want to run it" warnings from the file quarantine system introduced with....Leopard, I think?
Post reply on HN