It’s not a linux thing to put programs in the path. I use windows 10 all day and I can just run any prgram I install without special path editing. Only python requires this. When you say “only linux” you’re spreading propaganda to push a hidden objective that harms users.
-
-
I just went through my own PATH and the only things there are x-plat ports, system commands, and potential DLL hijacking issues. No Office, no video/audio editing tools, no games. Not sure what propaganda I'm meant to be pushing. The Windows design philosophy?
2 replies 0 retweets 0 likes -
The propaganda you’re pushing is that Python has to be this way because Windows is not Linux and only Libux allows you to access software easily. This is not only false on its face, but also denies that OSX’s installer exists. There is a hidden agenda to why you do this.
1 reply 0 retweets 0 likes -
It's not hidden. I want Python to work well for Windows users on Windows. I don't want Python being responsible for breaking other people's software. It's not an easy balance, especially given 99% of online posts ignore Windows (but Windows users still read them).
2 replies 0 retweets 0 likes -
This is also a motte-and-bailey fallacy and propaganda tactic: https://rationalwiki.org/wiki/Motte_and_bailey … First you don't do this because "it's a Linux thing", then when I prove you wrong you retreat to "it will break 1% of software". Both statements from you also have zero evidence, just words.
1 reply 0 retweets 1 like -
No, I started not doing it because it breaks software. I argue with people who say "everyone does this" by pointing out that "Linux does this". It's not propaganda, it's a position based on experience and deep familiarity with the issues involved.
1 reply 0 retweets 0 likes -
It doesn't break software. Maybe it broke software back in the old days but now it totally works. Additionally, if node can do it then you should just be like node. If not then you are causing suffering to work around your incompetence.
2 replies 0 retweets 0 likes -
Being just like node requires that we stop supporting side-by-side installs of different Python versions. I'm actually totally okay with this, and tried to adjust our release cycle to accommodate. Rest of the team voted it down, so there'll be more SxS now.
2 replies 0 retweets 0 likes -
Whoooaaa, I thought they just killed off Python 2 so why do you need side-by-side installs available to the entire planet instead of the 100 people who maybe need them?
1 reply 0 retweets 0 likes -
Because people need packages that run on 3.7 but not 3.8 (yet), or an app that only works on 3.6 but nothing later. Really, because Python's cross-version compatibility isn't good enough. Lot of work going into fixing that too. Many moving parts here!
2 replies 0 retweets 0 likes
You mean 10 people need that. And, nobody gets that capability out of the box with Python anyway. You need quite a lot of expert gear. You could also have a second installer that was aimed only at the 10 experts who need this. But nope, gotta make everyone suffer.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.