When somebody mentions the installation problems that come with Python, you soon see a deluge of people asking why nobody is fixing this.īut of course people are working on this. It's not like nobody knows about it, so why is it not fixed? I mean it's one banana, Michael. You may use the "py launcher" (recommended on Windows, but only available through the official installer), version suffixes (on Unix, or with the windows store), a GUI (anaconda launcher), a single entry point rewritten depending on your context (pyenv).Įven if none of that were a problem, the installation may very well be broken, which may happen because they are shipped that way (homebrew, the windows store), because of a failed installation process (pyenv) or because of missing dependencies (Linux packages). Since we are mentioning several versions of "python" or "pip", another issue is that running those require a different magical incantation depending on the OS you are using and the method of installation. Requiring knowledge and discipline is the opposite of what a streamlined experience looks like.
We solve that int the recipes given the weeks before, but this requires users knowing about it, and having discipline. Because when people call "python" or "pip", it's not uncommon they have several versions of those on their machine, and have no idea which one they are calling. Often, they will fight for the PATH.Īnd the PATH is what's winning or losing the war. People are faced with too many options, and have no time, desire and sometime skills to evaluate them.īut the paradox of choices is only the tip of the iceberg, the real trouble arises when the user uses several of them, because they don't play well with each other. I won't surprise you if I say the first issue of the Python installation process is how many ways there are to do it.
0 kommentar(er)
