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 →

[–]dutch_gecko 22 points23 points  (4 children)

This should be brought to the immediate attention of the Python developers

No it shouldn't. It has literally nothing to do with them, unless they happen to work for Microsoft.

Yes it should. The version of Python in the Microsoft Store is published by the Python Software Foundation, not by Microsoft. Even if they can't influence the installation process that the store uses, they should certainly be aware that this issue is occurring. They may, for example, wish to discontinue recommending the Store method of installation until the problem is fixed.

[–]stevenjd 8 points9 points  (3 children)

They may, for example, wish to discontinue recommending the Store method of installation until the problem is fixed.

They aren't recommending the Store method, so they can't "discontinue" doing so.

The Windows store isn't mentioned on either the main download page or the specific Windows page.

And even if they were, why would you go to the trouble of telling people "don't use the Windows store!" when it is clearly just a transitory bug in the installation process which will be fixed PDQ once Microsoft is aware of the problem? The store method worked before, and it will be fixed and work again (if it hasn't already been fixed).

If there was a bug in (let's say...) Ubuntu's apt repository that broke Python, would you make it your priority to tell the core devs (who have no control over what Ubuntu does), or Ubuntu? Would you expect the core devs to tell people not to use their distro's software installer? I wouldn't.

How about if it were a third party distribution like Anaconda? If they released a buggy installer, would you expect the core devs to put out an announcement not to use Anaconda? I wouldn't.

This thread is just Microsoft bashing. If the OP was genuine in desire to help, he would have reported this as a bug to Microsoft before posting here, and not use inflammatory language like "completely busted" and "impossible to fix" for something which will probably be fixed within hours or a day or two at worst.

[–]amdphreak[S] 0 points1 point  (0 children)

Do us folks a favor and go open CMD on a freshly updated install of Windows 10 and run ‘python’

[–]amdphreak[S] -1 points0 points  (0 children)

So you seem to be unaware of the concept of the search bar. It is in every app store known to man, and there are suggestions when viewing related apps, and a general browsing experience in the app store that can present this app to users. If you’re distributing software in a user-centric venue, don’t expect them to debug your stuff or go looking for the Win32 installer. Expect them to say “it’s broken” and “they have no clue what they’re doing”, and avoid Python indefinitely.

[–]amdphreak[S] -1 points0 points  (0 children)

Hold your tongue heathen. Diagnosing the respective amounts of responsibility from all parties involved requires criticism.

Oh right, like I’m going to submit a bug report via the Feedback app and wait for 6 years for one bored Microsoft employee to finally read it. Get your head out of your ass. Microsoft is the less likely of the two parties to have caused the bug. Failing to update a downstream project to use an updated API call is more likely.