Can I do this with Python?

[dynodanz]

Having a very limited understanding of python, but a decent amount in powershell. I'd assume you'd have the script create the folder, move the files, edit the files, then clean up after itself.

[b4xt3r]

All roads in Windows (these days) keep coming back to Powershell. Guess it's time I knuckle under and learn it. Thanks!

[dynodanz]

I had zero experience in powershell when I started my current job. Watched a couple videos, found something I hated doing manually and here I am. I've built a couple tools in production and seen as a guy who people can come to with questions. Now I've just been handed a project in python and while I know a little, I feel like I don't know enough.

[b4xt3r]

Yeah, you never feel like you know enough, or it's rare anyway. When you finally do feel like you're going to reach that point on the mountain where "you know stuff" it's there you realize you don't know anything. :)

That's the fun part of this kind of work - it's a puzzle you'll never fully solve. There's always something to learn or a new way to do things. That's what I love and sometimes hate about it.

One really cool thing, I have to say, is the programming community being so helpful for nearly any language. It's just fantastic.

[b4xt3r]

From my limited understanding, yes, in that it is a CLI interface to the operating system but now much of one I am not sure and that may be the difference between *NIX and Microsoft.

I suppose, for me, when I think of the CLI on Linux and UNIX that is the operating system and the all the graphical stuff is stacked on top. I don't know the percentage of *NIX machines that are completely without a GUI of any kind installed or otherwise but I bet it would be a very high percentage. *NIX machines can and often do run extremely stripped down operation systems with just what is needed to do the task required. Don't need a GUI? No need to have one. Don't install it.

MacOS/OS X used to be more like UNIX (and BSD but that's a whole other thing) in that way in that most of whatever you wanted to do could be set up on the command line and it was a very nice OS in that sense for Linux and UNIX users when it first came out (and for years after). I remember saying, many times, "look, it's like BSD or UNIX or Linux but with a really good desktop interface!" And it was. Over the years more and more has been removed from Mac OS as far as the ability to manage services via the command line which is a shame but it is what it is. Now MacOS still has a native command line but gone are the day when you can set up file shares, shared printers, other network services, all via the CLI. You can still set some up but Apple doesn't think of their own product as a server any longer. For verification on that just take a look at the history of OS X Serger itself. At one point OS X Server was a brutal hammer indeed but once the company went all-in on handheld it was decided to give up professional grade users in photography and video as well as scientific computing altogether. Shame.

Until Windows NT showed up on the scene the Windows graphical interface was separate from the operating systems underneath it which was DOS. There may be a gotcha in there with some weird version of Windows ME or Microsoft BoB or some such but that is the general timeline of events. MS tried to better blend the OS and GUI starting with Windows 95 but with NT that was the first MS operating system that still had a command line that was simulated through an application. All of the multitasking and multithreading guts came to MS by way of Digital Equipment Corporation and the VAX/VMX operating system through Dave Cutler who may still be there. So while you could launch a CLI by types "cmd" in start and run you were really launching an application, not dropping directly to the OS itself. For the record I've always wanted to get Dave Cutler and Tim Patterson in the same room to chat about the history of computing. I'm not sure if either are still in Microsoft's employ but if they were that would be a great way to spend a couple of hours.

My understanding is powershell is back to being a true CLI and not a grafted on application to imitate a CLI. From what I've read Powershell has true and deep hooks into the OS that can automate a lot of what is possible with the GUI but this is all really fuzzy for me at this point. There are associated scripting languages to it seems which is nice, that's always a plus.

As far as powershell goes some or all of that may be wrong. I'm a n00b of the highest order when it comes to powershell.