python pip install calling module by name in terminal
up vote
0
down vote
favorite
I've noticed that for some packages, for example, ipython and termdown, after I've successfully installed them with pip install, they can be immediately invoked from the terminal. e.g:
$ termdown 100
I understand that the primary file within these packages are operated by the #! shebang line and hence callable, however, where in the python directory are the hook that allowed them to become callable stored? e.g. a /bin folder where everything can be invoked from the terminal? Or is there some other mechanism like PATH in play? Thanks!
python shell path pip shebang
asked Nov 11 at 2:01
Rocky Li
2,7821316
add a comment |
up vote
0
down vote
favorite
I've noticed that for some packages, for example, ipython and termdown, after I've successfully installed them with pip install, they can be immediately invoked from the terminal. e.g:
$ termdown 100
I understand that the primary file within these packages are operated by the #! shebang line and hence callable, however, where in the python directory are the hook that allowed them to become callable stored? e.g. a /bin folder where everything can be invoked from the terminal? Or is there some other mechanism like PATH in play? Thanks!
python shell path pip shebang
asked Nov 11 at 2:01
Rocky Li
2,7821316
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I've noticed that for some packages, for example, ipython and termdown, after I've successfully installed them with pip install, they can be immediately invoked from the terminal. e.g:
$ termdown 100
I understand that the primary file within these packages are operated by the #! shebang line and hence callable, however, where in the python directory are the hook that allowed them to become callable stored? e.g. a /bin folder where everything can be invoked from the terminal? Or is there some other mechanism like PATH in play? Thanks!
python shell path pip shebang
asked Nov 11 at 2:01
Rocky Li
2,7821316
I've noticed that for some packages, for example, ipython and termdown, after I've successfully installed them with pip install, they can be immediately invoked from the terminal. e.g:
$ termdown 100
I understand that the primary file within these packages are operated by the #! shebang line and hence callable, however, where in the python directory are the hook that allowed them to become callable stored? e.g. a /bin folder where everything can be invoked from the terminal? Or is there some other mechanism like PATH in play? Thanks!
python shell path pip shebang
python shell path pip shebang
asked Nov 11 at 2:01
Rocky Li
2,7821316
asked Nov 11 at 2:01
Rocky Li
2,7821316
asked Nov 11 at 2:01
Rocky Li
2,7821316
asked Nov 11 at 2:01
Rocky Li
2,7821316
asked Nov 11 at 2:01
Rocky Li
2,7821316
2,7821316
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
Generally when a Python package is installed via pip, setuptools, etc. two mechanisms can be invoked within the packages setup.py file to produce a CLI executable command:
The scripts keyword argument and the console_scripts entry point.
Usually a symlink is created within /usr/local/bin that points back to the installed package.
↳ Python Packaging | Command Line Scripts
answered Nov 11 at 2:45
l'L'l
29.5k54891
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fstackoverflow.com%2fquestions%2f53245214%2fpython-pip-install-calling-module-by-name-in-terminal%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Generally when a Python package is installed via pip, setuptools, etc. two mechanisms can be invoked within the packages setup.py file to produce a CLI executable command:
The scripts keyword argument and the console_scripts entry point.
Usually a symlink is created within /usr/local/bin that points back to the installed package.
↳ Python Packaging | Command Line Scripts
answered Nov 11 at 2:45
l'L'l
29.5k54891
add a comment |
up vote
1
down vote
accepted
Generally when a Python package is installed via pip, setuptools, etc. two mechanisms can be invoked within the packages setup.py file to produce a CLI executable command:
The scripts keyword argument and the console_scripts entry point.
Usually a symlink is created within /usr/local/bin that points back to the installed package.
↳ Python Packaging | Command Line Scripts
answered Nov 11 at 2:45
l'L'l
29.5k54891
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Generally when a Python package is installed via pip, setuptools, etc. two mechanisms can be invoked within the packages setup.py file to produce a CLI executable command:
The scripts keyword argument and the console_scripts entry point.
Usually a symlink is created within /usr/local/bin that points back to the installed package.
↳ Python Packaging | Command Line Scripts
answered Nov 11 at 2:45
l'L'l
29.5k54891
Generally when a Python package is installed via pip, setuptools, etc. two mechanisms can be invoked within the packages setup.py file to produce a CLI executable command:
The scripts keyword argument and the console_scripts entry point.
Usually a symlink is created within /usr/local/bin that points back to the installed package.
↳ Python Packaging | Command Line Scripts
answered Nov 11 at 2:45
l'L'l
29.5k54891
answered Nov 11 at 2:45
l'L'l
29.5k54891
answered Nov 11 at 2:45
l'L'l
29.5k54891
answered Nov 11 at 2:45
l'L'l
29.5k54891
29.5k54891
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2fstackoverflow.com%2fquestions%2f53245214%2fpython-pip-install-calling-module-by-name-in-terminal%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
