search

bbolli / tumblr-utils

Utilities for dealing with Tumblr blogs, Tumblr backup
GNU General Public License v3.0
667 stars 124 forks source link

Python File Opens But Nothing Happens ?? #231

Closed sublucat closed 3 years ago

sublucat commented 3 years ago

Hello, I actually used this program in the past and it worked perfectly, but now it doesn't work for some reason....?? As shown on the picture I attached, when I type in the command and hit enter, the [tumblr_backup.py] file opens but nothing happens. I'm really confused on what I'm doing wrong since the only thing I changed in my python file is adding my tumblr api code.

cebtenzzre commented 3 years ago

That seems like what would happen if you have no file association for python scripts. Try running it as python tumblr_backup.py sublucat instead (assuming you have Python 2 installed and it is on your PATH).

sublucat commented 3 years ago

I really appreciate the fast response. I tried python tumblr_backup.py sublucat as you said, but it still didn't do anything. So I checked the PATH as you mentioned in case I missed something but I can't seem to figure out the issue.

The top image is the command line and the bottom images is the PATH with Python27 in it.

Issue_2

Issue_2b

bbolli commented 3 years ago

Is python.exe in the folder C:\Python27?

Can you try giving the complete path to python, e.g. C:\Python27\python.exe tumblr_backup.py sublucat? Is

sublucat commented 3 years ago

Yes, python.exe is in the C:/Python27 folder. I tried the path you suggested, and now it's giving me this error message.

Issue_3

cebtenzzre commented 3 years ago

@sublucat 401 unauthorized most likely means your API key is wrong. Make sure you've copied your OAuth consumer key.

sublucat commented 3 years ago

@Cebtenzzre Thank you for the input! After changing the OAuth consumer key it started exporting the posts! Although there are some codes that says error should I be looking into the folder again to make sure?

Issue Solved I guess

cebtenzzre commented 3 years ago

@sublucat That's because of non-ASCII characters in posts. It happens easily on Python 2 because raw bytes are interchangeable with ASCII strings. Feel free to open a separate issue mentioning that UnicodeDecodeError. For a quick fix, unicode works better on my fork, especially when used with Python 3.