Rather than having lot's of prints, you can do something like this:
print(
"This will",
"be printed",
"on separate",
"lines.",
sep="\n"
)
I'm not a huge fan of your naming too. Some of the names, like runsys could really use some underscores, like this: run_sys.
I also don't like comments like these:
##########################################
# TRULY CROSS PLATFORM THINGS START HERE #
##########################################
While they do sometimes provide a shred of decent info, ones like these don't really serve a good purpose.
In addition, all the code under your MAIN CODE RUN comment should be encapsulated inside an if __name__ == "__main__": block. This is to ensure that it properly runs on windows. See this Stackoverflow question this Stackoverflow question for more details.
I'm also noticing that you're mixing single quotes, '', and double quotes, "". I'd try to choose one or the other an be consistent.
You also are printing a blank line, or adding a newline to strings in some places. For example, in one place, you do print('Disk usage is:\n'), and in other places, you do things like print(''), or even worse, you do print('Disk usage is ', ) and use a comma. If you need to print with an extra newline on strings, just add the extra newline "\n" to the end of the string.
Finally, instead of having a string with many of the same characters, you can use string multiplication like this: print("#" * 30).
Rather than having lot's of prints, you can do something like this:
print(
"This will",
"be printed",
"on separate",
"lines.",
sep="\n"
)
I'm not a huge fan of your naming too. Some of the names, like runsys could really use some underscores, like this: run_sys.
I also don't like comments like these:
##########################################
# TRULY CROSS PLATFORM THINGS START HERE #
##########################################
While they do sometimes provide a shred of decent info, ones like these don't really serve a good purpose.
In addition, all the code under your MAIN CODE RUN comment should be encapsulated inside an if __name__ == "__main__": block. This is to ensure that it properly runs on windows. See this Stackoverflow question for more details.
I'm also noticing that you're mixing single quotes, '', and double quotes, "". I'd try to choose one or the other an be consistent.
You also are printing a blank line, or adding a newline to strings in some places. For example, in one place, you do print('Disk usage is:\n'), and in other places, you do things like print(''), or even worse, you do print('Disk usage is ', ) and use a comma. If you need to print with an extra newline on strings, just add the extra newline "\n" to the end of the string.
Finally, instead of having a string with many of the same characters, you can use string multiplication like this: print("#" * 30).
Rather than having lot's of prints, you can do something like this:
print(
"This will",
"be printed",
"on separate",
"lines.",
sep="\n"
)
I'm not a huge fan of your naming too. Some of the names, like runsys could really use some underscores, like this: run_sys.
I also don't like comments like these:
##########################################
# TRULY CROSS PLATFORM THINGS START HERE #
##########################################
While they do sometimes provide a shred of decent info, ones like these don't really serve a good purpose.
In addition, all the code under your MAIN CODE RUN comment should be encapsulated inside an if __name__ == "__main__": block. This is to ensure that it properly runs on windows. See this Stackoverflow question for more details.
I'm also noticing that you're mixing single quotes, '', and double quotes, "". I'd try to choose one or the other an be consistent.
You also are printing a blank line, or adding a newline to strings in some places. For example, in one place, you do print('Disk usage is:\n'), and in other places, you do things like print(''), or even worse, you do print('Disk usage is ', ) and use a comma. If you need to print with an extra newline on strings, just add the extra newline "\n" to the end of the string.
Finally, instead of having a string with many of the same characters, you can use string multiplication like this: print("#" * 30).
Rather than having lot's of prints, you can do something like this:
print(
"This will",
"be printed",
"on separate",
"lines.",
sep="\n"
)
I'm not a huge fan of your naming too. Some of the names, like runsys could really use some underscores, like this: run_sys.
I also don't like comments like these:
##########################################
# TRULY CROSS PLATFORM THINGS START HERE #
##########################################
While they do sometimes provide a shred of decent info, ones like these don't really serve a good purpose.
In addition, all the code under your MAIN CODE RUN comment should be encapsulated inside an if __name__ == "__main__": block. This is to ensure that it properly runs on windows. See this Stackoverflow question for more details.
I'm also noticing that you're mixing single quotes, '', and double quotes, "". I'd try to choose one or the other an be consistent.
You also are printing a blank line, or adding a newline to strings in some places. For example, in one place, you do print('Disk usage is:\n'), and in other places, you do things like print(''), or even worse, you do print('Disk usage is ', ) and use a comma. If you need to print with an extra newline on strings, just add the extra newline "\n" to the end of the string.
Finally, instead of having a string with many of the same characters, you can use string multiplication like this: print("#" * 30).
Rather than having lot's of prints, you can do something like this:
print(
"This will",
"be printed",
"on separate",
"lines.",
sep="\n"
)
I'm not a huge fan of your naming too. Some of the names, like runsys could really use some underscores, like this: run_sys.
I also don't like comments like these:
##########################################
# TRULY CROSS PLATFORM THINGS START HERE #
##########################################
While they do sometimes provide a shred of decent info, ones like these don't really serve a good purpose.
In addition, all the code under your MAIN CODE RUN comment should be encapsulated inside an if __name__ == "__main__": block.
Finally, instead of having a string with many of the same characters, you can use string multiplication like this: print("#" * 30).
Rather than having lot's of prints, you can do something like this:
print(
"This will",
"be printed",
"on separate",
"lines.",
sep="\n"
)
I'm not a huge fan of your naming too. Some of the names, like runsys could really use some underscores, like this: run_sys.
I also don't like comments like these:
##########################################
# TRULY CROSS PLATFORM THINGS START HERE #
##########################################
While they do sometimes provide a shred of decent info, ones like these don't really serve a good purpose.
In addition, all the code under your MAIN CODE RUN comment should be encapsulated inside an if __name__ == "__main__": block. This is to ensure that it properly runs on windows. See this Stackoverflow question for more details.
I'm also noticing that you're mixing single quotes, '', and double quotes, "". I'd try to choose one or the other an be consistent.
You also are printing a blank line, or adding a newline to strings in some places. For example, in one place, you do print('Disk usage is:\n'), and in other places, you do things like print(''), or even worse, you do print('Disk usage is ', ) and use a comma. If you need to print with an extra newline on strings, just add the extra newline "\n" to the end of the string.
Finally, instead of having a string with many of the same characters, you can use string multiplication like this: print("#" * 30).
Rather than having lot's of prints, you can do something like this:
print(
"This will",
"be printed",
"on separate",
"lines.",
sep="\n"
)
I'm not a huge fan of your naming too. Some of the names, like runsys could really use some underscores, like this: run_sys.
I also don't like comments like these:
##########################################
# TRULY CROSS PLATFORM THINGS START HERE #
##########################################
While they do sometimes provide a shred of decent info, ones like these don't really serve a good purpose.
In addition, all the code under your MAIN CODE RUN comment should be encapsulated inside an if __name__ == "__main__": block.
Finally, instead of having a string with many of the same characters, you can use string multiplication like this: print("#" * 30).
Rather than having lot's of prints, you can do something like this:
print(
"This will",
"be printed",
"on separate",
"lines.",
sep="\n"
)
I'm not a huge fan of your naming too. Some of the names, like runsys could really use some underscores, like this: run_sys.
I also don't like comments like these:
##########################################
# TRULY CROSS PLATFORM THINGS START HERE #
##########################################
While they do sometimes provide a shred of decent info, ones like these don't really serve a good purpose.
Finally, instead of having a string with many of the same characters, you can use string multiplication like this: print("#" * 30).
Rather than having lot's of prints, you can do something like this:
print(
"This will",
"be printed",
"on separate",
"lines.",
sep="\n"
)
I'm not a huge fan of your naming too. Some of the names, like runsys could really use some underscores, like this: run_sys.
I also don't like comments like these:
##########################################
# TRULY CROSS PLATFORM THINGS START HERE #
##########################################
While they do sometimes provide a shred of decent info, ones like these don't really serve a good purpose.
In addition, all the code under your MAIN CODE RUN comment should be encapsulated inside an if __name__ == "__main__": block.
Finally, instead of having a string with many of the same characters, you can use string multiplication like this: print("#" * 30).