Install does not work under a virtualenv

[GoogleCodeExporter]

I tried to install pyo under a virtualenv on Ubuntu and it did not work.

To reproduce:
1. Install all dependencies using apt-get
2. Make a virtualenv and activate it
3. Run 'python setup.py install'
4. Try to import pyo. The traceback is attached.

I am using the last svn version (as of today).

Original issue reported on code.google.com by joao.eel@gmail.com on 15 Jan 2011 at 6:16

Attachments:

• pyo_import_error.log

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have just noticed that if you want to run pyo with 64 bits precision, you 
should import pyo64, not pyo. Is there a way to make this transparent to the 
user? The way it is right now, a user cannot run the examples provided with the 
library.

Original comment by joao.eel@gmail.com on 15 Jan 2011 at 6:20

[GoogleCodeExporter]

Hi, I'm not sure why you want to run pyo under virtualenv... Why don't you run 
it directly from the terminal?

For the 64 bits precision, 32 and 64 bits versions can live side by side. You 
just have to build both and use which one you want. There is no way to make 
this choice transparent to the user because it's precisely a user's choice. 
Just build pyo two times:

sudo python setup.py install --install-layout=deb --use-jack

sudo python setup.py install --install-layout=deb --use-jack --use-double

After that, you can use both precisions!

Original comment by belan...@gmail.com on 18 Jan 2011 at 3:08

[GoogleCodeExporter]

Hi,

thanks for the answer. I use virtualenv so I don't have to install packages 
system-wide, but this was not a problem at all. Sorry for not making myself 
clear.

I now understand the difference between versions. I thought the 64 bit was 
supposed to be built everytime you want to run pyo on a 64 bit machine.

This is not a bug at all, you can even delete this ticket :)

Thanks for your work on pyo!

Original comment by joao.eel@gmail.com on 18 Jan 2011 at 3:13

[GoogleCodeExporter]

Yes, 32 - 64 bits, it's just the sample's precision... Nothing to do with the 
architecture!

Thanks for your interest in pyo!

Original comment by belan...@gmail.com on 19 Jan 2011 at 3:59

• Changed state: Invalid