Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support for SOME_VAR=(int, None)? #209

Open
Pomax opened this issue Jan 29, 2019 · 0 comments · Fixed by #332
Open

Support for SOME_VAR=(int, None)? #209

Pomax opened this issue Jan 29, 2019 · 0 comments · Fixed by #332
Assignees
@sergeyklay
Labels
enhancement New feature or request

Comments

@Pomax
Copy link

Pomax commented Jan 29, 2019

Is there a way to tell environ that SOME_VAR= in an env file is fine, and should lead to SOME_VAR being assigned the pythonic None when using the SOME_VAR=(int, None) format?
@claytondaley claytondaley mentioned this issue May 28, 2019
Open
tkdchen pushed a commit to tkdchen/django-environ that referenced this issue Oct 6, 2019
@blueyed
Merge pull request joke2k#209 from blueyed/coverage_enable_subprocess
18dcab0 
tests: use coverage_enable_subprocess instead of sitecustomize.py
@sergeyklay sergeyklay added the enhancement New feature or request label Sep 7, 2021
@mehdy mehdy mentioned this issue Oct 5, 2021
Merged
@sergeyklay sergeyklay self-assigned this Oct 6, 2021
@pataquets pataquets mentioned this issue Apr 30, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sergeyklay sergeyklay

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add support for empty var with None default value mehdy/django-environ
2 participants
@Pomax @sergeyklay