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
pywin32 ImportError for win32files on Windows7 #9751
Comments
It actually only just got built/uploaded |
In Process Monitor, python can't find pywintypes39.dll. It lives under pywin32_system32 folder. Found similar issue mhammond/pywin32#1431 |
The problem is msys2-contrib/cpython-mingw#48 and https://github.com/mhammond/pywin32/blob/70ddf693927fa1635f15e9ef41eb1aea37fdf32a/win32/Lib/pywin32_bootstrap.py#L22 We can patch this for now |
Disable it, so it takes the fallback path used for older Python versions. Fixes msys2#9751
See #9752 |
Chris, what does options=(staticlibs) in PKGBUILD do? Linking with static (gcc, stdc++ & winpthread)? |
From PKGBUILD(5) man page:
|
ah ok.. I built my pywin32 locally with I didn't put pywintypesXX.dll and pythoncomXX.dll in System32 folder. I never had import error like the one reported here. |
I'm glad you didn't put anything in the system32 folder, you should never put anything in the system32 folder in my opinion. |
i think, the only way to fix pywin32 missing dll is to put pythoncom and pywintypes dll in %SYSTEM32% folder (like upstream does) |
Absolutely not. Never put anything in system32. Just adjust your system
path to point to those dll's if you must, but do not put dll's into
system32 folder.
…On Thu., Mar. 10, 2022, 2:59 a.m. Raed Rizqie, ***@***.***> wrote:
i think, the only way to fix pywin32 missing dll is to put pythoncom and
pywintypes dll in %SYSTEM32% folder (like upstream does)
—
Reply to this email directly, view it on GitHub
<#9751 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACEIXRFCS7766T5SUHYXUUDU7GTWTANCNFSM5FWZTCTA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
In practice, it's still a bad idea. Even if you have to put them in a
separate folder, add that to the path, it's still better than to put it in
system32.
…On Thu., Mar. 10, 2022, 4:21 a.m. مهدي شينون (Mehdi Chinoune), < ***@***.***> wrote:
Those libraries are not built with mingw, They are not part of any package.
If they could be built on mingw then we could just solve the problem by
installing them in ${MINGW_PREFIX}/bin
—
Reply to this email directly, view it on GitHub
<#9751 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACEIXRCXIN4IYXPAED5JAEDU7G5LJANCNFSM5FWZTCTA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
You didn't, but I'm still reiterating for those contemplating it.
…On Thu., Mar. 10, 2022, 5:53 a.m. مهدي شينون (Mehdi Chinoune), < ***@***.***> wrote:
In practice, it's still a bad idea. Even if you have to put them in a
separate folder, add that to the path, it's still better than to put it in
system32.
Did I say something about putting them in system32?!
—
Reply to this email directly, view it on GitHub
<#9751 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACEIXRC2VLN246MN5FSNWBLU7HIBXANCNFSM5FWZTCTA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
We currently patch this here: https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-python-pywin32/010-workaround-broken-add-dll-dir.patch Because our Python doesn't support |
Sorry, I found them under
|
I am trying to port the d-rats applications from python2 to python3, etc.
My test system is frozen at Windows 7 since Windows 10 is not supported by the hardware vendor.
I thought that msys2 mingw-64 would make the easiest deployment for end users for the python packages that are available, but have hit an issue with the mingw-w64-x86_64-python-pywin32 package.
Any help would be appreciated.
OS is windows 7 64 bit.
msys2 was installed and packages were installed today.
The text was updated successfully, but these errors were encountered: