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

Why use 'dotenv' instead of the standard library 'parsecfg' in the project? #186

Closed
lihf8515 opened this issue Feb 4, 2022 · 0 comments · Fixed by #188
Closed

Why use 'dotenv' instead of the standard library 'parsecfg' in the project? #186

lihf8515 opened this issue Feb 4, 2022 · 0 comments · Fixed by #188

Comments

@lihf8515
Copy link

lihf8515 commented Feb 4, 2022

Why use the 'dotenv' module instead of the standard library 'parsecfg' in this project? In this way, there will be less dependence. I suggest using the standard library.
@itsumura-h itsumura-h mentioned this issue Feb 10, 2022
Merged
itsumura-h added a commit that referenced this issue Feb 10, 2022
@itsumura-h
remove dotenv (#188)
bf899e6 
close #186
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

remove dotenv itsumura-h/nim-allographer
1 participant
@lihf8515