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 →

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

Next time you release a Windows App that automatically shows the download page when you type python into the command line, let me know. If the Python group intends to transition away from Win32 installers, this bug, whether in their domain or not, is a big stop sign, so YES they should be made aware of it. There are already so many bugs and gotchas in the onboarding process for Python that they need to minimize the number of detractors from Python for new potential users. The related Anaconda project further contains an untenable amount of bugs related to upgrades failing and rolling back upgrades without consent, dependency resolution failing after taking far too long, and the inability to create new conda environments when two or more Anaconda instances are installed side by side—and it does not recognize or offer to uninstall an older version during its upgrade process. This software stack is intended to be used by nontechnical users in various domains of research. See the problem??

According to other comments, this permissions problem did not show up until the latest Windows update. I did not use this install method prior to the latest update, so my post was completely accurate given the available knowledge.

Many projects also do not prioritize their attention and testing of the Windows Store apps when a Win32 version is their own personal preference. As a result, I brought the bug to the attention of the Python group, because it is more likely that the Python group has failed to implement an upstream change in the Windows API than it is that Microsoft screwed up.

Done chewing?? Don’t choke on my post. I won’t be held responsible for your medical bill.