Just a couple quite notes:
is a slightly more simplified form of 'cat filename | less' same goes for 'more'.
Just to explain these commands, 'cat' will dump information from any file or any device under '/dev/' (you'd probably not want to be playing with the '/dev/' area until you know what you're playing with). It works well with devices because it just does an unformatted dump of data.
Both 'less' and 'more' offer the user some flexibility when reading large blocks of text. Such as scrolling around to read text and also search for text ('/' to activate search) 'q' will quit. I'd recommend using 'less' over 'more' as it's a more advanced (newer) system.
If you use the pipe '|' symbol it is telling the first piece of software to put its output through the second piece of software. Great if the first piece of software actually processes data.
Hitting 'shift-page up' or 'shift-page down' under a terminal will scroll up and down through the old output.
As to where stuff goes, there are 4 standard options:
1) It was installed from the package manager, so it goes under the standard system layout (bits scattered between /lib /bin /lots-more
2) It's under /home/user and you're happy with that (ie only that user wants the software).
3) /opt - this seems to be a common dumping ground for mostly self contained programs. Especially popular with modern commercial stuff. I'm not aware of any formal standard as to how it's laid out, not that it would really matter.
4) /usr/local - this pre-dates /opt and does have a standard layout. If there is only one file involved in your finished product (ie the python script itself) then it should really go into /usr/local/bin.
So, if there is only the one file to move, option 4 is the obvious one. If there are lots of files to move, and you're not looking to learn too much about /usr/local's layout, then option 3 is the best one. You can always revert to option 4 from option 3 at a latter date after gaining some more experience.
Program output is down to how the coder made the software work
. Typically it will go to wherever you are when you run the program: ie if you're in /home/user and you run a piece of software in /usr/local/bin, then output will go to /home/user. Not guaranteed though.