User specified Python environment is not prioritized in Python Path

Abierto
#4,093 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
38/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python
Área
devtools

Línea de trabajo

Start by reproducing the configured virtualenv behavior in Binary Ninja's Python interpreter with import sys; sys.path, as described in the issue. Trace the plugin environment setup and verify that the user-selected environment's site-packages appear before Binary Ninja's built-in site-packages when the issue is fixed.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Component: Plugin Effort: Low Impact: Medium

Version and Platform (required):

  • Binary Ninja Version: 3.4.4133
  • OS: Ubuntu
  • OS Version: 22.04
  • CPU Architecture: x64

Bug Description:
When a user manually sets the "virtualenv" of their Binja's plugin, they expect that Python to have priority in package lookup against the builtin Binja Python; however, it is not prioritized.

Steps To Reproduce:

  1. Open Binja and set up your Python to be something like this:
    image
  2. Restart Binja
  3. Go to the Python interpreter in Binja and type import sys; sys.path, this should result in something like:
['/home/mahaloz/.binaryninja/repositories/official/plugins', '/home/mahaloz/.binaryninja/repositories/community/plugins', '/home/mahaloz/.binaryninja/plugins', '/home/mahaloz/.binaryninja/python310/site-packages', ...]

Notice that the last entry in the path is /home/mahaloz/.binaryninja/python310/site-packages, which means when a user has a library installed on the Binja python, that one will always be chosen. Whenever a user sets their Python env manually, it's expected that their packages would be chosen when this happens.

Expected Behavior:
Whenever a user sets their Python env manually, it's expected that their packages would be chosen when this happens. After they do this change, they should see their site packages before Binjas in the Path.

Screenshots:
Show above.

Additional Information:
Linking BinSync issue so both can close when this is fixed: https://github.com/binsync/binsync/issues/241

Lenguaje dominante
C++
Estrellas
1.3k
Forks
298
Merge medio
5 d 5 h
PR fusionados (30 d)
19

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Vector35/binaryninja-api

Todos los issues de Vector35/binaryninja-api

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.