Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Appium-Python-Client library install failed : No module named 'appium'

Aberta
  • Algo errado?
#839 5 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
25/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Estagnada
Stack de tecnologia
python
Domínio
mobile-dev, testing-qa

Direção de pesquisa

Comece reproduzindo pip install Appium-Python-Client para a versão 2.8.1 com Python 3.11.2, pip 23.0.1 e setuptools 67.4.0. Leia setup.py na linha 19 e o appium.common.helper import referenciado; considera-se concluído quando a geração dos metadados do pacote e a instalação forem concluídas sem ModuleNotFoundError.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Hello,

I have following issue when trying to install appium library :

pip install Appium-Python-Client
Looking in indexes: http://nexus-proxy.groupe.generali.fr/python/repository/pypi-all/simple
Collecting Appium-Python-Client
Using cached http://nexus-proxy.groupe.generali.fr/python/repository/pypi-all/packages/appium-python-client/2.8.1/Appium-Python-Client-2.8.1.tar.gz (3.4 MB)
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error

× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [6 lines of output]
Traceback (most recent call last):
File "", line 2, in
File "", line 34, in
File "C:\Users\b300tvz\AppData\Local\Temp\pip-install-vifhpcuq\appium-python-client_75e9b86948b6479f8c84397cf0f73693\setup.py", line 19, in
from appium.common.helper import library_version
ModuleNotFoundError: No module named 'appium'
[end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

Here is my configuration of python, appium and installed libraries :

pip list
Package Version

async-generator 1.10
attrs 22.2.0
certifi 2022.12.7
cffi 1.15.1
docutils 0.19
h11 0.14.0
idna 3.4
outcome 1.2.0
pip 23.0.1
pycparser 2.21
PySocks 1.7.1
robotframework 6.0.2
robotframework-pythonlibcore 4.1.2
robotframework-seleniumlibrary 6.0.0
selenium 4.8.2
setuptools 67.4.0
sniffio 1.3.0
sortedcontainers 2.4.0
trio 0.22.0
trio-websocket 0.9.2
urllib3 1.26.14
wheel 0.38.4
wsproto 1.2.0

python --version
Python 3.11.2

appium --version
1.22.3

appium-doctor
WARN AppiumDoctor [Deprecated] Please use appium-doctor installed with "npm install @appium/doctor --location=global"
info AppiumDoctor Appium Doctor v.1.16.2
info AppiumDoctor ### Diagnostic for necessary dependencies starting ###
info AppiumDoctor ✔ The Node.js binary was found at: C:\JTB\nodejs\node.EXE
info AppiumDoctor ✔ Node version is 18.14.0
info AppiumDoctor ✔ ANDROID_HOME is set to: C:\Users\b300tvz\AppData\Local\Android\Sdk
info AppiumDoctor ✔ JAVA_HOME is set to: C:\JTB\jdk\jdk11.0.9_11
info AppiumDoctor 'adb' is in C:\Users\b300tvz\AppData\Local\Android\Sdk\platform-tools\adb.exe
info AppiumDoctor 'android' is in C:\Users\b300tvz\AppData\Local\Android\Sdk\tools\android.bat
info AppiumDoctor 'emulator' is in C:\Users\b300tvz\AppData\Local\Android\Sdk\emulator\emulator.exe
info AppiumDoctor 'apkanalyzer.bat' is in C:\Users\b300tvz\AppData\Local\Android\Sdk\cmdline-tools\latest\bin\apkanalyzer.bat
info AppiumDoctor ✔ adb, android, emulator, apkanalyzer.bat exist: C:\Users\b300tvz\AppData\Local\Android\Sdk
info AppiumDoctor ✔ 'bin' subfolder exists under 'C:\JTB\jdk\jdk11.0.9_11'
info AppiumDoctor ### Diagnostic for necessary dependencies completed, no fix needed. ###
info AppiumDoctor
info AppiumDoctor ### Diagnostic for optional dependencies starting ###
WARN AppiumDoctor ✖ opencv4nodejs cannot be found.
WARN AppiumDoctor ✖ ffmpeg cannot be found
WARN AppiumDoctor ✖ mjpeg-consumer cannot be found.
WARN AppiumDoctor ✖ bundletool.jar cannot be found
WARN AppiumDoctor ✖ gst-launch-1.0.exe and/or gst-inspect-1.0.exe cannot be found
info AppiumDoctor ### Diagnostic for optional dependencies completed, 5 fixes possible. ###
info AppiumDoctor
info AppiumDoctor ### Optional Manual Fixes ###
info AppiumDoctor The configuration can install optionally. Please do the following manually:
WARN AppiumDoctor ➜ Why opencv4nodejs is needed and how to install it: http://appium.io/docs/en/writing-running-appium/image-comparison/
WARN AppiumDoctor ➜ ffmpeg is needed to record screen features. Please read https://www.ffmpeg.org/ to install it
WARN AppiumDoctor ➜ mjpeg-consumer module is required to use MJPEG-over-HTTP features. Please install it with 'npm i -g mjpeg-consumer'.
WARN AppiumDoctor ➜ bundletool.jar is used to handle Android App Bundle. Please read http://appium.io/docs/en/writing-running-appium/android/android-appbundle/ to install it. Also consider adding the ".jar" extension into your PATH
EXT environment variable in order to fix the problem for Windows
WARN AppiumDoctor ➜ gst-launch-1.0.exe and gst-inspect-1.0.exe are used to stream the screen of the device under test. Please read https://appium.io/docs/en/writing-running-appium/android/android-screen-streaming/ to install them a
nd for more details
info AppiumDoctor
info AppiumDoctor ###
info AppiumDoctor
info AppiumDoctor Bye! Run appium-doctor again when all manual fixes have been applied!
info AppiumDoctor

Have you an idea to fix this issue ?
Thanks for your response

Linguagem predominante
Python
Estrelas
1.8k
Forks
570
Merge médio
1d 9h
PRs com merge (30d)
25

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de appium/python-client

Todas as issues de appium/python-client

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.