![如何在执行自动化测试时将 Python 3.5 测试的路径更改为 2.7?](https://linux22.com/image/1090000/%E5%A6%82%E4%BD%95%E5%9C%A8%E6%89%A7%E8%A1%8C%E8%87%AA%E5%8A%A8%E5%8C%96%E6%B5%8B%E8%AF%95%E6%97%B6%E5%B0%86%20Python%203.5%20%E6%B5%8B%E8%AF%95%E7%9A%84%E8%B7%AF%E5%BE%84%E6%9B%B4%E6%94%B9%E4%B8%BA%202.7%EF%BC%9F.png)
我是新手。背景是我使用 GIT 并可以从远程访问存储库。问题如下:存储库 Python 文件夹使用 2.7 语法。当我通过自动化执行时,我收到此错误(这是 2.7 到 3.5 的问题)
ERROR: Failure: SyntaxError (Missing parentheses in call to
'print' (test_controller.py, line 368))
此错误告诉我这是 Python 语法问题。其余结果如下:
Traceback (most recent call last):
File '/home/myName/.local/lib/python3.5/site-packages/nose/
failure.py', line 39, in runTest
因此基于这个结果,我发现它使用 Python 3.5 语法来检查存储库,但我有权访问的存储库中的 python 文件使用的是 2.7 语法。
那么我该如何更改路径/目录以使用 Python 2.7 语法检查?
更新(1)
which python
给我/usr/bin/python
更新 (2) 如果有帮助的话,这是我的 .bashrc 文件。当然,我仍然会排除故障并彻底检查。
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples
# If not running interactively, don't do anything
case $- in
*i*) ;;
*) return;;
esac
# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth
# append to the history file, don't overwrite it
shopt -s histappend
# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000
# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize
# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar
# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"
# set variable identifying the chroot you work in (used in the prompt
below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi
# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color|*-256color) color_prompt=yes;;
esac
# uncomment for a colored prompt, if the terminal has the capability;
turned
# off by default to not distract the user: the focus in a terminal
window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes
if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi
if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\
[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt
# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
;;
*)
;;
esac
# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" ||
eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'
alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
fi
# colored GCC warnings and errors
#export
GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:
locus=01:quote=01'
export PYTHON_PATH="/home/myname/Automation/pdci_keyword/python"
export PYTHONBASE="/home/myname/Automation/pdci_keyword/python"
export TEST_CONFIG_FILE="/home/myname/Automation/pdci_keyword/python"
# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'
# Add an "alert" alias for long running commands. Use like so:
# sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo
terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-
9]\+\s*//;s/[;&|]\s*alert$//'\'')"'
# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.
if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi
# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
if [ -f /usr/share/bash-completion/bash_completion ]; then
. /usr/share/bash-completion/bash_completion
elif [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi
fi
答案1
您可能需要更改 .bashrc 文件中导出的 PATH 变量(位于您的主目录中)。例如,我的包含:
export PATH="/home/max/anaconda2/bin:$PATH"
因为我使用的是 anaconda 版本的 python。如果你删除这个,它应该会回到内置版本,我认为是 2.7。你能发布你的 .bashrc 文件的内容吗?
编辑:如果您执行以下操作:
which python
在终端中它应该会显示 python 3.5 的位置;在 .bashrc 文件中查找该目录的内容
答案2
更新一下 - 我问过我的项目负责人,但负责人不知道如何修复路径问题。还问过同事,但没有得到明确的帮助。
所以我要做的是:我将使用“2to3”转换器,它允许我将所有 python 存储库文件夹更改为 python 3 语法。没有太多麻烦,试验并确保我有备份存储库文件以防出现问题。
不过,还是要感谢你的回答/评论,我对 linux/python 都还不熟悉,所以这个问题有点难以解决!我会勾选第一个答案,然后解决这个问题。如果出现其他错误,我会创建一个新主题。