Aws cloud9 pip install goes to python 2 7 instead of 3 6

When installing packages using pip in AWS Cloud9, you may encounter a situation where the installation is directed to Python 2.7 instead of Python 3.6. This can be frustrating, especially if you are working with Python 3.6-specific features or libraries. However, there are several ways to solve this issue and ensure that pip installs packages for Python 3.6.

Option 1: Using Python 3’s pip

The simplest solution is to explicitly use Python 3’s pip when installing packages. You can do this by running the following command:

python3 -m pip install package_name

This command ensures that the package is installed for Python 3.6 specifically. By using the python3 command, you are invoking the Python 3 interpreter, and the -m flag tells Python to run the specified module as a script. In this case, the module is pip, and you can then proceed to install the desired package.

Option 2: Virtual Environments

Another approach is to create a virtual environment specifically for Python 3.6 and install packages within that environment. This ensures that any package installations are isolated to the Python version you desire. Here’s how you can do it:

python3 -m venv myenv
source myenv/bin/activate
pip install package_name

In this solution, we first create a virtual environment named myenv using the python3 -m venv command. Then, we activate the virtual environment using the source command. Finally, we can use pip to install the desired package, which will be installed within the virtual environment and associated with Python 3.6.

Option 3: Specifying Python Version in Pip Command

If you prefer not to use virtual environments, you can also specify the Python version directly in the pip command. Here’s how:

pip3.6 install package_name

By using pip3.6 instead of just pip, you are explicitly telling pip to install the package for Python 3.6. This ensures that the package is installed in the correct Python version, regardless of any default settings or configurations.

After considering these three options, the best approach depends on your specific requirements and preferences. If you are working on a project that requires Python 3.6, using Python 3’s pip or virtual environments are recommended. These options provide better isolation and ensure that your project remains compatible with Python 3.6. However, if you only need to install a package for Python 3.6 without any further project requirements, specifying the Python version in the pip command can be a quick and straightforward solution.

Rate this post

7 Responses

  1. Comment:
    Well, this whole Python 2 vs Python 3 thing is like a never-ending maze. Cant we just stick with one and be done with it? 🤷‍♂️

  2. Option 1: Using Python 3s pip – Why not make it the default already?

    Option 2: Virtual Environments – Just another layer of confusion, isnt it?

    Option 3: Specifying Python Version in Pip Command – Ugh, so many extra steps!

Leave a Reply

Your email address will not be published. Required fields are marked *

Table of Contents