<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://howto.cs.uchicago.edu/lib/exe/css.php?s=feed" type="text/css"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>How do I? python</title>
    <subtitle></subtitle>
    <link rel="alternate" type="text/html" href="https://howto.cs.uchicago.edu/"/>
    <id>https://howto.cs.uchicago.edu/</id>
    <updated>2026-06-20T00:00:46+00:00</updated>
    <generator>FeedCreator 1.8 (info@mypapit.net)</generator>
    <link rel="self" type="application/atom+xml" href="https://howto.cs.uchicago.edu/feed.php" />
    <entry>
        <title>python:conda</title>
        <link rel="alternate" type="text/html" href="https://howto.cs.uchicago.edu/python:conda?rev=1548437284&amp;do=diff"/>
        <published>2019-01-25T11:28:04+00:00</published>
        <updated>2019-01-25T11:28:04+00:00</updated>
        <id>https://howto.cs.uchicago.edu/python:conda?rev=1548437284&amp;do=diff</id>
        <author>
            <name>Anonymous</name>
            <email>anonymous@undisclosed.example.com</email>
        </author>
        <category  term="python" />
        <content>Anaconda

Use system installed version

Conda is installed by default and you should be able to use it without doing anything.

If it does not work for you automatically all you need to do is source the right file.


$ source /opt/conda/etc/profile.d/conda.sh</content>
        <summary>Anaconda

Use system installed version

Conda is installed by default and you should be able to use it without doing anything.

If it does not work for you automatically all you need to do is source the right file.


$ source /opt/conda/etc/profile.d/conda.sh</summary>
    </entry>
    <entry>
        <title>python:pip</title>
        <link rel="alternate" type="text/html" href="https://howto.cs.uchicago.edu/python:pip?rev=1493746626&amp;do=diff"/>
        <published>2017-05-02T12:37:06+00:00</published>
        <updated>2017-05-02T12:37:06+00:00</updated>
        <id>https://howto.cs.uchicago.edu/python:pip?rev=1493746626&amp;do=diff</id>
        <author>
            <name>Anonymous</name>
            <email>anonymous@undisclosed.example.com</email>
        </author>
        <category  term="python" />
        <content>PIP (Python Modules)

Installation

These are general guide lines and not hard and fast rules.

The recommended method of installing via pip is:
  python[3] -m pip install --user &lt;somepackage&gt;
System Wide

Installing python modules system wide is normally done when a larger group of people need a particular module.</content>
        <summary>PIP (Python Modules)

Installation

These are general guide lines and not hard and fast rules.

The recommended method of installing via pip is:
  python[3] -m pip install --user &lt;somepackage&gt;
System Wide

Installing python modules system wide is normally done when a larger group of people need a particular module.</summary>
    </entry>
    <entry>
        <title>python:virtual_environments</title>
        <link rel="alternate" type="text/html" href="https://howto.cs.uchicago.edu/python:virtual_environments?rev=1467305815&amp;do=diff"/>
        <published>2016-06-30T11:56:55+00:00</published>
        <updated>2016-06-30T11:56:55+00:00</updated>
        <id>https://howto.cs.uchicago.edu/python:virtual_environments?rev=1467305815&amp;do=diff</id>
        <author>
            <name>Anonymous</name>
            <email>anonymous@undisclosed.example.com</email>
        </author>
        <category  term="python" />
        <content>Python Virtual Environments

What and Why

A Virtual Environment is a tool to keep the dependencies required by different projects in separate places, by creating virtual Python environments for them. It solves the “Project X depends on version 1.x but, Project Y needs 4.x” dilemma, and keeps your global site-packages directory clean and manageable. For example, you can work on a project which requires Django 1.3 while also maintaining a project which requires Django 1.0.</content>
        <summary>Python Virtual Environments

What and Why

A Virtual Environment is a tool to keep the dependencies required by different projects in separate places, by creating virtual Python environments for them. It solves the “Project X depends on version 1.x but, Project Y needs 4.x” dilemma, and keeps your global site-packages directory clean and manageable. For example, you can work on a project which requires Django 1.3 while also maintaining a project which requires Django 1.0.</summary>
    </entry>
</feed>
