308 reputation
16
bio website sethmmorton.github.io
location Portland, OR
age 30
visits member for 2 years, 4 months
seen Sep 16 at 5:11

Languages:

  • Python
  • Perl
  • Tcl
  • C++
  • Fortran
  • Bash/Csh (only when I have to)

Interests:

  • Repetitive task automation
  • Scientific computing
  • Text-base user interfaces

Mar
15
comment Uninstall python package and restore to previous setup?
pip uninstall won't work for EPD, which is the Enthought Python Distribution, a complete python distribution that includes matplotlib, numpy, scipy, and a few others. My guess is when he calls python, it calls the EPD python binary, which looks in its own library. Therefore, the old packages he had aren't found. If he installs the packages using the EPD python, they should be found when python is launched because they will be in the EPD python library.
Mar
15
comment Uninstall python package and restore to previous setup?
Python keeps a separate set of packages for each python distribution you install. Have you tried reinstalling the packages using the EPD python? OR, I'm guessing your original python installation still exists... check your filesystem. If you launch python using the original installation, do the packages work again?
May
17
comment 'brew doctor' command not recognizing path changes
To say it's incorrect would be incorrect. I'd say it depends on your philosophy of maintaining your system. Personally, I like to keep all modifications (such as changing my PATH) in single file (i.e. ~/.profile) so that if I need, I can "instantly" return to the system default. There also may be cases when a program assumes that the system path in /etc/paths is default and may break if it is not (this is not likely, but it could happen). If you don't have an issue with messing with your system files, then I can't tell you that it is incorrect. It's just that I wouldn't do it that way.
May
16
comment Changing the highlighted text background color in VIM on Mac OS X
As noted in the comment for the question, the key was to add the line set t_Co=8 in my .vimrc on my Mac.
May
16
comment Changing the highlighted text background color in VIM on Mac OS X
@garyjohn Thank you so much! It turns out that on Linux t_Co=8, but on Mac t_Co=256. I changed t_Co=8 on Mac, and everything is fixed! I don't have enough privilege to upvote your comment, otherwise I would. If you post your comment as an answer then I'll definitely upvote it.
May
16
comment RPM Build Failing in %build
I agree with Ignacio that you should remove the autogen.sh line. What has me confused is that you said the build failed even when this line was removed, but with the same error. If there was no line referencing autogen.sh then rpm shouldn't have been looking for it, so it shouldn't have complained that it didn't exist. Are you sure that you had removed the line telling it to execute autogen.sh before?
May
16
comment RPM Build Failing in %build
If the .spec file isn't too long, could you add this to the original post? Sometimes errors that appear on line B are due to something on line A.
May
16
comment RPM Build Failing in %build
Does it still give the error autogen.sh : command not found or is there a new error?