Forums » Bugs & Problems Search

NameError: name 'my API_KEY' is not defined New Reply

Author Post
Posts: 3
Registered: Jun 29, 2009

Hello

I'm just starting to have a bash around with remix, looks promising!

I have followed the instructions in the readme file. is config.py supposed to read API_KEY = "1234" or just API_KEY = 1234, do the commas tell python it is a string not a number or something?

But I don't know if that is the problem.

here is my error message:

Tinf:one tomriley$ python one.py 01-Highway To Hell.mp3 output.mp3 (the example script) Traceback (most recent call last): File "one.py", line 10, in import echonest.audio as audio File "/Library/Python/2.5/site-packages/echonest/audio.py", line 38, in import echonest.web.analyze as analyze; File "/Library/Python/2.5/site-packages/echonest/web/analyze.py", line 16, in import echonest.web.config as config File "/Library/Python/2.5/site-packages/echonest/web/config.py", line 5, in API_KEY = TOM'S KEY NameError: name 'TOM'S_KEY' is not defined

Posts: 3
Registered: Jun 29, 2009
print("code sample");

Tinf:one tomriley$ python one.py 01-Highway To Hell.mp3 output.mp3 Traceback (most recent call last): File "one.py", line 10, in import echonest.audio as audio File "/Library/Python/2.5/site-packages/echonest/audio.py", line 38, in import echonest.web.analyze as analyze; File "/Library/Python/2.5/site-packages/echonest/web/analyze.py", line 16, in import echonest.web.config as config File "/Library/Python/2.5/site-packages/echonest/web/config.py", line 5, in API_KEY = MHPJIMECF8N7BQNZU NameError: name 'MHPJIMECF8N7BQNZU' is not defined

print("code sample");
Posts: 105
Registered: Sep 05, 2008

tinfoiled: it should be API_KEY="YOUR KEY", note the quotes

also, remix questions are best asked on the remix google group

Posts: 3
Registered: Jun 29, 2009

yep got it fixed, apart from HTTP Error 500: INTERNAL SERVER ERROR, which I'll assume is related to firewall or something?

also, i really need to delete that uppper post with my api in it! there isn't a button.....

Reply to this Thread

You must log in to post a reply.