Split the grown script into loadable modules

[elfring]

The script “guider.py” grew to a remarkable size.
I imagine that it can occasionally be helpful to import only selected parts from the supported functionality on demand.
How do you think about to offer loadable modules accordingly? 🤔

[iipeace]

There were many requirements about it :)
But I don't like it because It may requires also installation or complex copy to target systems.
Why do you want it? because of memory usage?

[elfring]

But I don't like it because It may requires also installation

How does such a concern fit to your installation instructions?

or complex copy to target systems.

Would you like to collaborate with Python wheels?

Why do you want it?

💭 I imagine that adjusted code structures will support nicer run time characteristics.

because of memory usage?

This is another recurring application concern, isn't it? 🤔

[iipeace]

How does such a concern fit to your installation instructions?

Guider already provides it but it is for PIP or OE.

Would you like to collaborate with Python wheels?

some old and light platforms don't support it ;(

I imagine that adjusted code structures will support nicer run time characteristics.

may I ask you more explanation?

This is another recurring application concern, isn't it?

Yes, right.
Guider is just a complete standalone application :)

[elfring]

may I ask you more explanation?

Yes, of course.

I got the impression that some implementation details from the discussed (Python) software can influence selected program module calls in undesirable ways.

[iipeace]

I can understand it :)
decoupling is needed now,
I will try it step by step.

[elfring]

decoupling is needed now,

I became curious once more how another refactoring can evolve also for this software. 🤔

I will try it step by step.

• How do you think about to move help descriptions to other places?
• Will a reorganisation become helpful for the main program modules?
• Would you like to choose nicer tags (or labels) for this issue?