-
Notifications
You must be signed in to change notification settings - Fork 802
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
python 3.8 #1327
Comments
You will need to clone and compile this repository from source first, as there are currently no builds for Python 3.8. Install MS Build Toolshttps://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2017 Clone this repository
Build from source
|
@terrdavis did u build? |
No I didn't.
…On Thu, Jul 4, 2019 at 23:12 SmartManoj ***@***.***> wrote:
@terrdavis <https://github.com/terrdavis> did u build?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1327?email_source=notifications&email_token=AEAM2UBJP367AX742D623B3P53Q4TA5CNFSM4HDDYMC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZIUIGA#issuecomment-508642328>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEAM2UE52FDI2VCFCSLP5ITP53Q4TANCNFSM4HDDYMCQ>
.
|
Is there anyway to build online? |
No. |
What about https://visualstudio.microsoft.com/vso/ & https://coder.com/? |
|
Now that Python 3.8 is out, please let us know if you plan on spinning up a build for this. I've attempted a build, but I've run into a few issues:
I got this error after running the command
|
The build process sucks - most is for historical reasons and I'm planning on a revamp of things once I can kill the 2.7 builds, which I plan doing at the end of the year once 2.7 itself is dead. That doesn't help you now though :( The sorry I can't be more help - I expect I'll hit the same issue if I try today (but I'm not going to find time to try for a little time) |
I did not see the 3.8 builds! I had assumed this issue would be updated, and didn't check that assumption before going down this rabbit hole. |
Installed the new build from pypi, but it doesn't work:
|
Yeah, the builds are there for 3.8, but they don't work, I'll quote a message from Python-dev, I encountered this problem too. On 15Oct2019 1143, MRAB wrote:
The new os.add_dll_directory() function 1 is a way for pywin32 to work around this themselves without having to relocate files. The note in the doc also explains the cause. Cheers, |
Here's sample code for a workaround (for the win32clipboard, but it also works for other DLLs) win32 = 0 |
Sorry, forgot that indentation would be lost, but it should be obvious. |
Links:
Relevant excerpt from second link:
|
I think something has changed in Python, regarding .dll search paths / order. After a few tests, I concluded that pywintypes38.dll is the one that's not found (even if its dir is in the process' %PATH% (
Notes:
|
Would it make sense to place the dlls in the Python38/DLLS folder instead of calling |
FYI: I applied the fix (from #1430 ) to the original .whls and published them on [GitHub]: CristiFati/Prebuilt-Binaries - (master) Prebuilt-Binaries/PyWin32. |
I started using Python about a week ago.
|
Sure (but restore the indentation that got lost when I posted that). Or wait for the upcoming pywin32 release 226... Mark has merged a fix that will make this workaround unnecessary... but hasn't released it yet. Watch this repo for details of the release. |
Summarizing - check: @atomcgot: you don't have to rename anything, doing so would be a lame workaround (gainarie). Not sure where that idea came from, but it's terribly wrong. For Python 3.8(.0) feel free to use the .whls mentioned in the above URLs. |
pywin32 227 is out a few days now -- https://github.com/mhammond/pywin32/releases/tag/b227 |
Is this fixed yet? It doesn't seem to be working for me, I'm using 227. |
@ogaskell: Are you still encountering the issue? Can you provide more details like Python version (3.8.0), architecture, (is it a virtual environment)? Ar you sure the PyWin32 upgrade went OK? I've tested the v227 .whl with multiple Python 3.8 configurations, and it worked OK. |
Just fyi @CristiFati , I found that v227 fixed the issue for me at least, as compared to v225. |
I've slowly been progressing in porting pywin32 to mingw. Right now I have a [partial] builds of version 228 that run on Python 2.7, but fail with the described error on Python 3.8. |
@joankaradimov: What's the purpose for the MinGW / MSYS2 port? Is there an official Python distribution for Windows built with the above toolchains? |
There is no official binary distribution that I know of. But building with MinGW appears to be supported: https://wiki.python.org/moin/WindowsCompilers#GCC_-_MinGW-w64_.28x86.2C_x64.29
If you're asking about the port of Python - MSYS2 is essentially a Unix userland on top of Windows. And it's hard to get a modern Unix userland running without a Python interpreter. And to solve this MSYS2 ships its own build of Python in its package manager. If you're asking about the port of PyWin32 - a specific problem I'm trying to solve is - get emscripten to run on the tools provided by MSYS2. Managing its long list of dependencies on Windows is a hassle. A real package manager is very handy. |
I've just open Emscripten home page, I don't know anything a bout it. Does it reference PyWin32? That would be strange. From what am I concerned Python built on MSYS2 (or any other Nix like emulator - e.g. Cygwin, ...) should only expose a Nix interface, so having PyWin32 (Win APIs exposed) there, would be incorrect from the design point of view. |
It does, yes. Parts of it are written in Python.
This is about porting to MinGW. Which is native Win32. It's GCC combined with a free reimplementation of the Win32 SDK. It only depends on the DLLs that are shipped in System32. So that should not be an incorrect design based on your criteria. (However, once it's ported, in theory it could be tweaked to work on MSYS2, Cygwin, and even Linux with libwine.) |
Is this issue still relevant? Python 3.8 support was added a long time ago |
Nope - I guess we can expect a new one for 3.13, but this one is no longer relevant. |
I would like to use this in Python 3.8.
I tried to install by renaming the latest python 3.7 .whl but when I try to import
win32api
I get this error:ImportError: DLL load failed: The specified module could not be found.
The text was updated successfully, but these errors were encountered: