So this is really nit-picky, but it would help the readability of the code if you followed the PEP8 style guide. Depending on what editor you use, there should be various plugins that flag pep8 violations in the editor. Here's an example of what it would look like. Hovering over the red line tells me what the editor thinks could be improved.
I've never actually read the entire pep8 guide, but in general:
All imports at the top of the file, starting with standard library imports (import X) in alphabetical order, then third-party packages, then relative imports.
Two new lines before any new function / class definition.
Very picky about spacing and how things should line up.
I can help you find a pep8 plugin and configure it, if you let me know what editor you're using.
So this is really nit-picky, but it would help the readability of the code if you followed the PEP8 style guide. Depending on what editor you use, there should be various plugins that flag pep8 violations in the editor. Here's an example of what it would look like. Hovering over the red line tells me what the editor thinks could be improved.
I've never actually read the entire pep8 guide, but in general:
import X
) in alphabetical order, then third-party packages, then relative imports.I can help you find a pep8 plugin and configure it, if you let me know what editor you're using.