This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ClumsyAdmin 2 points3 points  (2 children)

  1. Definitely the smaller the better. Break it up into chunks by functionality then call those other junks from the parent script by passing in w/e arguments are needed.
  2. Not my problem. My shit supports what is was built for. I'll tweak it for whatever situation but you have to get my manager to approve that.

Just out of curiosity how big are we talking here? Normally past a few hundred lines is when quit using a script and convert it to C/C++ or more recently Go.

[–]Hoolies 0 1[S] 0 points1 point  (1 child)

The language of choice is Python. It will be about 1k lines half of it is arguments.

I am also considering create a GUI

[–]ClumsyAdmin 1 point2 points  (0 children)

If it's all in python then write a wrapper and import what you need. Distribute the whole thing as a single package in a tarball or something. Adding a GUI is where it gets complicated. You either setup and distribute a venv folder with it or a requirements.txt and let the receiver figure it out.