I recommend setting up a proper project structure, instead of the one-file approach which tends to get cluttered and hard to maintain. Then, organize your classes and functions into modules (files) and subpackages based on functionality.
Thanks for the suggestion, Yeah that's right, handling one-file approach for large piece of code looks hard to maintain. And sometimes hard to debug. Also, I checked yesterday Pylint gives some warnings about " Too many statements (51/50) (too-many-statements)" this seems I've written something more than 50lines in a function. well, that needs to be split...
Anyway thanks again and Happy new year.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I recommend setting up a proper project structure, instead of the one-file approach which tends to get cluttered and hard to maintain. Then, organize your classes and functions into modules (files) and subpackages based on functionality.
Thanks for the suggestion, Yeah that's right, handling one-file approach for large piece of code looks hard to maintain. And sometimes hard to debug. Also, I checked yesterday Pylint gives some warnings about " Too many statements (51/50) (too-many-statements)" this seems I've written something more than 50lines in a function. well, that needs to be split...
Anyway thanks again and Happy new year.