Issue #31 'make install' on OSX lion installs in wrong dir #32

Open
wants to merge 2 commits into
from

Projects

None yet

5 participants

@Tylerc230

I'm installing ino by cloning the github repo and running 'make
install'. It appears to install the lib files at
'/usr/local/lib/python2.7/site-packages/ino'. When I run:
ino build, I get:
Traceback (most recent call last):
File "/usr/local/bin/ino", line 3, in
from ino.runner import main
ImportError: No module named ino.runner

I believe the correct place to install would be
/Library/Python/2.7/site-packages/ino
If I'm in error please let me know the correct procedure to install on
OSX; I'm not terribly knowledgable of python.

running 'python setup.py' with no CL flags seems to install in the
proper place. I'm not sure what the best solution is so I just
create a new make task

Tylerc230 added some commits May 4, 2012
@Tylerc230 Tylerc230 Issue #31 'make install' on OSX lion installs in wrong dir
I'm installing ino by cloning the github repo and running 'make
install'. It appears to install the lib files at
'/usr/local/lib/python2.7/site-packages/ino'. When I run:
ino build, I get:
Traceback (most recent call last):
File "/usr/local/bin/ino", line 3, in <module>
from ino.runner import main
ImportError: No module named ino.runner

I believe the correct place to install would be
/Library/Python/2.7/site-packages/ino
If I'm in error please let me know the correct procedure to install on
OSX; I'm not terribly knowledgable of python.

running 'python setup.py' with no CL flags seems to install in the
proper place. I'm not sure what the best solution is so I just
create a new make task
3f65df4
@Tylerc230 Tylerc230 Adding a flag to 'ino serial' to allow setting of picocom escape char
I've add the '--escape' flag to 'ino serial' to allow users to
change the C-a escape char (C-a conflicts with tmux escape char :) ).
2b6129f
@Tylerc230

I blew it. I meant for those 2 commits to be separate pull requests. i guess I was supposed to make 2 branches? Let me know if you want me to remove and retry.

@pfalcon

Yes, you should make separate branches for separate merge requests. git cherry-pick or git rebase -i is easy way to "split" a branch in 2.

@sidneywidmer

could you please merge this in the master branch? Had the exact same problem and this fix works perfectly. Could've saved me half an hour if it where in the master

@moacirosa

Its seems that this same issue happens in Ubuntu 12.04 and also works making use of "python setup.py"

@kitschpatrol

Just ran into this. One more vote for a merge into master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment