r/Python • • Sep 15 '15

Ask microsoft to include Python in Windows by default

https://windows.uservoice.com/forums/265757-windows-feature-suggestions/suggestions/6693586-ship-python-3-and-python-2-with-windows-10
1.2k Upvotes

329 comments sorted by

View all comments

33

u/the_hoser Sep 15 '15

Why stop there? Let's provide a Ruby interpreter as well! Maybe we can go a little wild and include TCL!

Why should Microsoft provide an interpreter for your favorite language?

I'd rather they just include a decent C compiler and some standards-compliant build tools. This would solve more problems than bundling a version of Python with the OS would ever solve.

4

u/port53 relative noob Sep 15 '15

For 99% of Windows users that would just be huge amounts of bloat.

2

u/the_hoser Sep 15 '15

You're right! But you seem to be missing the point of my statement. I consider adding Python to also be the same kind of bloat.

Or are you referring to the C compiler?

1

u/BobHogan Sep 16 '15

It isn't about Python being someone's favorite language. Python is rapidly rising to the top of the list of most desirable languages to know. Its robust, easy, can run anywhere there is a C compiler (which is almost everywhere except windows), and powerful. Its not a fair comparison to a language like Ruby, or Lisp, or whatever else you want to list, since it is so much more popular than those are.

2

u/the_hoser Sep 16 '15

Right, I agree with you. Python is awesome.

Why does it need to be bundled with Windows?

1

u/BobHogan Sep 16 '15

It doesn't need to be bundled with Windows but that doesn't mean it shouldn't be. Photo apps don't need to be bundled with windows. A browser doesn't need to be bundled in with the OS. Neither does a calculator app. Yet they are bundled in because the pros vastly outweigh the cons. The same is true for Python. There are enough people using Windows that are frustrated over non native support (millions) that it does justify bundling it in. There are no downsides that can't be easily addressed. And the "bloat" is negligible considering the size of the OS itself.

4

u/the_hoser Sep 16 '15

It doesn't need to be bundled with Windows but that doesn't mean it shouldn't be.

I argue that it shouldn't be.

Photo apps don't need to be bundled with windows.

You're right. Web browsers can probably do that job.

A browser doesn't need to be bundled in with the OS.

Blasphemy. How else will I download firefox?

Neither does a calculator app.

Agree. Web browser can do that.

Yet they are bundled in because the pros vastly outweigh the cons.

For the web browser, I agree.

The same is true for Python.

I disagree.

There are enough people using Windows that are frustrated over non native support (millions) that it does justify bundling it in.

Again, I disagree. There are plenty of frustrated Python developers. Most Windows users could not care less about its abscence from the OS.

There are no downsides that can't be easily addressed.

I disagree. Version fixation is a very real problem in the Python community. Windows would only make it worse.

And the "bloat" is negligible considering the size of the OS itself.

Sure. I guess. I'm not worried about how much disk space can't be used to store photos and pirated movies.

The 'bloat' I refer to is the organizational bloat of maintaining YET ANOTHER FEATURE. Does the Windows team really need to take on this responsibility? You can't just clone the latest version off Python.org and ship that with the disk image. Microsoft would have to take personal ownership of the version of Python that they ship with Windows. It would need more than the one guy working on Windows support in Python to make it so. They would have to audit the code (good for Python in the near term, if they share their code. The coin's still flipping in the air as to whether or not they would.)

In the long term, it would be a disaster. The version that ships with windows would be the most popular version of Python in the world. It would become the version of Python. Python 3.7 just came out? Who cares? Microsoft only offers 3.4.7 and that's what we use. That's what the libraries use. That's what everybody uses.

I'd rather just have them help us with improving the behavior of Python in Windows. They're doing just that. They have a full-time developer doing just that.

Don't mess with a good thing.

2

u/[deleted] Sep 16 '15

I like that almost everywhere except windows excludes most computers.

4

u/desmoulinmichel Sep 15 '15

It's not because it's my favorite language.

It's because :

  • Mac and Linux already have it pre-installed and us them a lot. This proves both robustness and usability.

  • Python is the only language that is good at scripting AND many other things. Usually you have either good scripting OR other things. E.G: ruby has a great ecosystem in the Web, but is less competitive in other area

  • C-compiler is an entire different issue. Embedding python doesn't target primarily app dev, but scripters, so they can share the script with non dev, or deploy it on a lot of machines on an heterogeneous park.

13

u/theywouldnotstand Sep 15 '15 edited Sep 15 '15

Arch linux user here. Had to install python manually (as is true with most software on arch.)

The key difference here, is that most Linux distributions have python packages that are easy to install and update using tools included in the distro. Windows does not do this, so it's up to the user or administrator to install and maintain.

It would be nice if microsoft maintained a python package that is optional to install through windows update, but I don't think it should be automatically installed. Most windows users wouldn't use it.

5

u/the_hoser Sep 15 '15 edited Sep 15 '15

Mac and Linux already have it pre-installed and us them a lot. This proves both robustness and usability.

Faulty assumption. I administrate at least one Linux system (that I can recall) that does not have Python installed. I agree that it is common for Linux distributions to have a Python interpreter installed, but it's not all roses and candy. RedHat is using python 3.1 for craps sake.

Python is the only language that is good at scripting AND many other things. Usually you have either good scripting OR other things. E.G: ruby has a great ecosystem in the Web, but is less competitive in other area

That's just like, your opinion man. Don't get me wrong, I love Python, too, but I know a number of Ruby programmers that would say exactly the same thing you just said, and they would be no less right or wrong than you are.

C-compiler is an entire different issue.

It is the issue. Since there is no standardized way to build software on windows (vs OS X and Linux) then it is difficult to deploy python and python plugins to windows.

Embedding python doesn't target primarily app dev, but scripters, so they can share the script with non dev, or deploy it on a lot of machines on an heterogeneous park.

Then why not Bash, or some simple implementation of a Unix shell, existing as a subset of Bash? If all you want is heterogeneous scripting, let's go with the path of least resistance.

EDIT: Also, I just realized that, if Microsoft were to produce a *sh implementation, they might actually be forced to fix their faulty shell handling! Win-win for everybody!

7

u/net_goblin Sep 15 '15

It is the issue. Since there is no standardized way to build software on windows (vs OS X and Linux) then it is difficult to deploy python and python plugins to windows.

Since when is the way to build software standardized on OS X and Linux? Plain GNU make, autotools + GNU make, CMake + GNU make, CMake + Ninja, scons, ... the possibilities are endless. They only don't break between compiler versions as often as Visual Studio projects. But calling it standardized is more than bold.

2

u/the_hoser Sep 15 '15

You do have a fair point. I concede that it's not Microsoft's responsibility to do it the way Linux/OS X do it.

In that case, I wish only that they would standardize on a set of build tools and include them with the operating system.

-2

u/desmoulinmichel Sep 15 '15

Faulty assumption. I administrate at least one Linux system (that I can recall) that does not have Python installed. I agree that it is common for Linux distributions to have a Python interpreter installed, but it's not all roses and candy.

Fedora and Ubuntu represent 90% of the market. You can always find exception for verything. The only thing it leads is to do nothing.

RedHat is using python 3.1 for craps sake.

It's enough.

That's just like, your opinion man.

No it's not. It's not that there no other languages capable of such. it's just that their ecosystem didn't develop in that direction. It's not a technical thing, it's a social thing. You can do data analysis with Ruby, but they use the banks and the scientits are using Python. And you can use Ruby for scripting, but admin are using Python.

It is the issue.

It is AN issue. And is has nothing to do with cross plateform scripting.

Embedding python doesn't target primarily app dev, but scripters, so they can share the script with non dev, or deploy it on a lot of machines on an heterogeneous park.

Then why not Bash, or some simple implementation of a Unix shell, existing as a subset of Bash? If all you want is heterogeneous scripting, let's go with the path of least resistance.

Because :

  • MS is involved in Python, not bash.

  • Python can do more than bash.

  • bash is file oriented (unix philosophy) while python is general purpose oriented.

It's not a matter of preference.

I do love Python.

But it's objectivelly the best tool for this situation.

There is a reason you find it everywhere : web dev, finance, science, 3D, scripting, prototyping, geospatial, glue... It's very versatile and easy to use, and super portable, while not being focus on a specific use.

3

u/iamhaz Sep 15 '15

Fedora and Ubuntu represent 90% of the market. You can always find exception for verything. The only thing it leads is to do nothing.

Got a source on that?

That's just like, your opinion man.

No it's not. It's not that there no other languages capable of such. it's just that their ecosystem didn't develop in that direction. It's not a technical thing, it's a social thing. You can do data analysis with Ruby, but they use the banks and the scientits are using Python. And you can use Ruby for scripting, but admin are using Python.

Admins are using the right tool for the right job, that may or may not be Python, it's often Bash, or even Perl or <insert obscure language of the week here>. Python isn't a special snowflake in this regard.

It is the issue. It is AN issue. And is has nothing to do with cross plateform scripting.

Embedding python doesn't target primarily app dev, but scripters, so they can share the script with non dev, or deploy it on a lot of machines on an heterogeneous park.

Python can do more than bash.

Bash can do just as much as Python.

bash is file oriented (unix philosophy) while python is general purpose oriented.

Wat.

It's not a matter of preference.

It's pretty clear it is a matter of preference to you. Nothing wrong with that, but don't pretend it isn't.

I do love Python.

We can see that :)

But it's objectivelly the best tool for this situation.

Nothing about this is objective.

There is a reason you find it everywhere : web dev, finance, science, 3D, scripting, prototyping, geospatial, glue... It's very versatile and easy to use, and super portable, while not being focus on a specific use.

Same could be said about any language if you try hard enough.

→ More replies (2)

0

u/the_hoser Sep 15 '15

And any Ruby fanboy would sling similar sounding arguments about why Ruby is the best tool for this situation.

Fedora and Ubuntu represent 90% of the market. You can always find exception for verything. The only thing it leads is to do nothing.

You're absolutely right there. I was merely pointing out that it's not as ironclad a bundle as you seem to be convinced it is.

No it's not. It's not that there no other languages capable of such. it's just that their ecosystem didn't develop in that direction. It's not a technical thing, it's a social thing. You can do data analysis with Ruby, but they use the banks and the scientits are using Python. And you can use Ruby for scripting, but admin are using Python.

We're talking about scripting here. Anything that can open a subshell qualifies.

The Rubyist would argue that the scientific stuff isn't as important as the web stuff. They would point out that their standard VM routinely outperforms the Python VM. They would also point out that OS X is bundled with Ruby, and that anybody using Linux could easily install Ruby.

I'm not advocating Ruby, here. I'm merely pointing out that your position is one of opinion and preference. There's nothing objective about it.

It is AN issue. And is has nothing to do with cross plateform scripting.

And deploying for Python on Windows will remain just as heinous as it is today. Using a C extension? You're screwed. This is a bigger problem than anybody's scripting concerns would ever be. It's easy to throw together two scripts. It's a huge pain to deploy real Python applications, and none of this will help.

MS is involved in Python, not bash.

Microsoft has provided a shell implementation in the past. They can do it again.

Python can do more than bash.

I thought that you were worried about scripting?

bash is file oriented (unix philosophy) while python is general purpose oriented.

Being file-oriented makes it really ideal for the kinds of scripting many administrators do. I realize that Windows has some more complicated constructs, and the scripting of those constructs would be a little... less natural in Bash, but I don't see how it'd be any more natural in Python. A command to make DCOM calls would be just as easy to use as a library to make DCOM calls.

It's not a matter of preference.

Yes it is.

But it's objectivelly the best tool for this situation.

No, it isn't. There's nothing objective about it.

There is a reason you find it everywhere : web dev, finance, science, 3D, scripting, prototyping, geospatial, glue... It's very versatile and easy to use, and super portable, while not being focus on a specific use.

I agree. It's a fantastic language. And as a matter of preference, it's a popular one.

Java is more popular, though. It's used for almost all of those things, and more. If popularity was the metric we're going for here, why doesn't Microsoft bundle Java instead?

Right... they tried that. They also modified it beyond recognition, creating a schism in the Java community. At least Guido isn't as evil and lawsuit-happy as Sun was.

1

u/desmoulinmichel Sep 15 '15

And any Ruby fanboy would sling similar sounding arguments about why Ruby is the best tool for this situation.

They could not as Ruby is not installed by default on Linux. The whole thing here is about default installation.

The Rubyist would argue that the scientific stuff isn't as important as the web stuff.

For which Python works well (you know this youtube website is coded in Python...). So Python is popular in the Web AND outside of the web.

Most importantly, MS has invested in Python, Linux distro has invested in Python. Banks have invested in Python. Google have invested in Python. Not Ruby. Python.

They would point out that their standard VM routinely outperforms the Python VM.

Which for scripting has no importance.

Microsoft has provided a shell implementation in the past. They can do it again.

It's a lot more work than installing Python by default, which does more than bash.

I thought that you were worried about scripting?

Additional bonus doesn't hurt. Python is fantastic at scripting. The plus is, it's not JUST fanstastic at scripting.

No, it isn't. There's nothing objective about it.

What's not objective about :

  • people use it a lot;

  • it does the job;

  • it's installed on most competitors;

?

why doesn't Microsoft bundle Java instead?

Because it's not a scripting language. Because it's not installed on Mac and Linux already.

They also modified it beyond recognition, creating a schism in the Java community.

You don't need to modify Python to make it work. You can just ship it the way it is. Plus MS already has a foot in the Python word. They are already doing it right.

2

u/the_hoser Sep 15 '15

They could not as Ruby is not installed by default on Linux. The whole thing here is about default installation.

Any Linux admin worth their salt can install Ruby in 10 seconds. If you're worried about clueless end-users, don't. There are none in the Linux world.

For which Python works well (you know this youtube website is coded in Python...). So Python is popular in the Web AND outside of the web.

Ruby is, in my experience, far more popular than Python for web development. Python does a good job, for sure, but the culture is with Ruby on this one.

Most importantly, MS has invested in Python, Linux distro has invested in Python. Banks have invested in Python. Google have invested in Python. Not Ruby. Python.

Twitter invested in Ruby, Github invested in Ruby, Hulu invested in Ruby...

We can do this all day.

What's not objective about :

people use it a lot;

it does the job;

it's installed on most competitors;

?

Moot points. The same could be said for Java or Flash. Bash is arguably even more popular.

You don't need to modify Python to make it work. You can just ship it the way it is. Plus MS already has a foot in the Python word. They are already doing it right.

And here's the crux of the proplem: They will modify Python. What's worse, they won't fix the core problems of developing and distributing applications written in Python on windows. Bundling Python would actually have the potential to make it worse. It's already bad on OS X. People shy away from Python 3 because their laptop doesn't have it by default.

And the proposed solution still doesn't solve the binary module problem. If you dare write something in a later version of Python that Microsoft deigns to provide, then you still have the same problems that we have right now. You still have issues with binary modules.

You're not making windows better with this. You're making Python worse.

1

u/[deleted] Sep 15 '15

This whole conversation is about having cross platform defaults. The fact a sys admin can install Ruby doesn't matter when I want to send a cleanup script to my mom.

1

u/the_hoser Sep 15 '15

It's still platform-specific, though. Even if it's in the same language. You're going to have three scripts in one file instead of three scripts in three files. I don't see any value in this.

1

u/[deleted] Sep 15 '15

I've written plenty of scripts that work cross platform. Anything that doesn't affect system files will be fine.

Simple example, you want to process 10,000 photos and convert the RAW images into web jpg images. This script would be 100% the same on both Windows and Linux. Launch the script, choose the input/output directories, and away you go.

→ More replies (0)
→ More replies (2)

0

u/desmoulinmichel Sep 15 '15

And... come on... you want this too !

:p

2

u/the_hoser Sep 15 '15

NO! NO NO NO NO NO! I do NOT want this!

It would literally be the worst thing to happen to Python in Windows. It would co-opt the definition of "Python" to be "the version on Windows" all of Python software would be written to conform to their version, with whatever modifications they decide to make.

The best thing that Microsoft could do for Python is to provide a standards-compliant C compiler and build environment. Beyond that, their contributions to make Python work better in Windows are enough.

→ More replies (2)

0

u/jugalator Sep 15 '15

Why should Microsoft provide an interpreter for your favorite language?

I think it's simply to have an interpreter that can be used cross platform. At least one. There exists no interpreter that is a) bundled and b) cross platform across Windows, Mac, Linux today.

5

u/the_hoser Sep 15 '15

I think Bash would be a better candidate, then. It's less political. It's simpler to deploy (nobody writes Bash plugins), and arguably more stable than Python.

Look, I love Python, but I don't see why it's something that should be bundled with Windows.

→ More replies (2)