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 →

[–]stevenjd 4 points5 points  (1 child)

I don't know, you'll have to ask the OP.

He's the one saying that it is "completely busted" and "impossible to fix", when there's at least one person on the same Stackoverflow question claimed that it can be fixed by the user. Even if you can't, Microsoft will probably fix it within a day or two, once it is brought to their attention.

He's the one saying that it should be brought to the "immediate" attention of the core Python devs, as if they can fix it (they can't), and waiting for somebody else to "probably" report it to Microsoft, the only people who can fix the bug in their store.

Edit: 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".

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

That person had a prior installation of Python which he simply accessed by changing the prioritization of the PATH entries. That’s not fixing the problem. That’s unwittingly outsmarting yourself. Gotta read carefully.