User specified Python environment is not prioritized in Python Path

Aperta
#4,093 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
38/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
python
Ambito
devtools

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
C++
Stelle
1.3k
Fork
298
Merge medio
5g 5h
PR unite (30g)
19

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Vector35/binaryninja-api

Tutte le issue di Vector35/binaryninja-api

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.