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

31–40 of 65 posts

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

#31

Post by levosmetalo »

microtonal wrote: post #16
oellegaard wrote: post #3

Earlier quoted context omitted.

The major reason behind the switch is that I recently had to rename a file, that someone accidentally comitted with an uppercase letter. We had to do it on another machine. It's a valid concern though.

At my previous employer, where most developers use Linux, there was a README and a readme with different content in the same directory in a git repository. Loads of fun on case-insensitive OS X, since git always believed some data was removed ;).

The way you phrased it one could assume that it's somehow git's fault ;)

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

#32

Post by taude »

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 had tons of issues trying to get Postgres to work on my Mac. Lots of other conflicts, too. I think the Mountain Lion OS upgrade fried my host dev environment, too. Eventually, I went the VM route....afterall, you're going to eventually deploy to a Linux box anyway, and there's enough differences that you'll feel the pain when you go to deploy.

And now, I don't have a polluted host OS with tons of versions of software. I can easily try out new technologies, kill the VM, and start over.

Keeping VMs for different projects in their on silo'd around is really convenient.

Switching OSes or upgrading, rebuilding a computer, etc. I don't loose these configurations.

The list goes on and one.

RAM is cheap. I think I paid $100 to upgrade my Mac Book Pro to 16 GB.

I can also switch back to a host Windows machine and take my VMs with me (should the need arise)

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

#33

Post by huxley »

mhurron wrote: post #12
huxley wrote: post #9

Earlier quoted context omitted.

When I was running the developer version of Mavericks, the site_packages weren't preserved, which meant pip & setuptools were broken, so I had to reinstall them like so: http://www.pip-installer.org/en/latest/installing.html then upgrading pip and virtualenvwrapper: $ sudo easy_install pip $ sudo pip install --upgrade virtualenvwrapper If that doesn't do the trick, you might need to install the Xcode command line too…

Wouldn't it be better to not install eggs into the system path and instead into site-packages on a per-user basis? Or, quite frankly, not use the system python at all?

Sure ideally, I've played with pyenv a bit but for my main machine I've kept my systemwide installs down to just enough to run virtualenv and virtualenvwrapper (everything else lives inside virtualenvs).

For several situations though (like when Xcode command line tools stops working after a major OS update) it won't matter. You need a c compiler for several packages and having your stuff isolated per-user or using a non-system Python won't help that one bit.

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

#34

Post by levosmetalo »

ams6110 wrote: post #8
oellegaard wrote: post #3

Earlier quoted context omitted.

The major reason behind the switch is that I recently had to rename a file, that someone accidentally comitted with an uppercase letter. We had to do it on another machine. It's a valid concern though.

mv File _file; mv _file file

I wish it was always that simple.

I don't know about Mac, but once I had a problem that some of the game installers created folder " Games", although "Games" was already there.

Fun time trying to delete or rename to something same this " Games" folder using Windows Explorer, Total commander and command prompt. Each one of them got confused and tried to delete "Games" instead of " Games". At the end, I just fired up lcc, and made a simple C program calling `ulink(" Games");`. And it worked ;)

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

#35

Post by workhere-io »

taude wrote: post #32
workhere-io wrote: post #18

Earlier quoted context omitted.

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 had tons of issues trying to get Postgres to work on my Mac. Lots of other conflicts, too. I think the Mountain Lion OS upgrade fried my host dev environment, too. Eventually, I went the VM route....afterall, you're going to eventually deploy to a Linux box anyway, and there's enough differences that you'll feel the pain when you go to deploy. And now, I don't have a polluted host OS with tons of versions of softwa…

I had tons of issues trying to get Postgres to work on my Mac

Did you try http://postgresapp.com ?

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

#36

Post by quarterto »

recuter wrote: post #23
vivab0rg wrote: post #20

Earlier quoted context omitted.

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

Why is it even better?

  Why yet another clone of powerline?
    vim-airline is a nice plugin, but it uses too much functions of other plugins, which should be done by users in .vimrc.

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

#38

Post by Xylakant »

oellegaard wrote: post #3
ra wrote: post #2

Be wary of using case sensitive FS. Many apps simply don't work on case sensitive. Maybe they've fixed it, but not long ago the whole Adobe suite just wouldn't work on case sensitive EXT FS. You should use a convention for your filenames anyway. Eg in Python you always use lower case.

The major reason behind the switch is that I recently had to rename a file, that someone accidentally comitted with an uppercase letter. We had to do it on another machine. It's a valid concern though.

Well, you can just use a mounted disk image formatted with a case sensitive HFS as development env. You'll need to mount that every time you restart but that's a minor hassle compared to problems you might run into when using a case sensitive FS for your primary partition.

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

#39

Post by kayoone »

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.

yeah that works okay if you only need that, but then comes another project or new requirements and suddenly you run mongodb, redis and some background worker stuff as well and this slowly pollutes your system.

I did it that way for a long time too, but running vms became so convenient with vagrant and all the box configurations you can download that its kind of a no-brainer as long as you have 8Gigs of RAM or more.

Post reply on HN