I've been using Aquamacs Emacs and Bash Shell for Python development on my Mac OS X.
Though now I'm about to start develop a hybrid project with my PACS and
ROI project (Python + BerkeleyDB ...) and XNAT (Java + PostgreSQL + Apache Tomact + XML ...), and it's good to have an IDE though when a project is composed of several different projects, programs and languages.
I had given up to use Eclipse IDE for my Python development because of several errors and issues with Numpy, unresolved imports and etc...
Now I've investigated further on this problem and I've almost resolved those problems:
- Unresolved import errors (and warnings)
Manually add the source directories, .egg files or whatever which is containing the libraries with the 'unresolved import' errors and warnings in the PyDev PYTHONPATH.
Then try again.
When it's not resolved yet, then try modifying, adding more source folders, etc. to the project's PYTHONPATH.
Play around with those until it works.
You might need to examine, which libraries is loaded when you launch Python on Bash Shell, and which libraries you included in your PyDev preferences, when you have e.g. several other versions of a same library (e.g. Numpy) installed on your machine.
- DYLD_LIBRARY_PATH problem
I use several bash variables to let my system know where I have libraries, binaries, header files, etc.
Though, when a program is launched as an Apple Mac .app, those apps don't see my bash path variables and configurations.
The solution is to edit the ~/.MacOSX/environment.plist file,
One might get the same result (for my case, just letting my Eclipse IDE to know my DYLD_LIBRARY_PATH) editing the app's Info.plist file as is appearing in Apple's Mac OS X Reference Library
here, which might be a safer way to play around only with the app which matters, rather then to play around system-wide.
Though I haven't tried that, as editing the ~/.MacOSX/environment.plist just worked, and I didn't want to log out and log in and so on ...
