llvm-project VS PyInstaller

Interesting! What is your take on TinyGo. How does the LLVM compiler compare to say something you are familiar with, i.e. gcc? Would it be comparable?

Locating this kind of bug usually starts innocently, by commenting out various places of your own code, then analyzing your program under a debugger only to find yourself doing git clone https://github.com/llvm/llvm-project a few hours later 😅

> Should I report it somewhere?

Please do. You can open an issue (Bugzilla has been deprecated) on LLVM's github repo: https://github.com/llvm/llvm-project

Here is what Clang thinks: https://github.com/llvm/llvm-project/blob/589b9df4e15131348b...

parens: ()

squares: []

braces: {}

basically a mixed of British and American English

Apple | Debugger Engineer | Full-time | Onsite | Cupertino

The LLDB team at Apple is looking for an engineer to work on the LLDB debugger. LLDB is a core part of Apple's developer tools, used internally to debug Apple's software stack and externally by millions of developers. You’ll be able to work on different levels of the stack: from supporting our existing and upcoming platforms to developing new features to make debugging even better. Most of your work will be open source, on llvm.org (http://llvm.org/) and github.com (http://github.com/) where you’ll collaborate with the LLVM and Swift community.

If you love working on low-level tools you should check out the details here: https://jobs.apple.com/en-us/details/200311412/debugger-engi...

% emcc -v emcc (Emscripten gcc/clang-like replacement + linker emulating GNU ld) 3.1.8-git clang version 15.0.0 (https://github.com/llvm/llvm-project.git 80ec0ebfdc5692a58e0832125f2c6a991df9d63f) Target: wasm32-unknown-emscripten Thread model: posix InstalledDir: /usr/local/Cellar/emscripten/3.1.8/libexec/llvm/bin

clang + lldb for getting work done

I'm working with PyInstaller under Python 2.6, which is only partially supported due to the mess MS have created with their manifest nonense which now affects Python since it is now MSVC8 compiled.

Yes, that is due to a problem with the tool I use to create the .exe. See this for more information. It will be fixed in the next few days

I've had this exact same problem with Norton Antivirus and Pyinstaller, and it is such a royal pain. There's any number of false positives from antiviruses, none of which can be handled by pyinstaller at all. The only possible recommendation is to tell the antivirus vendors to quit being so aggressive. And sometimes that works, for a specific version compiled at a specific time, until you update pyinstaller, or change to a new machine, or the phase of the moon changes.

are you running windows 7? here's a relevant issue i found on the pyinstaller github https://github.com/pyinstaller/pyinstaller/issues/4908

pyinstaller

I learned the hard way about all the issues with Tkinter/PyInstaller/Big Sur. I've tried the fixes here and was unable to get it functioning properly because /System/Library/Frameworks/Tk.framework/Tk and /System/Library/Frameworks/Tcl.framework/Tcl weren't found. I've tried PyInstaller, cx-freeze, py2app, and nuitka. I'm unable to get my program to function properly after compiling with any of these on macOS, and this is a closed source project so I need some level of code obfuscation as well.

Generally, what needs to be done to create an Django/Electron app is to package (I'm using pyInstaller)the Django app into an stand-alone executable and then bundle that into an Electron app. The question is which server should be used for this case to server Django before packaging it with pyInstaller? At the moment I'm using cherryPy as a WSGI web server to serve Django.

They need to be installed for a developer to use them. But it's entirely possible to package Python programs up into a single executable for distribution, with dependencies included. See PyInstaller.

I would go straight to using pyinstaller: https://github.com/pyinstaller/pyinstaller

Thanks, but I’m not real sure as for the other way around (x86 compiled and executed on ARM set that tell the exact same message) this exact same behavior was described as a bug that was corrected. source: https://github.com/pyinstaller/pyinstaller/issues/5640