Skip to content

Clarify the meaning of export - #159

Closed
0mp wants to merge 1 commit into
theskumar:masterfrom
0mp:patch-1
Closed

Clarify the meaning of export#159
0mp wants to merge 1 commit into
theskumar:masterfrom
0mp:patch-1

Conversation

@0mp

@0mp 0mp commented Dec 17, 2018

Copy link
Copy Markdown

The export keyword does not influence the process of sourcing a file.
It only means that the specified variables are going to be passed to
subprocesses.

The `export` keyword does not influence the process of sourcing a file. 
It only means that the specified variables are going to be passed to
subprocesses.
@coveralls

Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 90.244% when pulling cc4f0c8 on 0mp:patch-1 into f9863d3 on theskumar:master.

1 similar comment
@coveralls

Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 90.244% when pulling cc4f0c8 on 0mp:patch-1 into f9863d3 on theskumar:master.

@theskumar

Copy link
Copy Markdown
Owner

I would say that's not true. export is allowed so that the .env file can be used with source command, similar to a shell script.

The export keyword is ignored by python-dotenv library alltogether.

@0mp

0mp commented Dec 18, 2018

Copy link
Copy Markdown
Author

Hi!

export is allowed so that the .env file can be used with source command, similar to a shell script.

However, you do not need to use export in order to load variables with . (or source).

Maybe the documentation should just mention, that the export keyword is accepted and ignored?

@theskumar

Copy link
Copy Markdown
Owner

Maybe the documentation should just mention, that the export keyword is accepted and ignored?

Yeah. that works with me.

@theskumar theskumar closed this in 98e4eee Jan 2, 2019
johnbergvall pushed a commit to johnbergvall/python-dotenv that referenced this pull request Aug 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants