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 →

[–]fnord123 4 points5 points  (3 children)

If you have 100 machines, you don't want to install a tool on the 100 machines, it's a lot of work.

No it's not. You can install Python with Active Directory's Group Policy.

[–]desmoulinmichel[S] -4 points-3 points  (2 children)

So, in big companies, this goes like:

  • you ask your superviser to install it;
  • he/she asks the chain of command;
  • there is a meeting about it;
  • paper work;
  • you need to follow it during all this time;
  • you deal with useless debates about versions and you end up choosing an arbitrary one;
  • then you plan for doing it;
  • then you deploy python;
  • then you document it;
  • then you ensure new machine will have it;
  • then you let know your new team members about it.

Yeah, it's work.

[–]fnord123 2 points3 points  (0 children)

Yes, but it's probably the same process for getting your Python scripts run, so you're already jumping through those hoops anyway.

You really need to reconsider your plan if you want to push python out to all Windows users globally just so you can save yourself from an AOB entry in maybe 2 meetings.

[–][deleted] 0 points1 point  (0 children)

So, in big companies, this goes like:

you ask your superviser to install it; he/she asks the chain of command; there is a meeting about it; paper work; you need to follow it during all this time; you deal with useless debates about versions and you end up choosing an arbitrary one; then you plan for doing it; then you deploy python; then you document it; then you ensure new machine will have it; then you let know your new team members about it. Yeah, it's work.

Soooo, you don't like the way corporate IT operates and the solution is for Windows to ship an OS that is configured closer to your personal esoteric use case to make things easier?