Mac vs. PC for Django work.
keukaman
design work on. Could I get some comments related to which is better
for Django work - P.C. or Mac, as well as some pros & cons of each?
Thanks.
Adrian Holovaty
I'll be the first to say that the Django documentation is inherently
biased toward Unix, so you'll probably find it easier to use Linux or
Mac than Windows. (None of us core dudes use Windows, to my
knowledge.)
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com
Roodie
any real difference between the two ( regarding django development of
course ). Only one thing - postgres setup can be a little tricky on
the macbook, while mySQL has a nice native installer which "just
works". You have svn, nice text editors, even a full ide ( Eclipsy +
pyDev plugin ) for both.
---
Roodie
Eric Walstad
One of the developers on my team works on a Mac, while the other two of
us are on Linux. Our apps are deployed on Linux PC machines. The Mac
guy had a harder time setting up his development environment, having to
compile more packages from source, than we Linux guys did. However,
once set up, we had few issues with cross-platform compatibility. One
was that there were some differences in the capabilities of the Mac
Python, if I recall correctly, that forced us to drop the use of
Django's 'include' template tag. That was waaaaayyy back in the days of
Django 0.91, though, so that may no longer be an issue on Django trunk.
Eric.
Jay Parlar
> One of the developers on my team works on a Mac, while the other two of
> us are on Linux. Our apps are deployed on Linux PC machines. The Mac
> guy had a harder time setting up his development environment, having to
> compile more packages from source, than we Linux guys did. However,
> once set up, we had few issues with cross-platform compatibility. One
> was that there were some differences in the capabilities of the Mac
> Python, if I recall correctly, that forced us to drop the use of
> Django's 'include' template tag. That was waaaaayyy back in the days of
> Django 0.91, though, so that may no longer be an issue on Django trunk.
>
You can get a newer version of Python (2.4) for the Mac, binary installers too.
I use OS X for all my Django development, and it's been flawless.
There are binary installers for PostgreSQL and MySQL. I haven't had to
build anything from source for my setup (except PIL, but that builds
perfectly with 'python setup.py install')
At my old job, I did Django development with Gentoo, that worked nicely too.
Jay P.
Joseph Kocherhans
I use OS X as well for all my development and deploy on both windows
(work) and linux (personal). Deploying on windows is kind of a pain in
the ass. Django development is heavily command line biased. Maybe
windows has some nice command line tools, but the defaults suck and
are a total pain to use.
If you go the mac route, I recommend using darwinports(now macports)
to install either python2.3 or python2.4. I've never used the default
os install of python, and have never had any issues with the
darwinports version. It also makes it easy to install database
wrappers, ldap modules, etc. Darwinports isn't as nice as say apt-get
on debian/ubuntu, or FreeBSD's ports collection, but it does the
job... mostly. Being able to use TextMate, LaunchBar, and a gazillion
other mac specific apps is worth the pain for me. My close second
choice would be Ubuntu.
Joseph
Wilson MacGyver
the latest Python from http://www.python.org/download
It's straight forward and let you have up to date python
so you can avoid problems like that.
Michael Samoylov
Tyson Tate
Intel Mac. You can run the delicious UNIX-y goodness of MacOS X for
real work and then drop in to Windows when you need to do whatever it
is that people would want to do in Windows (get headaches?).
Django works wonderfully on MacOS X. It's a perfect development
environment, really. TextMate, the Mac-only text editor, is one of
the best programming editors out there (aside from Vim and Emacs, I
guess). There's also a few Django bundles out there for TextMate
which are amazingly useful in hammering out code quickly.
-Tyson
Marcelo Maia Garcia
Kenneth Gonsalves
On 13-Sep-06, at 8:51 PM, Eric Walstad wrote:
> was that there were some differences in the capabilities of the Mac
> Python
do you have to use Mac Python? Cant you install the standard python
like on other BSDs?
--
regards
kg
http://lawgon.livejournal.com
http://nrcfosshelpline.in/web/
Kenneth Gonsalves
On 13-Sep-06, at 10:43 PM, Tyson Tate wrote:
> Heck, why not get the best of both worlds: Get a MacBook or other
> Intel Mac. You can run the delicious UNIX-y goodness of MacOS X for
> real work and then drop in to Windows when you need to do whatever it
> is that people would want to do in Windows (get headaches?).
i think the question was Mac vs PC, not Mac vs windoze. PC !=
windoze. I do my django work on ubuntu on the desktop, but use Mac on
my laptop - and 90% of the work is in the darwin shell anyway
brian corrigan
no c compiler installed. You can download xcode tools (I think) from
the apple developer site which will give you gcc. The problem is that
xcode is about a 1GB (latest realease). Takes a while to download.
Other than that though, there is a perfect tutorial on
http://toolmantim.com/article/2006/5/31/installing_django_on_osx
Helped alot!
Cheers
Brian
Johannes Beigel
> The only problem I came across with the Mac (iBook) was that there is
> no c compiler installed. You can download xcode tools (I think) from
> the apple developer site which will give you gcc. The problem is that
>
XCode should be contained on your Mac OS X installation DVD, although
this is could be a slightly outdated version, of course. But if you just
need a gcc this should do fine.
-jojo
Roodie
Fortunately the xcode tools is on the install DVD for the newer OSX
versions.
>
> The only problem I came across with the Mac (iBook) was that there is
> no c compiler installed. You can download xcode tools (I think) from
> the apple developer site which will give you gcc. The problem is that
> xcode is about a 1GB (latest realease). Takes a while to download.
---
Roodie
Kenneth Gonsalves
On 14-Sep-06, at 1:48 PM, brian corrigan wrote:
> The only problem I came across with the Mac (iBook) was that there is
> no c compiler installed. You can download xcode tools
it is there on the install CD, but not in the default install
spacedman
things to work on there can be annying at times - its usually file
paths to python, and things like #!/bin/env and all that, and whether
you run from cygwin or DOS shell. Aaargh, the horror. I wrote my poker
blog at home on Windows. My IDE was emacs.
At work where we do real Django stuff our current developer is using
Eclipse on Windows, but his replacement will be Linuxing.
I'd be tempted to say to do your development on the platform that most
closely matches your deployment platform. We're using Apache and
mod_python on our own Linux web server here, so that's the best thing
for development for us.
Barry
Cheng Zhang
On Sep 13, 2006, at 11:21 PM, Eric Walstad wrote:
> One of the developers on my team works on a Mac, while the other
> two of
> us are on Linux. Our apps are deployed on Linux PC machines. The Mac
> guy had a harder time setting up his development environment,
> having to
> compile more packages from source, than we Linux guys did. However,
> once set up, we had few issues with cross-platform compatibility. One
> was that there were some differences in the capabilities of the Mac
> Python, if I recall correctly, that forced us to drop the use of
> Django's 'include' template tag. That was waaaaayyy back in the
> days of
> Django 0.91, though, so that may no longer be an issue on Django
> trunk.
I am surprised to know that. In our situation, I write code on my
Mac, and we deploy on Gentoo Linux. No any single compatibility issue
or setup issue at all. Setting up our dev environment on Windows is a
bit tricker than on Mac or Gentoo Linux, but it's still pretty smooth.
If your Mac guy use the stock Python installation (2.3) comes with
Mac OS X, then he should upgrade it from http://pythonmac.org/
packages/py24-fat/index.html immediately.
With the combined help from that link, easy_install and darwinports
(now rename as macports)/fink, the Mac ride will be flawless.
－Cheng Zhang
http://www.ifaxian.com
1st Django powered site in Chinese ;-)
http://www.aiyo.cn
Our 2nd Django powered site in Chinese
Cheng Zhang
On Sep 14, 2006, at 8:01 PM, spacedman wrote:
> I'd be tempted to say to do your development on the platform that most
> closely matches your deployment platform. We're using Apache and
> mod_python on our own Linux web server here, so that's the best thing
> for development for us.
My opinion is that doesn't matter. We are going with the most
convenience/comfortable route.
IMHO the built-in web server is perfect for development usage,
autoloading, easy message output on console, etc.
Apache + mod_python is only one way out of many Django deployment
methods. In our experience, lighttpd + scgi is much better than that.
Again, pick what is the most comfortable one is always our guideline.
Cheng Zhang
Python or any web design work at all.
TextMate is a great editor, at least as much powerful as Vim or
Emacs, with a overwhelmingly damn pretty looking and enjoyable GUI.
The only con of TextMate is it ain't free and open source. :-)
Rails guys are using Mac everywhere, since they also know the joy of
using Mac and TextMate.
The only con of Mac might be the price if you are also looking at a
Dell laptop, but if your eyes are on a ThinkPad, you might be
surprised by the price of equally equipped Mac laptop.
My 867MHz/768MB PowerBook G4 still serve my work and life pretty
well, after all these 3 years. :-)
And it's getting faster and faster with each update from Apple. It
might be a surprise if you come from Windoze world, but that's pretty
normal with Linux world as well. With the improvement on
infrastructure open-source software like GCC, the same set of app
will run faster on the same set of hardware.
－Cheng Zhang
http://www.ifaxian.com
1st Django powered site in Chinese ;-)
http://www.aiyo.cn
Our 2nd Django powered site in Chinese
Eric Walstad
Hey Cheng,
Thanks for your feedback. I'll send it along to our Mac developer.
Best,
Eric.