n causing problems with node-waf ? (bug)

[alessioalex]

Since I installed n and tried to also install something like GeoIP or anything else that needed compiling with node-waf, I get:

Traceback (most recent call last):
File "/usr/local/bin/node-waf", line 14, in
import Scripting
ImportError: No module named Scripting

I have python 2.7, I run on node 0.4.12 and these things compiled before using n.

I'm no expert, but on a forum I found this:

"In fact nodejs-waf script adds /usr/share/nodejs/wafadmin and Tools/
to sys.path before importing Scripting module.
That might be screwed by setting PREFIX_NODE environment variable.
Is that the case for you ?"

And on n's documentation I seen something mentioned about PREFIX_NODE.

Please look into this, n is perfect and I want to keep using it, but at the same time I sometimes need compiled node modules :)

[tj]

hmm that scripting thing looks familiar, I thinkkk that's a python version issue, i'll check it out when i have a minute

[tj]

which os? I just ran into this for osx lion, I noticed ns copies were all messed on lion too

[alessioalex]

Ubuntu 11.04

[tj]

hmm weird :s will have to look into this later