install package in specific python version

anaconda3/lib/python3.7/site-packages (from requests) (3.0.4) Requirement already satisfied: chardet=3.0.2 in. Requirement already satisfied: certifi>=2017.4.17 in. anaconda3/lib/python3.7/site-packages (from requests) (1.24.1)

For example, if I run the following command: → pip install requests However, you might notice that the output of the command does include a reference to a particular package version. When we run this command there is no mention of any sort of package version. In this course so far we have installed Python packages using the command pip install, where is the name of the Python package that you want to install. If the change is not backwards compatible (so it is a 'breaking change'), the major version is increased. If the change is a backwards compatible piece of new functionality, the minor version is increased. If the change is a backwards compatible bug fix, the patch is increased. The changes are split according to three different categories: Whenever a change is made to a Python package, the version number is changed (regardless of how small the change is). For example, at the time of writing the latest version of the requests package is 2.24.0 .

where major, minor, and patch are all integer numbers. Python packages, however, are versioned according to a strict format: Similar to text documents, Python packages are 'versioned' so that we can easily keep track of what is in each version. Alternatively, you might use a file name based on the date: myfile22062020.doc , myfile23062020.doc , myfile27062020.doc . When you have previously worked on text documents you might have found yourself naming files as myfile.doc , myfilev2.doc , myfilev3.doc , etc., so that you can keep track of which version is which.

Install package in specific python version