Recherche avancée

Sur d’autres sites (8779)

• Functionallity (supposedly) of shutil.which("ffmpeg") with pyinstaller flag —windowed is use

  8 juin 2021, par vanilla

  I have a github project for my app Scout. I use pyinstaller to compile. I just added a feature that uses ffmpeg, and I use shutil.which() to see if it's installed in order to warn and disable the features using it.

  


  When I run it straight with python3 scout.py, or with virtually any other flags than--windowed, --no-console, it will return None even when I have ffmpeg. Before it returns /usr/bin/ffmpeg.

  


  Those flags make it so the app doesn't have a console in the background, not sure exactly what I can do about this. I have tried using some of these flags to solve the problem but pyinstaller doesn't seem to recognize them.

  


  I have also tried if os.system("ffmpeg -version") != 0:, but the same thing happens, it will return 0 for anything but the windowed version.

  


  Any help ?

  


• Shutil not detecting ffmpeg module and python3 incorrectly, all when compiled with pyinstaller

  9 juin 2021, par vanilla

  Right now I am almost finished with my version of my app. The last thing I am having trouble with is detecting the FFmpeg module, to warn users that they need it for certain features that have been added this version. When I run the script through my python interpreter in terminal, which the directories of it is in my library frameworks directory, The shutil will run as expected and return the version or whatever as I do have it installed. However, when I compile it and launch specifically the one windowed, with no console output, it doesn’t work. Now what I mean by that it returns none type.

  


  From talking to someone in my previous Reddit thread I tried printing out python3 and seeing what directories that would bring with shutil.which(‘python3’). Interesting enough, when put into my tkinter text field (don't have a console) it would bring up my python binary from the directory /usr/bin/python3. The one I have all my modules for it and everything installed on is the one :

  


  >>> import shutil
>>> print(shutil.which('python3'))
/Library/Frameworks/Python.framework/Versions/3.9/bin/python3


  


  So we can see that there are to installations or whatever of python3 interpreters (I believe I am saying this right), and I am confused on maybe I am being hinted to use the python3 binary from /usr/bin/ to compile it with pyinstaller and install the needed modules with /usr/bin/pip3 with it ?

  


  A user from the reddit thread I made below made a alternative :

  


  


  I tested it on my computer after fixing a bug, and both the shutil and os methods work. It seems to be a problem on your end, which is strange. What version of Python do you have ? Also in your script right above testing for ffmpeg, try inserting this line :
print('ffmpeg' in os.listdir('/usr/local/bin'))

  


  


  This other method with os unfortunately returned a None as well. I am ultimately trying to have some kind of method to reliably detect ffmpegs's binary on all operating systems. If anyone can provide some insight as to what may cause problems similar to these or knows other solutions, or can identify some kind of hiccup I can avoid that would be amazing.

  


  I have a hunch since shutil when compiled returned the bin directory for python3 instead of the framework one that actually has all the modules installed, that could mean something to me to try using pyinstaller with that one instead ?

  


  Thanks !

  


  https://www.reddit.com/r/learnpython/comments/nu3a1d/functionallity_supposedly_of_shutilwhichffmpeg/

  


• Anomalie #3017 : Gestion des versions de plugins

  6 juillet 2021

  Il y aurait beaucoup de choses à dire là dessus.
  Personnellement je ne suis pas hyper motivé par la chose car en gros on demande au fil du temps de plus en plus à SVP d’être aussi bon que Composer pour la gestion de versions.
  Ça demanderait à refaire completement la logique de SVP.

  - D’abord à interroger une API externe pour obtenir la liste des plugins / paquets compatibles avec notre version de SPIP (plutôt que de passer par des dépots qui contiennent aussi les paquets pour des versions de SPIP qui ne nous concernent pas). Déjà cette partie est à faire (mais c’est pas le plus dur, vu que Eric a déjà fait une partie de job)
  - Ensuite ça veut dire stocker localement (soit en bdd comme maintenant, soit autrement — ce qui serait mieux) l’ensemble des paquets possibles pour chaque plugin : il peut y en avoir un grand nombre (1 par tag en gros…)
  - Et gérer tous les cas supplémentaires de mises à jour que toutes ces possibilités composent.

  Le SAT Solver (https://fr.wikipedia.org/wiki/Probl%C3%A8me_SAT) de SVP n’est déjà pas parfait. Il mériterait d’être refait avec un PHP plus récent. Et peut être utiliser une librairie spécifique pour ce travail mais je ne sais pas si ça existe en PHP, mis à part celui de Composer...

  Bref tout ça pour dire que… à vouloir refaire Composer dans SVP… avec nos moyens humains et connaissances du sujet loin d’être aussi grandes que l’équipe de Composer, j’ai peur qu’on s’enlise.