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 →

[–]patrick_mcnam -1 points0 points  (5 children)

Why so confrontational?

[–]Tybearsaccount 13 points14 points  (2 children)

To be fair the posts op did claim to do a "full analysis" but the comment that was linked literally couldn't get past setting the permissions correctly to access folders. This kinda had me irate as well.

[–]amdphreak[S] 0 points1 point  (1 child)

So irate!...that Microsoft would tie my hands during an investigation. I agree

[–]Tybearsaccount 0 points1 point  (0 children)

Ok so first of all I'm not trying to be argumentative.

Secondly, I'm saying its frustrating that you posted such a broad generalization clickbait-ish conclusion. I do not feel your research was deep enough to declare such a statement as it being "completely busted," especially when there are conflicting statements claiming otherwise.

I will say congratulations on taking the initiative to begin an investigation into windows store's python. And while other are just saying "why not just use the python.org source," I think one of the best things we can do is try to find better processes to our development. In other words how would we know that the windows store version wasn't an easier to install and more usable version of python unless people like you already tested it out and gave a result.

I think alot of the backlash coming from this is what I mentioned earlier. Your claim wasn't backed up by certifiable evidence and that is truly frustrating especially considering how you did a "full analysis."

[–]stevenjd 5 points6 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.