Im not sure of when pip was introduced, or more importantly when it was considered "the" method of installation. I know it was included in python 2.7.9+ and 3.4+. It seems crazy that it is already considered "the" method of installation already.
I am also not sure why i am so anti-pip. I guess the main reason is it seems to hide too much of what is going on behind the scenes. And like knowing what is going on. So much so that i sometimes manually copy libs to the proper directory in python when i had trouble installing a wheel with pip on windows.
Most of the time i am not in windows. And most of the time linux repos has a repo of the required library. But sometimes the version does not match or the repo does not exist. I still prefer downloading the wanted version and building via setup script.
I mean one part i dont understand is we tell people to use command prompt/terminal to know what is going on under the hood VS using an IDE...but yet we expect them to not know when installing...and just take the easy road.
I am also not sure why i am so anti-pip. I guess the main reason is it seems to hide too much of what is going on behind the scenes. And like knowing what is going on. So much so that i sometimes manually copy libs to the proper directory in python when i had trouble installing a wheel with pip on windows.
Quote:If you are really having trouble with pip. You can just simply copy the pygame files over to your python installation. If you downloaded the incorrect wheel this will also fail. Since windows cannot extract a wheel file all you need to do is change the wheel extension to zip instead. Extract it. It will extract 3 directories, pygame, pygame***.data, and pygame***.dist-info. The stars are where the version and bit type are. Go into pygame***.data directory and copy headers directory over to your python's include directory. So in the end, you should have C:\PythonXX\include\headers. Now rename that headers directory to "pygame". (C: \PythonXX\include\pygame) Now go back to you extracted directories from the wheel. Copy both the pygame and pygame***.dist-info directories over to pythons's Lib/site-packages directory. So these two directories will be placed into C:\PythonXX\Lib\site-packages\. (C:\PythonXX\Lib\site-packages\pygame and C:\PythonXX\Lib\site-packages\pygame***.dist-info) Now attempt to import pygame and see if was installed correctly.
Note this directory is based on the fact that python was installed at the location C:\PythonXX. Python3.4 defaults to this location whereas python3.5 and greater default to other location. You can find this location by opening a python interpreter and executing the line
Most of the time i am not in windows. And most of the time linux repos has a repo of the required library. But sometimes the version does not match or the repo does not exist. I still prefer downloading the wanted version and building via setup script.
I mean one part i dont understand is we tell people to use command prompt/terminal to know what is going on under the hood VS using an IDE...but yet we expect them to not know when installing...and just take the easy road.
Recommended Tutorials: