-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: Pywin32 updates #5615
WIP: Pywin32 updates #5615
Conversation
according to the build log, it's erroring out at
Could be a simple thing to fix potentially. |
There are a bunch of those and they are easy to fix, yes. But I don't want to patch the code. This should be fixed by adding P.S. |
My suggestion is patching, But, in a way that we don't break things for the standard way to compile it, but working towards getting it upstream. That way once it's done, there isn't a burden to maintain a patch |
dcba2d8
to
9089c2c
Compare
I've further updated the version from 221 to 224.
Yes, I'm definitely looking to do just that. |
Update: |
6caa450
to
6a69516
Compare
👍 |
I've made some more PRs in pywin32. Some of them - already merged: Fix char/wchar/tchar inconsistencies in PythonService.cpp And with #5659 fixed, I should be able to have something working within a few days. |
934eb5f
to
4f4ebd6
Compare
@joankaradimov is any progress on this? |
I have the package compiling, installing, and running locally. I was able to use the A couple of modules rely on MFC and cannot be fixed. At least not any time soon. I will replace them with code that raises Additionally I intend to wait for a new version of Another blocker is #5616. I use a patched Right now I'm working on some SEH code. Luckily it's C++ code and I should be able to use |
@joankaradimov how goes progress on this front? I see your PR has been accepted upstream, but are you still working on the SEH code? |
@ZachBacon Yes, I'm still working on it. It's a bit of a mess. I'm unable to link to Other than that - I've opened another PR in pywin32. |
4f4ebd6
to
87590d9
Compare
I've updated to version 225, squashed all commits up to that point, and I've added myself as a maintainer (I don't know if Ray Donnelly has interest in maintaining this; maybe I should drop a mail). I'm still struggling with |
Hi @joankaradimov, I don't have a lot of time to maintain things on MSYS2 unfortunately. Thank you for helping out though, it is very much appreciated. |
This turned out to be way more complex and time consuming then I thought. I experimented with vectored exception handling and came up with nothing. I read the LibSEH code and documentation, but the documentation says it does not support 64 bit SEH. It also looks too complex. I don't like the idea of downloading all of that in a Then I decided to go with mingw's Eventually I decided to take a shot at my own implementation of |
@joankaradimov any news? |
@Alexpux I have a handling of 64-bit SEH that I am happy with. I'm still working on an implementation for 32-bit, but I don't think that's a blocker -- it can be patched in with a later release. Additionally I had another PR merged: mhammond/pywin32#1444 Right now I am waiting for pywin32 228 to be released. It should be fairly soon. It will include another MINGW compatibility fix. It will also drop compatibility with Python 2. I notice a lot of MSYS2 packages have already dropped Python 2. I believe that should also be done here. |
I've updated to version 228. Some new errors are popping up now :( I'm working on fixes (and potentially on backporting as much as possible to pywin32) |
70cb109
to
3498035
Compare
3b96c74
to
bae1e7a
Compare
This is on hold again, unfortunately. After building and installing I'm experiencing the problems described here. It appears that pywin32 has problems with Python 3.8. On top of that some of the modules cannot be compiled. But that is expected for the moment. Here are some of the failures:
Additionally - I've disabled two more modules - P.S. |
bae1e7a
to
749394c
Compare
So, should we just merge this as is, so it doesn't bitrot even more, or wait? |
There's a problem in the installation I haven't fixed yet. I'd say we wait for the next version. It should drop Python 2 support and rewrite most of It will also include another MINGW compatibility fix I made in pywin32. |
ok, thanks for the update |
Just noticed that the b300 is released. Perhaps we can get some progress here? |
This patch fixes the build with the latest windmc.exe (missing trailing LF causes windmc to omit #endif in the generated .h file) |
Another thing is that os.add_dll_directory() in mingw python is somehow broken. So I had to add this patch:
|
yeah, we reverted the DLL lookup changes for 3.8 because they broke too much, and that affects add_dll_directory(). Something that needs to be fixed at some point. |
- ignore Windows SDKs installed by Visual Studio - avoid compilation errors via compiler flags - extract min/max patches to a separate file - fix more min/max calls - move module dependency fixes to a separate patch file - add more missing module dependencies - generate static import libraries for pywintypes and pythoncom - remove the python version suffixes from dependencies - update to version 225
- update to 228 - drop Python 2 support - fix some MAPI compilation problems - simplfy the patch file for dependencies - drop the patch file for min/max - disable some modules
Rebased on master. I'm going to merge this so it doesn't bit rod more. Feel free to create a new PR improving things. |
Note: this package does not build correctly (and never did, I believe).
I've updated the code to the latest version. I've fixed a conflict with the Visual Studio SDK headers being used instead of MinGW's.
I also got a couple more modules to build. Most changes are not here, though. I'll make a PR directly in the pywin32 with my changes.