Feature request: custom merge logic or variables
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
Línea de trabajo
Start with the dotenv methods that accept the existing override parameter and trace how values from .env are applied to the environment. Define how a variable-to-callable API would coexist with current override and non-override behavior, using the LD_LIBRARY_PATH example as the target case. Done means custom merge logic can extend and normalize a colon-separated value without changing existing defaults.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Hello, this is a feature request for enabling custom merge logic when the environment variables are updated with values read from .env file.
My use case is that I would like to append an element to a colon-separated list of paths. Typical colon-separated environment variables are PATH or LD_LIBRARY_PATH. So the reading of the .env file should neither override, nor leave the original environment variables, instead it should extend the list.
Currently I use the following pseudo-code for this:
cfg = dotenv_values()
path_elems = []
if 'LD_LIBRARY_PATH' in os.environ:
path_elems.extend(os.environ['LD_LIBRARY_PATH'].split(':'))
if 'LD_LIBRARY_PATH' in cfg:
path_elems.append(cfg['LD_LIBRARY_PATH'])
path_elems = list(OrderedDict.fromkeys(path_elems)) # remove duplicates
path = ':'.join(path_elems)
path = path.replace('::', ':') # remove empty elements
os.environ['LD_LIBRARY_PATH'] = path
I think such logic could be integrated into the dotenv library. This would require changing the API: instead of / apart the override parameter the dotenv methods could take a variable name -> callable dictionary, where the callable would take as parameters the current and the new value and handle the merge logic for the specified variable. Senseful default behavior could be configured to simulate the current override/not override functionality.
- Lenguaje dominante
- Python
- Estrellas
- 8.9k
- Forks
- 581
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de theskumar/python-dotenv
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
theskumar/python-dotenv#699 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 35/100
theskumar/python-dotenv#697 ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 28/100
theskumar/python-dotenv#693 · 1 comentario ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
theskumar/python-dotenv#683 · 4 comentarios ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
theskumar/python-dotenv#644 · 2 comentarios ·
Todos los issues de theskumar/python-dotenv
Issues similares
-
area/auth bug comp/agent P3 platform/discord type/security
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
NousResearch/hermes-agent#117848 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
bancolombia/sentinel#23 ·
-
test md AbiertoCI
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100