The function returns something like that
To make things more readable you could return dictionary (as suggested by ichabod801) or namedtuple. Then you have labels associated to your values to comprehend their meaning (FYI: namedtuples from collections built-in module are lightweight, immutable and have nice clean syntax to access values, something like: monsterpower.bosslevel
I observed that you imported module inside the function. Is there particular reason to do so? If there is no such reason I suggest to stick to PEP8 - Imports:
(17, 15, 25, 154, 2, 4, 6, 10). I don't think that this is something which can be easily interpreted say in two weeks. What order, what values etc.To make things more readable you could return dictionary (as suggested by ichabod801) or namedtuple. Then you have labels associated to your values to comprehend their meaning (FYI: namedtuples from collections built-in module are lightweight, immutable and have nice clean syntax to access values, something like: monsterpower.bosslevel
I observed that you imported module inside the function. Is there particular reason to do so? If there is no such reason I suggest to stick to PEP8 - Imports:
Quote:Imports are always put at the top of the file, just after any module comments and docstrings, and before module globals and constants.
I'm not 'in'-sane. Indeed, I am so far 'out' of sane that you appear a tiny blip on the distant coast of sanity. Bucky Katt, Get Fuzzy
Da Bishop: There's a dead bishop on the landing. I don't know who keeps bringing them in here. ....but society is to blame.
Da Bishop: There's a dead bishop on the landing. I don't know who keeps bringing them in here. ....but society is to blame.