Develop Reference

Mac OS M1 Monterey 12.4: wrong python library with "Port"

I´ve got a new MacBook Pro with M1 chip and it seems as if not alle of the open source software is converted to arm64.
Nethertheless, I try to compile missing tools (like numpy) manuell from source, like in the good ole days. As I try to do it I have to install, deinstall a lot and one tool is "port" which is working except for one thing that it complains all the time about Libraries I don't use anymore (because some tools (like Eclipse) for example are not working with Python 3.10). Therefore I regressed to Python 3.9 but every time I want to install something with "port" (which it does), it complains about the "old" Python 3.10 libs. How could I get rid of this messages?
Warning: Error parsing file
/opt/local/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/lxml/html/diff.cpython-310-darwin.so: Error opening or reading file

I was in a sort of "Dead-Lock" because versions, Libraries and executables were not consistent with Python, Eclipse, Python pip packages etc, because some packages weren't ported to amd64 until now. For example numpy and I tried to compile it from source which was possible but still not working.
Then I stumbled over a hint in a different problematic were Rosetta was recommended for that specific problem. (I´ve never worked with Rosetta because most applications were running)
So I duplicated the "terminal" Application and configured one for Rosetta, started and installed Python 3.10 in it with all new packages and startet all executables from that terminal.
After some fiddling Eclipse startet with Python and the packages which my application needed, like numpy.
(And in addition to that, it seems as if it very much faster than before)

How to make my python 3 desktop application portable?

I have tried portable python but the latest version is 3.2.5. (need 3.6+)
I cannot install libraries on it, even the get-pip.py doesn't work.
I'm trying to figure out how to make my project portable on windows systems that do not have python installed.
Also I want the minimum possible libraries(core python modules) to keep the project as lean as possible,

I would go with cx_Freeze - multiplatform module for freezing your Python script in a way that allows you to open it on other Windows machines even if they do not have Python installed. It got very nice and clear documentation also: http://cx-freeze.readthedocs.io/en/latest/ and works a bit better on Windows machines then alternative PyInstaller from my experience (which has interesting option of one-file-package, but in many cases leads to security warnings due to some dirty hacks used to obtain that feature).
However, it may not be enough if you are using some specific modules in your app, as for example matplotlib, dash, etc modules are very hard to pack correctly with Freezer.

I have found a solution to my own question after a couple of days.
I did not want to create an executable for my project but I wanted a portable python folder so that I can add libraries to it as and when I need.
The recent version of portable python is WinPython.
I had to delete some unnecessary files out of it though.
It's size is about 77 mb after extracting
https://winpython.github.io/
https://sourceforge.net/projects/winpython/files/WinPython_3.6/3.6.5.0/WinPython64-3.6.5.0Zero.exe/download

Xcode 8: Loading a plug-in failed

when launching Xcode beta 8 on a macOS Sierra beta I'm getting this error:
Loading a plug-in failed.
The plug-in or one of its prerequisite plug-ins may be missing or damaged and may need to be reinstalled.
After searching, it seems that the issue is related with python and the new security measures that Apple introduced after XCode Ghost.
I couldn't find a solution, anybody can help?
EDIT
By looking at the Xcode logs, I noticed that it has NOTHING (apparently) to do with Python.
I see a whole bunch of
*Requested but did not find extension point with identifier Xcode.**
errors
I have to say that I also have Xcode 7 installed on my machine.

I had the exact thing happen to me except on High Sierra. I had deleted the old version folders of Python in /System/Library/Frameworks/Python.framework/Versions/, which was a mistake seeing that these are the Apple installed Python files. After trying to launch Xcode, Xcode could no longer access the Python files it needed. Unfortunately I had deleted them and emptied the trash, so the only way I could restore those files was by reinstalling High Sierra.
So if you run into this plugin error and you've messed with Python files, you need to recover those files either by taking them back out of the trash or by reinstalling your operating system (reinstalling doesn't erase the data on your computer, but it will add missing files, such as the Python ones I deleted).
Hope that helps someone in a similar situation.

I've had the similar logs that seemed to have nothing to do with Python, but what ended up working for it is removing python from /Library/Frameworks with help from this answer https://stackoverflow.com/a/3819829/3046504
It was still not working, but then extracting Xcode 9.1 from the xip and launching it triggered some additional installer all worked.

Had the same issue, found the solution over there : https://developer.apple.com/forums/thread/100026
I found the key to a solution here:
https://developer.apple.com/forums/thread/100026
In the Xcode app directory:
/Applications/Xcode.app/Contents/Resources/Packages
there are four packages: CoreTypes.pkg MobileDevice.pkg
MobileDeviceDevelopment.pkg XcodeSystemResources.pkg
I had to open and install all of these packages to fix the Xcode
launch failure. Then Xcode opens normally.

if you were doing something in Python, you may have accidently deleted some files. I had the same problem and I was trying to fix it for a few days. Finally, I found a way how to fix it. Just right click on "Finder app" icon and select "Go to folder..", then paste "/System/Library/Frameworks/". If you have there a file called "Python.framework", just delete it and download new one on my website[link]. Then just restart your Mac. If it works, contact me so I know if it worked. If not, conctact me too so we can figure it out together🙂

Python 64-bit unable to start correctly (0xc00000cc) on Windows HPC

I'm trying to get my application ported over to 64-bit Python. Everything works fine on my 64-bit Windows 7 workstation (with a E8600 Core 2 Duo), but when I try to execute the same Python 2.7.2 64-bit program (which is stored in a network location) on a Windows Server 2008 HPC system with a Xeon X5680, it immediately fails (regardless of passing a source file or not) with a dialog box that reads:
"The application was unable to start correctly (0xc00000cc). Click OK to close the application."
I think both these processors should support the x86-64 instruction set, so I'm surprised it doesn't "just work." Looking up the error code from Microsoft, I found that it means "{Network Name Not Found} The specified share name cannot be found on the remote server." What it is talking about? I've tried copying the Python 64-bit installation over to the local drive, but it gives the same network-related error.
How can I fix this? Is there some inherent incompatibility that I'm missing. 32-bit Python works perfectly on both my workstation and on the HPC nodes. I'd prefer to not have to recompile everything on the HPC nodes.
Thanks.

#partofthething, based on your comment, I'm not sure how extensive your xcopy was, but it is possible you were missing some Python DLLs.
For example, if you used the standard Python installer, and Python was installed C:\Python27, you should also have C:\Windows\System32\python27.dll, or C:\Windows\SysWOW64\python27.dll. You can copy these to the root directory of your python install and then run from a network drive without any issues, but otherwise they'd be discoverable in the C:\Windows\* location.
The above should work no matter what, but I've got some theories of what might have happened:
It's possible you've chosen a non-standard install directory - This doesn't make much sense, but it could somehow be represented in the Python you're copying to the network (i.e. you installed in C:\Python27-64, and that does not exist on the HPC server).
the DLLs were completely missing - I'm doubtful they were missing, because then you should get message saying something like:
The program could not start because python27.dll is missing from your computer. Try reinstalling the program to fix this problem.
the DLLs were the wrong architecture - I wasn't able (didn't have enough patience) to get Python 2.7.2 installed, but I was able to get python 2.7.8 to fail with a more sensible error 0xc000007b (STATUS_INVALID_IMAGE_FORMAT) by forcing it to use 32-bit DLLs with a 64-bit Python.

Problem deploying Python program (packaged with py2exe)

I have a problem: I used py2exe for my program, and it worked on my computer. I packaged it with Inno Setup (still worked on my computer), but when I sent it to a different computer, I got the following error when trying to run the application: "CreateProcess failed; code 14001." The app won't run.
(Note: I am using wxPython and the multiprocessing module in my program.)
I googled for it a bit and found that the the user should install some MS redistributable something, but I don't want to make life complicated for my users. Is there a solution?
Versions:
Python 2.6.2c1,
py2exe 0.6.9,
Windows XP Pro

You need to include msvcr90.dll, Microsoft.VC90.CRT.manifest, and python.exe.manifest (renamed to [yourappname].exe.manifest) in your install directory. These files will be in the Python26 directory on your system if you installed Python with the "Just for me" option.
Instructions for doing this can be found here.
Don't forget to call multiprocessing.freeze_support() in your main function also, or you will have problems when you start a new process.
While others have discussed including the MSVC runtime in your install package, the above solution works when you only want to distribute a single .zip file containing all your files. It avoids having to create a separate install package when you don't want that additional complication.

You should be able to install that MS redistributable thingy as a part of your InnoSetup setup exe.

When you run py2exe, look closely at the final messages when it's completed. It gives you a list of DLLs that it says are needed by the program, but that py2exe doesn't automatically bundle.
Many in the list are reliably available on any Windows install, but there will be a few that you should manually bundle into your Inno Setup installation. Some are only needed if you want to deploy on older Windows installs e.g. Win 2000 or earlier.

You can ship the runtime DLLs in question with your application as a "private assembly". This simply means putting a copy of a specially-named directory containing the runtime DLLs and their manifests alongside your executable.
See my answer to this post.