On Thu, Jul 28, 2011 at 10:08 AM, Kolbe <maximilian.jack...@gmail.com> wrote: > lol. > > what's your recommended build for OSX though if I were to use django? >
I don't know what you mean by 'build,' but my standard setup was compiling my own Python (requires installing XCode) and using PostgreSQL (using the EnterpriseDB installer). Then a virtualenv for each project with --no-site-packages used. That's pretty much it. I use Postgres instead of sqlite because sqlite doesn't enforce all the constraints so, for example, unique_together isn't enforced. When you go to production you'll get errors you missed in development. If you use sqlite in production as well then you'll miss the errors completely and end up with different data than you expected. The only "trick" to it was compiling psycopg2 (the Postgres driver for Python). It only works with 32-bit Python, so you'll have to compile Python as 32-bit instead of the default 64 that comes with OS X. Here's a blog post I wrote about how to take care of that. http://shawnmilo.blogspot.com/2009/11/psycopg2-on-snow-leopard.html -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
