Open rexzhang opened 3 years ago
That's annoying. I don't know what's going on here.
To help exclude parts of the code base: Are you on an M1 system?
That's annoying. I don't know what's going on here.
To help exclude parts of the code base: Are you on an M1 system?
i am working at intel Core i5(macbook pro)...
Although it will report an error, the packaged program is working
Maybe it's just a crop(stripping) failure?
stripping zlib.so
stripping _codecs_kr.so
strerror: [Errno 35] write could not complete without blocking
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
BlockingIOError: [Errno 35] write could not complete without blocking
ipping _lzma.so
Also, if i use brew to install python, it will cause the program not to work. I guess it's an ABI compatibility issue
https://github.com/ronaldoussoren/py2app/issues/312#issuecomment-755148041
To rule out issues with stripping binaries: run python3 setup.py py2app --no-strip
.
This results in a slightly larger application bundle, but that's not a problem in general. Note that you do need to be careful if there are closed-source C extensions and you distribute to a 3th-party, non-stripped binaries make it easier to decompile without special tooling (AFAIK, I how no experience with reverse engineering at all).
Having this same issue, cant open the app. https://pastebin.com/iivkhd0G
Before that I got an error for ruamel.yaml module not existing when it is there in the venv in pycharm as it worked before I took away --alias.
Is there something wrong with not aliasing?
I haven't found the root cause of this problem yet, and what doesn't help is that I haven't been able yet to reproduce this on my own machines.
Alias mode is significantly different from regular mode. In normal mode the code and dependencies for your application are copied into the app bundle, and in some cases modified (in particular for C shared libraries), to create a fully standalone app bundle. In alias mode the app bundle basically contains symlinks to the code outside of the bundle, mostly to have a shorter cycle time during development (just edit the sources to update the app, and only rebuild when dependencies change).
I expect that "something" interferes with copying or modifying, and given the error message likely during the removal of debug info from binaries ('stripping ...'). The code in the macholib library that does the actual work for this is fairly old and can be made robust (for example with retrying). That's something I can look in to, but as I said I cannot reproduce the issue myself and hence cannot verify if a change to this code will actually fix the issue.
I am running Catalina, I am going to try this out on bigSur on my M1 mac mini, I believe it will work on arm64 I guess?
Py38/Py39 + macOS 11.1 + xcode 12.3 + py2app 0.23 + pyobjc 7.1
full log(it's too long, so i cut some line)