1 # Buildsheet autogenerated by ravenadm tool -- Do not edit.
3 NAMEBASE= python-python-dotenv
7 SDESC[v11]= Sets environment from .env file (3.11)
8 SDESC[v12]= Sets environment from .env file (3.12)
9 HOMEPAGE= https://github.com/theskumar/python-dotenv
10 CONTACT= Python_Automaton[python@ironwolf.systems]
13 SITES[main]= PYPIWHL/6a/3e/b68c118422ec867fa7ab88444e1274aa40681c606d59ac27de5a5588f082
14 DISTFILE[1]= python_dotenv-1.0.1-py3-none-any.whl:main
19 OPTIONS_AVAILABLE= PY311 PY312
20 OPTIONS_STANDARD= none
21 VOPTS[v11]= PY311=ON PY312=OFF
22 VOPTS[v12]= PY311=OFF PY312=ON
24 DISTNAME= python_dotenv-1.0.1.dist-info
28 [PY311].USES_ON= python:v11,wheel
30 [PY312].USES_ON= python:v12,wheel
32 [FILE:2508:descriptions/desc.single]
35 [![Build Status][build_status_badge]][build_status_link]
36 [![PyPI version][pypi_badge]][pypi_link]
38 Python-dotenv reads key-value pairs from a `.env` file and can set them as
40 variables. It helps in the development of applications following the
41 [12-factor] principles.
45 * [Load configuration without altering the environment]
46 * [Parse configuration as a stream]
47 * [Load .env files in IPython]
48 - [Command-line Interface]
51 * [Variable expansion]
58 pip install python-dotenv
61 If your application takes its configuration from environment variables,
63 application, launching it in development is not very practical because you
65 those environment variables yourself.
67 To help you with that, you can add Python-dotenv to your application to
69 configuration from a `.env` file when it is present (e.g. in development)
71 configurable via the environment:
74 from dotenv import load_dotenv
76 load_dotenv() # take environment variables from .env.
78 # Code of your application, which uses environment variables (e.g. from
80 # `os.getenv`) as if they came from the actual environment.
83 By default, `load_dotenv` doesn't override existing environment variables.
85 To configure the development environment, add a `.env` in the root
95 The syntax of `.env` files supported by python-dotenv is similar to that of
99 # Development settings
101 ADMIN_EMAIL=admin@${DOMAIN}
102 ROOT_URL=${DOMAIN}/app
105 If you use variables in values, ensure they are surrounded with `{` and
107 `${DOMAIN}`, as bare variables such as `$DOMAIN` are not expanded.
109 You will probably want to add `.env` to your `.gitignore`, especially if it
111 secrets like a password.
113 See the section "File format" below for more information about what you can
119 ### Load configuration without altering the environment
121 The function `dotenv_values` works more or less the same way as
122 `load_dotenv`, except it
123 doesn't touch the environment, it just returns a `dict` with the values
128 from dotenv import dotenv_values
130 config = dotenv_values(".env") # config = {"USER": "foo", "EMAIL":
136 f7b63ef50f1b690dddf550d03497b66d609393b40b564ed0d674909a68ebf16a 19863 python_dotenv-1.0.1-py3-none-any.whl