Each virtual environment has its own bin/ directory and when activated its
bin/ is in your $PATH

On Tue, Sep 6, 2022 at 1:45 PM <c.buhtz@posteo.jp> wrote:

Hello,

I try to get it onto my head how virtual environments (via venv) works
when I have packages with "entry points".

I can define such entry points in the setup.cfg like this (full example
[1]):

[options.entry_points]
console_scripts =
hyperorg = hyperorg.__main__:main

When I install such a package via pip the result is a shell script in /usr/bin/...

What happens when I install such a package with an entry point via "pip install ." when an virtual environment is activated?

Kind
Christian

[1] --
<https://codeberg.org/buhtz/hyperorg/src/branch/develop/setup.cfg>
--
https://mail.python.org/mailman/listinfo/python-list

--

CALVIN SPEALMAN

SENIOR QUALITY ENGINEER

calvin.spealman@redhat.com M: +1.336.210.5107
[image: https://red.ht/sig] <https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hello,

I try to get it onto my head how virtual environments (via venv) works
when I have packages with "entry points".

I can define such entry points in the setup.cfg like this (full example
[1]):

[options.entry_points]
console_scripts =
hyperorg = hyperorg.__main__:main

When I install such a package via pip the result is a shell script in /usr/bin/...

What happens when I install such a package with an entry point via "pip
install ." when an virtual environment is activated?

Kind
Christian

[1] --
<https://codeberg.org/buhtz/hyperorg/src/branch/develop/setup.cfg>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)