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
modulegraph seams to not handle extended __path__ set in a hook (hook-win32com) #1322
Comments
Also followed all the instructions and parameters under: https://github.com/pyinstaller/pyinstaller/wiki/How-to-Report-Bugs#make-sure-everything-is-packaged |
Anton, Perhaps: import pythoncom might work? Doesn't makes sense, but does help in one of my hooks. |
Seams as if the module is actually called
|
Looks as if
So this comes down do be yet another way for namespace-packages :-( [Update:] |
I'll verify that this statement is correct on my laptop in two days time, would be awesome if the dev branch solved this (I just used the prepackaged installer for a quick fix on a project) :) |
@htgoebel not sure how you got it to run or how your
|
@Torxed I only tested it using Python2.7 and the |
from win32com.shell import shell
crashes the finished .exe with "No module named".
We need to handle this in |
This has basically been solved by implementing post-create package hooks. Since as of today we have no failing test for this and esp. win32com is working, I'm closing this issue. I've opened #1532 as a follow up for checking all hooks if they need to be converted. |
What is a solution to this one? I am using version 3.0 and still getting this issue with win32com.shell. |
The problem is that the folder |
|
This is how py2exe handles this module if this is of any help |
@htgoebel Does this look like a new candidate for |
This should become a |
Ok, I'm going to try that. |
@matysek Sorry for getting back on this so late. But all appears to be well. Thank you for looking in to this! Best regards, |
http://stackoverflow.com/questions/31203580/pyinstaller-not-reading-my-hook-file-and-doesnt-work-with-win32com-shell
In short, doing
from win32com.shell import shell
doesn't getshell
included, it also doesn't help to create ahook-win32com.shell.py
file. That never gets read. At first I thought it might get picked up bywin32com.py
which is the main module hook/file.. But modifying that doesn't help the end result.Here's the log:
warnfiletegrity.txt
Problem:
The text was updated successfully, but these errors were encountered: