![]() ![]() ![]() ![]() Given that you failed to know/discover all 3 of those workarounds on your own, it is clear that lack the knowledge/diagnostic skills to use PyInstaller. And standard Python to know that you run any Python package using python -m and could have simply used python -m PyInstaller arguments here.Standard packaging to know that package entry points are placed in the python-env/Scripts folder.It's standard command line knowledge that an executable's location needs to be in PATH to be findable.We don't give you the answer because you're clearly not ready to be using PyInstaller. As says, this is neither a bug nor is it anything to do with PyInstaller. This is an issue tracker for reporting bugs about PyInstaller. ![]() So as far as I'm concerned, it's your fault if you ignore that message. However, when you install a package with entry-point scripts and your Scripts directory is not in PATH, pip warns you about it and tells you to add it to PATH. And no other package that has entry-point scripts will work for you, either (when you try to call its entry-point scripts, that is). If you don't have that directory in PATH for whatever reason, there's nothing we can do about it. The PyInstaller installation procedure is carried out by standard python setup tooling, which install package's entry-point scripts into python's Scripts directory. Whether it's a PATH issue or PIP issue, I see no reason to dismiss the issue with an insult regarding someone's experience with package management.īecause this has nothing to do with PyInstaller. pip installs a module into site-packages, and there is no pyinstaller.exe or any other executable file there that I can see. The dismissive comment above notwithstanding, it should be as simple asīut, it's not. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |