Hi Giovanni,
yes, I agree. This situation should be detectable. I think what happened
in this case was as follows: msvcr90.dll in Python26\DLLs directory
(added manually), #39 patch not applied. Configure.py -> Makespec.py ->
Build.py, now the msvcr90.dll is in the output directory.
Patch gets applied -> the DLL is skipped, but it's already in the output
dir. So, maybe it would be enough if we cleared the output dir when
running Build.py?
Does this sound about right?
- Florian
Am 01.03.2010 19:46, schrieb Giovanni Bajo:
On Mon, 2010-03-01 at 20:41 +0200, Raoul Snyman wrote:
On 1 March 2010 20:33, Giovanni Bajo<[email protected]> wrote:
Do you think this is a situation that could be detected and diagnosed by
PyInstaller?
I manually added those files to the Python DLL directory, so I'm not
sure that it's really necessary if Florian's patch is in place.
Yes, but you weren't able to solve your problems by yourself, and there
was no diagnostic to help you. In many years of PyInstaller, I've seen
so many "broken" environments you wouldn't believe :)
The policy I would like to follow is: "if it works by running python
foobar.py, it must run after packaging as well, no matter what the
environment is". Either that, or we should at least error out (or
provide a warning, in case we can't be sure).
This is why I'm asking Florian if there is a way to detect this
situation.
--
You received this message because you are subscribed to the Google Groups
"PyInstaller" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pyinstaller?hl=en.
