Log file Viewer

[00:00:45] <herrwolfe45> it seems like this could be done by creating a temporary setup.cfg file that could be used as well

[17:19:08] <stbatduke> Hello #pypa !!

[17:20:32] <stbatduke> I am new to python, and in my new position I am trying to utilize bash scripting to automate the setup and creation new virtualenv and installation of pip packages, etc ...

[17:21:45] <stbatduke> When I setup the bash script traditionally, it seems to spawn a new bash shell, which then brings the environment outside of the python virtualenv, so my question would be: Is there a way to automate this where the script can create and then "enter" the virtualenv and then run pip install commands and python commands within the new python virtualenv ?

[17:23:00] <stbatduke> (I do plan to use python scripts in the future instead of bash scripts, but I need this as a temporary solution sooner than when I will have a full grasp of python etc)

[17:24:26] <dstufft> stbatduke: source the activate script in the virtualenv bin, or explicitly call python and such from the virtualenv bin

[17:26:46] <stbatduke> ok

[17:26:58] <stbatduke> thanks dstufft !

[17:27:02] <stbatduke> so the environment my team uses works with "workon" to activate, I understand this is a script, but I can't find any documentation online about it ...

[17:27:20] <dstufft> workon comes from a secondary package

[17:27:22] <dstufft> virtualenv-wrapper

[17:27:31] <stbatduke> ok gotcha

[17:27:51] <stbatduke> that would be installed in the system python, rather than the virtualenv python, right?

[17:30:10] <dstufft> yea

[17:37:51] <stbatduke> so workon uses an activate script, but I'm not sure how to find the source of the workon script or the activate script

[23:17:57] <buck1> what's the current state of the art for shipping python apps to windows?

[23:18:10] <buck1> pyinstaller?