There is loads of documentation written for Python, I use it every day. A short summary:
Main entry point is https://docs.python.org/3/, bookmark it It always points to the newest version that exist, but you can select the version that you actually have. Also, in the documentation it is usually mentioned that some function or so "was added in Python 3.x" if it was added later.
The 'Tutorial' is a tutorial, but one for people that can already program. Also, it treats most if not all features of the language (haven't read it for a long time, so ymmv), including the more advanced ones. Very useful to read once you have the basics done, as you will find new wonderful features that come in handy sometimes.
The 'Library reference' is exactly that, it lists all modules that come with Python, that you can just import, such as time. It lists all functionality that a module has, often with a load of examples, but there are also more densely documented modules, that you may not immediately understand. The table of contents is organized on topic, so you can find easily all related modules in some area that you are looking for.
The 'Language Reference' is about the Python language itself. It's the precise description of the language, including all details how it works. It's useful if you need to know precisely how it works. Likely you will find it difficult to read, as it's dense material.
The 'Python setup and usage', I have no clue whatsoever.
The 'Python Howtos' is more of a guide on some areas, describing what is available, and how to do things in practice. Don't look there often, but can be useful at times.
The 'Installing Python Modules' is about installing (non-standard) Python modules. There are a few zillion Python modules out there at the Internet. If you think "he, this looks useful enough to make a module for", it's a safe bet that someone has already done that and put it at the Internet.
The 'Distributing Python Modules' is the other side, you wrote a module, how to publish it?
The 'Extending and embedding' is about connecting Python to C and vice versa. Only useful if you also know C/C++ and want to call C from Python code or Python from C code. The 'Python/C' API is like the library reference for it.
The 'FAQ' has questions with answers obviously, no idea what, though.
With 'Indices and tables':
The 'Module Index' is the #1 goto page for accessing the module documentation. You can also find a link at the top-right of the page.
The 'Index' basically contains all Python words, I sometimes look there, but I use the search box at the top much more often.
So there you have it, enough for a few holidays reading material
Quote
Could I combine time with a while statement, to keep the game going until time reaches required time state?
Not with input, as it blocks until you hit 'enter'. You can do it in the console terminal if you really insist, but it's not that simple in Python, as it's close to the operating system.
It becomes much easier if you switch to eg pygame, where you get events when the keyboard is used automatically, so I think the simpler solution is to accept now that you cannot abort until 'enter' is pressed, and revisit this problem when you're in the event based world of many graphical programming systems.