Modules

[menator01]

I was just wondering how big the program needs to be before you just create modules to import? What is the common practice on that subject?
Thank

[Larz60+]

Not quite sure what you're asking.

most all scripts import something.
none ever have imports only
technically you can do it, but what's the point?

[menator01]

I was just curious. Like on the learning project I been working on, I created a database module that connects and does the queries. One line of code verses 15 lines. The sqlite3 version checks to see if it exist or not. It's less code I'm having to look/scroll through within the main code. It's not really that big of a deal.
Just wondering what the common practice is.

[deanhystad]

I was wondering the same thing. The easiest thing to distribute is one file, but big files are hard to edit and maintain. Eventually you create some modules and import the module into your program. A module should have a well defined purpose, but depending on what you are doing that can result in rather large modules. You get tired of really big modules so your create sub-modules. To organize your sub-modules you create a directory structure.

It took me months to figure out how to organize my code so I could import my modules and my module inter-dependencies and unit tests and example snippets all work. Even though everything is working I have no confidence that I didn't make some really dumb choices and I'll have to reorganize everything once others start using my code. I have searched for anything that discusses this part of Python and there is not much there. Set your path. Use __import__.py files. Here is how you make a package. Good stuff, but more nuts and bolts than theory or practice.