On Tue, Oct 20, 2009 at 10:02 AM, Darren Dale dsdal...@gmail.com wrote:
On Mon, Oct 19, 2009 at 9:50 PM, William Kyngesburye
wokl...@kyngchaos.com wrote:
Hmm, Macports. It's great for those who want a familiar packagae-manager
setup or just don't want to get their fingers dirty compiling
On Oct 20, 2009, at 11:05 AM, Darren Dale wrote:
I found some other issues related to using the system python
(/Library/Python/2.6/site-packages appearing late in PYTHONPATH, so
system-provided packages like numpy-1.2.1 are favored over manually
installed packages like numpy-1.3), so it looks
Excellent, thank you for the pointer.
May I request a feature? Could this be mentioned somewhere in the mac
README? Or would it be possible to add some logic to the mac
installation scripts to find where distutils installs packages by
default?
Darren
On Sun, Oct 18, 2009 at 11:04 PM, William
about installation best practices on OS X
Excellent, thank you for the pointer.
May I request a feature? Could this be mentioned somewhere in the mac
README? Or would it be possible to add some logic to the mac
installation scripts to find where distutils installs packages by
default?
Darren
On Mon, Oct 19, 2009 at 6:55 PM, Robert Bobbson rbobb...@yahoo.com wrote:
One thing you are going to find out is that Apple isn't the quickest on the
draw with updating things like Python. It's
only recently that they made a move to anything near the 2.6 line, so I
have long since given up
Hmm, Macports. It's great for those who want a familiar packagae-
manager setup or just don't want to get their fingers dirty compiling
source. It adds itself to your PATH and can cause trouble for non-
Macports builds (getting wrong versions of tools in the system, like
GNU vs. BSD
I just recently started working with OS X, and was wondering if
someone could point me to some discussion about best practices for
installing Qt and PyQt. For example, today I installed the Qt-4.6 beta
dmg, but was surprised that symlinks to tools like designer were not
created on the path.
By default (as you've noticed), SIP and PyQt install their binary
executables in the framework. This is fine for the python.org Python,
but installing in the system frameworks is not quite proper.
What I do for SIP and PyQt and the system python is specify a custom
bin (and site-packages
