Difference between two similar commands to activate a Python venvHow can I Open Multiple Customized Terminal...
Can a dragon be stuck looking like a human?
Find x angle in triangle
Why would the Pakistan airspace closure cancel flights not headed to Pakistan itself?
Dilemma of explaining to interviewer that he is the reason for declining second interview
Why Normality assumption in linear regression
How can animals be objects of ethics without being subjects as well?
Quenching swords in dragon blood; why?
Guns against regular people
Isn't using the Extrusion Multiplier like cheating?
Typing Amharic inside a math equation?
If I sold a PS4 game I owned the disc for, can I reinstall it digitally?
"Free" Hopf algebra
Can I write a book of my D&D game?
Why did other German political parties disband so fast when Hitler was appointed chancellor?
What is the purpose of easy combat scenarios that don't need resource expenditure?
What kind of hardware implements Fourier transform?
Word or phrase for showing great skill at something without formal training in it
It took me a lot of time to make this, pls like. (YouTube Comments #1)
Why exactly do action photographers need high fps burst cameras?
Why don't American passenger airlines operate dedicated cargo flights any more?
Why is working on the same position for more than 15 years not a red flag?
What is this metal M-shaped device for?
How to acknowledge an embarrassing job interview, now that I work directly with the interviewer?
What makes the Forgotten Realms "forgotten"?
Difference between two similar commands to activate a Python venv
How can I Open Multiple Customized Terminal Shells?Bash Script that will start up second Terminal process?Run AppleScript from bash scriptIn iTerm, why is a command shell's command not picking up things on my $PATH?Problem running rst2html from command lineUpgraded to Yosemite, mkdir now says “permission denied”Using python screws up the shell (and/or terminal?)!Calling Python 3 script from AppleScriptAutomator: “Run Shell Script” throws error because of missing “on” commandMacports: switching back to the system default version of Python
I have a script that I run as part of my development (it's the activation script for a Python venv environment). The way the documentation suggests that we run it is by going to the folder containing our venv
folder and running . venv/bin/activate
. This works properly (second command in my example).
However, what I would have expected to run is ./venv/bin/activate
, i.e. providing a relative path to the activate script (first command in my example). This doesn't work at all (although I am not surprised because the activate file doesn't have "execute" permissions attached to it).
My-MBP:flask-tutorial stephendewey$ ./venv/bin/activate
-bash: ./venv/bin/activate: Permission denied
My-MBP:flask-tutorial stephendewey$ . venv/bin/activate
(venv) My-MBP:flask-tutorial stephendewey$
So my question is, what is the command that works (. venv/bin/activate
) actually doing? I've never seen syntax like that before.
terminal command-line bash python
add a comment |
I have a script that I run as part of my development (it's the activation script for a Python venv environment). The way the documentation suggests that we run it is by going to the folder containing our venv
folder and running . venv/bin/activate
. This works properly (second command in my example).
However, what I would have expected to run is ./venv/bin/activate
, i.e. providing a relative path to the activate script (first command in my example). This doesn't work at all (although I am not surprised because the activate file doesn't have "execute" permissions attached to it).
My-MBP:flask-tutorial stephendewey$ ./venv/bin/activate
-bash: ./venv/bin/activate: Permission denied
My-MBP:flask-tutorial stephendewey$ . venv/bin/activate
(venv) My-MBP:flask-tutorial stephendewey$
So my question is, what is the command that works (. venv/bin/activate
) actually doing? I've never seen syntax like that before.
terminal command-line bash python
add a comment |
I have a script that I run as part of my development (it's the activation script for a Python venv environment). The way the documentation suggests that we run it is by going to the folder containing our venv
folder and running . venv/bin/activate
. This works properly (second command in my example).
However, what I would have expected to run is ./venv/bin/activate
, i.e. providing a relative path to the activate script (first command in my example). This doesn't work at all (although I am not surprised because the activate file doesn't have "execute" permissions attached to it).
My-MBP:flask-tutorial stephendewey$ ./venv/bin/activate
-bash: ./venv/bin/activate: Permission denied
My-MBP:flask-tutorial stephendewey$ . venv/bin/activate
(venv) My-MBP:flask-tutorial stephendewey$
So my question is, what is the command that works (. venv/bin/activate
) actually doing? I've never seen syntax like that before.
terminal command-line bash python
I have a script that I run as part of my development (it's the activation script for a Python venv environment). The way the documentation suggests that we run it is by going to the folder containing our venv
folder and running . venv/bin/activate
. This works properly (second command in my example).
However, what I would have expected to run is ./venv/bin/activate
, i.e. providing a relative path to the activate script (first command in my example). This doesn't work at all (although I am not surprised because the activate file doesn't have "execute" permissions attached to it).
My-MBP:flask-tutorial stephendewey$ ./venv/bin/activate
-bash: ./venv/bin/activate: Permission denied
My-MBP:flask-tutorial stephendewey$ . venv/bin/activate
(venv) My-MBP:flask-tutorial stephendewey$
So my question is, what is the command that works (. venv/bin/activate
) actually doing? I've never seen syntax like that before.
terminal command-line bash python
terminal command-line bash python
edited 6 mins ago
200_success
4381415
4381415
asked 2 hours ago
StephenStephen
292315
292315
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The . command is an alias for source so the two commands are really
./venv/bin/activate
and
source venv/bin/activate
Also note that for the system to actually process a file it needs the absolute path ie one beginning with /
Both files names here are relative ones ie ones that can only be understood with the knowledge of the current directory which is the variable $(CWD)
The two file names expand to $(CWD)/./venv/bin/activate and $(CWD)/venv/bin/activate . is the current directory and so both are $(CWD)/venv/bin/activate
The difference between running a command directly or via source is that if run directly as in the first command bash creates a new sub shell and runs the command in that and the commands in the script only affect that sub shell and when the script rends that sub shell is closed and all the changes to environment are lost. source, however, runs the command in the current shell and any changes to the environment remain after the script finishes as if the commands in the script were typed into the current shell.
The activate script (I assume is from Python virtual environment management) works by changing the $PATH so that the correct python environment is found when you use python script.py
To do this you need to alter your current $PATH and so the activate script needs to be run using source.
Also see https://askubuntu.com/questions/182012/is-there-a-difference-between-and-source-in-bash-after-all and https://superuser.com/questions/176783/what-is-the-difference-between-executing-a-bash-script-vs-sourcing-it
Not that running a command requires the command to be executable. The command to be run is always a file and that file has to be marked as executable by the system. That is the executable flag has to be set on the file permissions which you can see by ls -l venv/bin/activate
source however is in the current shell and just reads the file as text and then executes the commands it sees, So this file only needs to be readable. For more on that see https://unix.stackexchange.com/questions/291404/why-does-bashs-source-not-need-the-execution-bit I like this answer
It's more of a convenience thing: Let the system run it for me directly if the the bit is set, otherwise I need to do it indirectly
1
Thanks, this answers almost all my questions. But why would the "direct command" run into a permissions issue while the "source command" doesn't?
– Stephen
1 hour ago
@Stephen When you do a long listing, does the file lack the execute permission?ls -l venv/bin/activate
portion of the answer? That would explain the permission error when you try to execute the file directly as opposed to letting the shell read the file for contents. Unix permissions come from a model established quite a while back, so they sometimes are confusing why you could read a file as opposed to execute it as a "binary" or "app" +1 to the asker and answerer here - great question that lets Mark explain why it happens as well as what to do.
– bmike♦
52 mins ago
Thanks all, I think the edit to the answer answers my remaining question (the execute bit was indeed turned off, but I don't need to change that since I can justsource
it).
– Stephen
14 mins ago
add a comment |
From man bash
:
. filename [arguments]
source filename [arguments]
Read and execute commands from filename in the current shell environment and
return the exit status of the last command executed from filename. If filename
does not contain a slash, filenames in PATH are used to find the directory
containing filename. The file searched for in PATH need not be executable.
So basically source
runs the code within the script/file as part of the current shell environment (which is different from executing it, which runs it in a separate shell). This is mainly used to set environment variables, aliases etc to be used in the current shell.
Thanks, I think the last part of the bash manual entry answers the part of my question about permissions:source
doesn't even require something to be executable.
– Stephen
1 hour ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "118"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f352774%2fdifference-between-two-similar-commands-to-activate-a-python-venv%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The . command is an alias for source so the two commands are really
./venv/bin/activate
and
source venv/bin/activate
Also note that for the system to actually process a file it needs the absolute path ie one beginning with /
Both files names here are relative ones ie ones that can only be understood with the knowledge of the current directory which is the variable $(CWD)
The two file names expand to $(CWD)/./venv/bin/activate and $(CWD)/venv/bin/activate . is the current directory and so both are $(CWD)/venv/bin/activate
The difference between running a command directly or via source is that if run directly as in the first command bash creates a new sub shell and runs the command in that and the commands in the script only affect that sub shell and when the script rends that sub shell is closed and all the changes to environment are lost. source, however, runs the command in the current shell and any changes to the environment remain after the script finishes as if the commands in the script were typed into the current shell.
The activate script (I assume is from Python virtual environment management) works by changing the $PATH so that the correct python environment is found when you use python script.py
To do this you need to alter your current $PATH and so the activate script needs to be run using source.
Also see https://askubuntu.com/questions/182012/is-there-a-difference-between-and-source-in-bash-after-all and https://superuser.com/questions/176783/what-is-the-difference-between-executing-a-bash-script-vs-sourcing-it
Not that running a command requires the command to be executable. The command to be run is always a file and that file has to be marked as executable by the system. That is the executable flag has to be set on the file permissions which you can see by ls -l venv/bin/activate
source however is in the current shell and just reads the file as text and then executes the commands it sees, So this file only needs to be readable. For more on that see https://unix.stackexchange.com/questions/291404/why-does-bashs-source-not-need-the-execution-bit I like this answer
It's more of a convenience thing: Let the system run it for me directly if the the bit is set, otherwise I need to do it indirectly
1
Thanks, this answers almost all my questions. But why would the "direct command" run into a permissions issue while the "source command" doesn't?
– Stephen
1 hour ago
@Stephen When you do a long listing, does the file lack the execute permission?ls -l venv/bin/activate
portion of the answer? That would explain the permission error when you try to execute the file directly as opposed to letting the shell read the file for contents. Unix permissions come from a model established quite a while back, so they sometimes are confusing why you could read a file as opposed to execute it as a "binary" or "app" +1 to the asker and answerer here - great question that lets Mark explain why it happens as well as what to do.
– bmike♦
52 mins ago
Thanks all, I think the edit to the answer answers my remaining question (the execute bit was indeed turned off, but I don't need to change that since I can justsource
it).
– Stephen
14 mins ago
add a comment |
The . command is an alias for source so the two commands are really
./venv/bin/activate
and
source venv/bin/activate
Also note that for the system to actually process a file it needs the absolute path ie one beginning with /
Both files names here are relative ones ie ones that can only be understood with the knowledge of the current directory which is the variable $(CWD)
The two file names expand to $(CWD)/./venv/bin/activate and $(CWD)/venv/bin/activate . is the current directory and so both are $(CWD)/venv/bin/activate
The difference between running a command directly or via source is that if run directly as in the first command bash creates a new sub shell and runs the command in that and the commands in the script only affect that sub shell and when the script rends that sub shell is closed and all the changes to environment are lost. source, however, runs the command in the current shell and any changes to the environment remain after the script finishes as if the commands in the script were typed into the current shell.
The activate script (I assume is from Python virtual environment management) works by changing the $PATH so that the correct python environment is found when you use python script.py
To do this you need to alter your current $PATH and so the activate script needs to be run using source.
Also see https://askubuntu.com/questions/182012/is-there-a-difference-between-and-source-in-bash-after-all and https://superuser.com/questions/176783/what-is-the-difference-between-executing-a-bash-script-vs-sourcing-it
Not that running a command requires the command to be executable. The command to be run is always a file and that file has to be marked as executable by the system. That is the executable flag has to be set on the file permissions which you can see by ls -l venv/bin/activate
source however is in the current shell and just reads the file as text and then executes the commands it sees, So this file only needs to be readable. For more on that see https://unix.stackexchange.com/questions/291404/why-does-bashs-source-not-need-the-execution-bit I like this answer
It's more of a convenience thing: Let the system run it for me directly if the the bit is set, otherwise I need to do it indirectly
1
Thanks, this answers almost all my questions. But why would the "direct command" run into a permissions issue while the "source command" doesn't?
– Stephen
1 hour ago
@Stephen When you do a long listing, does the file lack the execute permission?ls -l venv/bin/activate
portion of the answer? That would explain the permission error when you try to execute the file directly as opposed to letting the shell read the file for contents. Unix permissions come from a model established quite a while back, so they sometimes are confusing why you could read a file as opposed to execute it as a "binary" or "app" +1 to the asker and answerer here - great question that lets Mark explain why it happens as well as what to do.
– bmike♦
52 mins ago
Thanks all, I think the edit to the answer answers my remaining question (the execute bit was indeed turned off, but I don't need to change that since I can justsource
it).
– Stephen
14 mins ago
add a comment |
The . command is an alias for source so the two commands are really
./venv/bin/activate
and
source venv/bin/activate
Also note that for the system to actually process a file it needs the absolute path ie one beginning with /
Both files names here are relative ones ie ones that can only be understood with the knowledge of the current directory which is the variable $(CWD)
The two file names expand to $(CWD)/./venv/bin/activate and $(CWD)/venv/bin/activate . is the current directory and so both are $(CWD)/venv/bin/activate
The difference between running a command directly or via source is that if run directly as in the first command bash creates a new sub shell and runs the command in that and the commands in the script only affect that sub shell and when the script rends that sub shell is closed and all the changes to environment are lost. source, however, runs the command in the current shell and any changes to the environment remain after the script finishes as if the commands in the script were typed into the current shell.
The activate script (I assume is from Python virtual environment management) works by changing the $PATH so that the correct python environment is found when you use python script.py
To do this you need to alter your current $PATH and so the activate script needs to be run using source.
Also see https://askubuntu.com/questions/182012/is-there-a-difference-between-and-source-in-bash-after-all and https://superuser.com/questions/176783/what-is-the-difference-between-executing-a-bash-script-vs-sourcing-it
Not that running a command requires the command to be executable. The command to be run is always a file and that file has to be marked as executable by the system. That is the executable flag has to be set on the file permissions which you can see by ls -l venv/bin/activate
source however is in the current shell and just reads the file as text and then executes the commands it sees, So this file only needs to be readable. For more on that see https://unix.stackexchange.com/questions/291404/why-does-bashs-source-not-need-the-execution-bit I like this answer
It's more of a convenience thing: Let the system run it for me directly if the the bit is set, otherwise I need to do it indirectly
The . command is an alias for source so the two commands are really
./venv/bin/activate
and
source venv/bin/activate
Also note that for the system to actually process a file it needs the absolute path ie one beginning with /
Both files names here are relative ones ie ones that can only be understood with the knowledge of the current directory which is the variable $(CWD)
The two file names expand to $(CWD)/./venv/bin/activate and $(CWD)/venv/bin/activate . is the current directory and so both are $(CWD)/venv/bin/activate
The difference between running a command directly or via source is that if run directly as in the first command bash creates a new sub shell and runs the command in that and the commands in the script only affect that sub shell and when the script rends that sub shell is closed and all the changes to environment are lost. source, however, runs the command in the current shell and any changes to the environment remain after the script finishes as if the commands in the script were typed into the current shell.
The activate script (I assume is from Python virtual environment management) works by changing the $PATH so that the correct python environment is found when you use python script.py
To do this you need to alter your current $PATH and so the activate script needs to be run using source.
Also see https://askubuntu.com/questions/182012/is-there-a-difference-between-and-source-in-bash-after-all and https://superuser.com/questions/176783/what-is-the-difference-between-executing-a-bash-script-vs-sourcing-it
Not that running a command requires the command to be executable. The command to be run is always a file and that file has to be marked as executable by the system. That is the executable flag has to be set on the file permissions which you can see by ls -l venv/bin/activate
source however is in the current shell and just reads the file as text and then executes the commands it sees, So this file only needs to be readable. For more on that see https://unix.stackexchange.com/questions/291404/why-does-bashs-source-not-need-the-execution-bit I like this answer
It's more of a convenience thing: Let the system run it for me directly if the the bit is set, otherwise I need to do it indirectly
edited 1 hour ago
answered 2 hours ago
MarkMark
19.9k115795
19.9k115795
1
Thanks, this answers almost all my questions. But why would the "direct command" run into a permissions issue while the "source command" doesn't?
– Stephen
1 hour ago
@Stephen When you do a long listing, does the file lack the execute permission?ls -l venv/bin/activate
portion of the answer? That would explain the permission error when you try to execute the file directly as opposed to letting the shell read the file for contents. Unix permissions come from a model established quite a while back, so they sometimes are confusing why you could read a file as opposed to execute it as a "binary" or "app" +1 to the asker and answerer here - great question that lets Mark explain why it happens as well as what to do.
– bmike♦
52 mins ago
Thanks all, I think the edit to the answer answers my remaining question (the execute bit was indeed turned off, but I don't need to change that since I can justsource
it).
– Stephen
14 mins ago
add a comment |
1
Thanks, this answers almost all my questions. But why would the "direct command" run into a permissions issue while the "source command" doesn't?
– Stephen
1 hour ago
@Stephen When you do a long listing, does the file lack the execute permission?ls -l venv/bin/activate
portion of the answer? That would explain the permission error when you try to execute the file directly as opposed to letting the shell read the file for contents. Unix permissions come from a model established quite a while back, so they sometimes are confusing why you could read a file as opposed to execute it as a "binary" or "app" +1 to the asker and answerer here - great question that lets Mark explain why it happens as well as what to do.
– bmike♦
52 mins ago
Thanks all, I think the edit to the answer answers my remaining question (the execute bit was indeed turned off, but I don't need to change that since I can justsource
it).
– Stephen
14 mins ago
1
1
Thanks, this answers almost all my questions. But why would the "direct command" run into a permissions issue while the "source command" doesn't?
– Stephen
1 hour ago
Thanks, this answers almost all my questions. But why would the "direct command" run into a permissions issue while the "source command" doesn't?
– Stephen
1 hour ago
@Stephen When you do a long listing, does the file lack the execute permission?
ls -l venv/bin/activate
portion of the answer? That would explain the permission error when you try to execute the file directly as opposed to letting the shell read the file for contents. Unix permissions come from a model established quite a while back, so they sometimes are confusing why you could read a file as opposed to execute it as a "binary" or "app" +1 to the asker and answerer here - great question that lets Mark explain why it happens as well as what to do.– bmike♦
52 mins ago
@Stephen When you do a long listing, does the file lack the execute permission?
ls -l venv/bin/activate
portion of the answer? That would explain the permission error when you try to execute the file directly as opposed to letting the shell read the file for contents. Unix permissions come from a model established quite a while back, so they sometimes are confusing why you could read a file as opposed to execute it as a "binary" or "app" +1 to the asker and answerer here - great question that lets Mark explain why it happens as well as what to do.– bmike♦
52 mins ago
Thanks all, I think the edit to the answer answers my remaining question (the execute bit was indeed turned off, but I don't need to change that since I can just
source
it).– Stephen
14 mins ago
Thanks all, I think the edit to the answer answers my remaining question (the execute bit was indeed turned off, but I don't need to change that since I can just
source
it).– Stephen
14 mins ago
add a comment |
From man bash
:
. filename [arguments]
source filename [arguments]
Read and execute commands from filename in the current shell environment and
return the exit status of the last command executed from filename. If filename
does not contain a slash, filenames in PATH are used to find the directory
containing filename. The file searched for in PATH need not be executable.
So basically source
runs the code within the script/file as part of the current shell environment (which is different from executing it, which runs it in a separate shell). This is mainly used to set environment variables, aliases etc to be used in the current shell.
Thanks, I think the last part of the bash manual entry answers the part of my question about permissions:source
doesn't even require something to be executable.
– Stephen
1 hour ago
add a comment |
From man bash
:
. filename [arguments]
source filename [arguments]
Read and execute commands from filename in the current shell environment and
return the exit status of the last command executed from filename. If filename
does not contain a slash, filenames in PATH are used to find the directory
containing filename. The file searched for in PATH need not be executable.
So basically source
runs the code within the script/file as part of the current shell environment (which is different from executing it, which runs it in a separate shell). This is mainly used to set environment variables, aliases etc to be used in the current shell.
Thanks, I think the last part of the bash manual entry answers the part of my question about permissions:source
doesn't even require something to be executable.
– Stephen
1 hour ago
add a comment |
From man bash
:
. filename [arguments]
source filename [arguments]
Read and execute commands from filename in the current shell environment and
return the exit status of the last command executed from filename. If filename
does not contain a slash, filenames in PATH are used to find the directory
containing filename. The file searched for in PATH need not be executable.
So basically source
runs the code within the script/file as part of the current shell environment (which is different from executing it, which runs it in a separate shell). This is mainly used to set environment variables, aliases etc to be used in the current shell.
From man bash
:
. filename [arguments]
source filename [arguments]
Read and execute commands from filename in the current shell environment and
return the exit status of the last command executed from filename. If filename
does not contain a slash, filenames in PATH are used to find the directory
containing filename. The file searched for in PATH need not be executable.
So basically source
runs the code within the script/file as part of the current shell environment (which is different from executing it, which runs it in a separate shell). This is mainly used to set environment variables, aliases etc to be used in the current shell.
answered 2 hours ago
nohillside♦nohillside
52.3k13111154
52.3k13111154
Thanks, I think the last part of the bash manual entry answers the part of my question about permissions:source
doesn't even require something to be executable.
– Stephen
1 hour ago
add a comment |
Thanks, I think the last part of the bash manual entry answers the part of my question about permissions:source
doesn't even require something to be executable.
– Stephen
1 hour ago
Thanks, I think the last part of the bash manual entry answers the part of my question about permissions:
source
doesn't even require something to be executable.– Stephen
1 hour ago
Thanks, I think the last part of the bash manual entry answers the part of my question about permissions:
source
doesn't even require something to be executable.– Stephen
1 hour ago
add a comment |
Thanks for contributing an answer to Ask Different!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f352774%2fdifference-between-two-similar-commands-to-activate-a-python-venv%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown