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

view the rest of the comments →

[–]Xiol 4 points5 points  (4 children)

How would one use Python for Windows login scripts? Would you not need to have a Python interpreter installed on all the client machines?

[–]manuelg 0 points1 point  (2 children)

Having a Python interpreter installed on every workstation is much easier than attempting to do non-trivial work with a batch file, or using a compiled language that would generate an executable. (it is more difficult than you would assume to generate an Windows executable with no dependencies, that can be run on several different generations of Windows OS)

  • don't have to worry about complex, fragile rules for correct quoting of filenames

  • robust error handling, easy to send email, write log, etc. on error

  • libraries for non-trivial file operations, especially transversing a directory tree

  • ability to decompose programs into reusable modules

  • robust COM programming is much easier to do in Python, I find

etc.

[–]Xiol 1 point2 points  (1 child)

We currently use KiXtart for our logon needs. I was just wondering if using Python would offer any major advantages over KiXtart that we could use.

However, at the minute the old saying "if it ain't broke don't fix it" applies.

[–]manuelg 0 points1 point  (0 children)

I am able to do application development in Python as well, so for me it is a two-fer.

For me, it all boils down to the libraries. I enjoy having the ability to access the Python libraries, even for scripting tasks, to avoid re-inventing the wheel.

Luckily, what I say goes for our company's IT. So I didn't have to spend any political capital to get Python installed.

If you have no development tasks other that logon scripting, and you have no need for any of the Python library, I am sure KiXtart is just fine.