#
# setup.python.sh: Install a specific Python version and packages for it.
# Usage: setup.python.sh <pyversion> <requirements.txt>
set -xe

source ~/.bashrc
VERSION=$1
REQUIREMENTS=$2

# Install Python packages for this container's version
if [[ ${VERSION} == "python3.13-nogil" || ${VERSION} == "python3.14-nogil" ]]; then
  cat >pythons.txt <<EOF
$VERSION
EOF

To declare those types and the internal types, you can use the standard Python module `typing`. It exists specifically to support these type hints.

#### Newer versions of Python { #newer-versions-of-python }

The syntax using `typing` is **compatible** with all versions, from Python 3.6 to the latest ones, including Python 3.9, Python 3.10, etc.

//// tab | Python 3.10+

```Python hl_lines="1"
{!> ../../docs_src/python_types/tutorial009_py310.py!}
```

////

//// tab | Python 3.8+

```Python hl_lines="1  4"
{!> ../../docs_src/python_types/tutorial009.py!}
```

////

//// tab | Python 3.8+ جایگزین

```Python hl_lines="1  4"
{!> ../../docs_src/python_types/tutorial009b.py!}

    wget https://www.python.org/ftp/python/3.14.0/Python-3.14.0rc1.tar.xz
    tar -xf Python-3.14.0rc1.tar.xz
  fi
  pushd Python-3.14.0rc1
  mkdir -p /python314-0rc1-nogil
  CC=clang-18 CXX=clang++-18 ./configure --prefix /python314-0rc1-nogil --disable-gil --with-ensurepip=install
  make -j$(nproc)
  make install -j$(nproc)
  ln -s /python314-0rc1-nogil/bin/python3 /usr/bin/python3.14-nogil
  popd
else

# Setup Python
COPY setup.python.sh /setup.python.sh
COPY builder.requirements.txt /builder.requirements.txt
RUN /setup.python.sh python3.9 /builder.requirements.txt
RUN /setup.python.sh python3.10 /builder.requirements.txt
RUN /setup.python.sh python3.11 /builder.requirements.txt
RUN /setup.python.sh python3.13 /builder.requirements.txt
RUN /setup.python.sh python3.13-nogil /builder.requirements.txt

RUN /setup.python.sh python3.9 requirements.txt
RUN /setup.python.sh python3.10 requirements.txt
RUN /setup.python.sh python3.11 requirements.txt
RUN /setup.python.sh python3.12 requirements.txt
RUN /setup.python.sh python3.13 requirements.txt
# python3.13-nogil is a free-threaded build of python3.13.
RUN /setup.python.sh python3.13-nogil requirements.txt
RUN /setup.python.sh python3.14 requirements.txt

```

</div>

////

## Read env vars in Python { #read-env-vars-in-python }

You could also create environment variables **outside** of Python, in the terminal (or with any other method), and then **read them in Python**.

For example you could have a file `main.py` with:

```Python hl_lines="3"
import os

name = os.getenv("MY_NAME", "World")
print(f"Hello {name} from Python")
```

/// tip

```console
// اینجا هنوز متغیر محیطی رو تنظیم نکردیم
$ python main.py

// چون متغیر محیطی رو تنظیم نکردیم، مقدار پیش‌فرض رو می‌گیریم

Hello World from Python

// ولی اگه اول یه متغیر محیطی بسازیم
$ export MY_NAME="Wade Wilson"

// و بعد دوباره برنامه رو صدا کنیم
$ python main.py

// حالا می‌تونه متغیر محیطی رو بخونه

Hello Wade Wilson from Python
```

</div>

////

```
.
├── app                  # "app" is a Python package
│   ├── __init__.py      # this file makes "app" a "Python package"
│   ├── main.py          # "main" module, e.g. import app.main
│   ├── dependencies.py  # "dependencies" module, e.g. import app.dependencies
│   └── routers          # "routers" is a "Python subpackage"
│   │   ├── __init__.py  # makes "routers" a "Python subpackage"

The key factor is that a dependency should be a "callable".

A "**callable**" in Python is anything that Python can "call" like a function.

So, if you have an object `something` (that might _not_ be a function) and you can "call" it (execute it) like:

```Python
something()
```

or

```Python
something(some_argument, some_keyword_argument="foo")
```

then it is a "callable".