“源”的批次等价物在 Windows 上：如何从 virtualenv 运行 Python 脚本

发布于 2024-11-26 00:41:40 字数 441 浏览 1 评论 0原文

我已经编写了相当多的 bash 脚本，但在 Windows 上编写的批处理脚本却很少。我正在尝试激活 Python virtualenv，运行 Python 脚本，然后在脚本退出时停用 virtualenv。

我有一个名为 env 的文件夹，它是我的 virtualenv，还有一个名为 work 的文件夹，其中包含我的脚本。

这是我到目前为止所得到的：

%~dp0env\Scripts\activate.bat
python %~dp0work\script.py
deactivate

但是，当我运行脚本时，它会激活 virtualenv 然后停止。它不会到达第二行并运行 Python 脚本。有没有办法“获取”激活脚本文件夹，以便可以像我从命令行调用 activate.bat 一样运行批处理脚本的其余部分？

原文

I've done a fair bit of bash scripting, but very little batch scripting on Windows. I'm trying to activate a Python virtualenv, run a Python script, then deactivate the virtualenv when the script exits.

I've got a folder called env, which is my virtualenv, and a folder called work, which contains my scripts.

This is what I've got so far:

%~dp0env\Scripts\activate.bat
python %~dp0work\script.py
deactivate

However, when I run the script, it activates the virtualenv then stops. It does not get to the second line and run the Python script. Is there a way to "source" the activate script folder, so that the rest of the batch script can be run as if I'd called activate.bat from the command line?

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

温柔女人霸气范 2024-12-03 00:41:40

我想说，您只需要在 activate.bat 调用前面添加“call”，以确保执行 activate 后恢复当前的批处理文件：

call %~dp0env\Scripts\activate.bat

考虑对 deactivate.bat 执行相同的操作。此外，如果您想确保当前的 cmd.exe 环境不会因调用批处理文件而受到污染，请考虑将命令包装在 setlocal/endlocal 命令对中。

I'd say you just need to prepend 'call' to your activate.bat invocation, to ensure that the current batch file is resumed after activate is executed:

call %~dp0env\Scripts\activate.bat

Consider doing the same for deactivate.bat. Furthermore, if you want to ensure that the current cmd.exe environment is not polluted by a call to your batch file, consider wrapping your commands in a setlocal/endlocal command pair.

回复收藏 0 原文

疧_╮線 2024-12-03 00:41:40

我制作了一个指向 cmd /k "path/to the/script/activate.bat" 的 .lnk 文件，它可以工作。

CMD 参数&选项

回复收藏 0 原文

执笔绘流年 2024-12-03 00:41:40

我想您只想在 Windows 中执行与 Linux Bash/shell 中预期相同的命令。当我想启动 virtualenv 时，我实际上位于其顶级目录中，Linux 命令将是“source bin/activate”。

在Windows上模拟这个行为是没有问题的。就我个人而言，我将一个名为 activate.bat 的批处理文件放在 PATH 环境变量中的某个位置，如下所示：

:: activate.bat
@echo off
REM source bin/activate
if "%1" == "bin/activate" (
    if not EXIST "%CD%\Scripts\activate.bat" goto notfound
    set WRAPEX=Scripts\activate.bat
) ELSE (
       set WRAPEX=%*
)
call %WRAPEX%
goto :eof

:notfound
echo Cannot find the activate script -- aborting.
goto :eof

I suppose you just want to perform the same commands in Windows as if expected in Linux Bash/shell. When I want to start a virtualenv I am actually in its top directory, and the Linux command would be "source bin/activate".

It is no problem to simulate this behaviour on Windows. Me personally, I've put a batch file named activate.bat somewhere on the PATH environment variable like this:

:: activate.bat
@echo off
REM source bin/activate
if "%1" == "bin/activate" (
    if not EXIST "%CD%\Scripts\activate.bat" goto notfound
    set WRAPEX=Scripts\activate.bat
) ELSE (
       set WRAPEX=%*
)
call %WRAPEX%
goto :eof

:notfound
echo Cannot find the activate script -- aborting.
goto :eof

回复收藏 0 原文

~没有更多了~