The latest articles on DEV Community by Mohamed Wazeem (@wazcodes). https://dev.to/wazcodes https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2740110%2Fa96f9bb2-054c-49a5-8c6a-15997f6e2bd8.png https://dev.to/wazcodes en Mohamed Wazeem Sat, 01 Nov 2025 10:00:07 +0000 https://dev.to/wazcodes/what-i-learned-while-installing-python-2o5o https://dev.to/wazcodes/what-i-learned-while-installing-python-2o5o <h2> How to Install Python </h2> <ol> <li>Go to <a href="https://www.python.org/downloads/" rel="noopener noreferrer">python.org/downloads</a>.</li> <li>Download the Python installer based on your operating system.</li> <li>Install Python using the downloaded file. <ul> <li>Make sure you check “Add Python to PATH” if you are using Windows.</li> </ul> </li> </ol> <h2> What I Found Interesting </h2> <p>Since my school days, I’ve installed Python many times and even helped others do it. But only recently did I realize an important factor during installation — adding Python to the environment variables.</p> <p>I had noticed that typing <code>python</code> in the Command Prompt didn’t work; instead, I had to use <code>py</code> to check the version of Python I was using. I used to think that <code>python</code> and <code>pip</code> worked only for versions before 3.10, and that for later versions we had to use <code>py</code> and <code>pip3</code>.</p> <p>But I was wrong. The real reason was that I hadn’t added Python to the PATH environment variable during installation.</p> python programming learning