On Thu, 2011-01-13 at 10:39 -0800, Paul McNett wrote:
> Hi, I'm using PyInstaller 1.5, the patched one for Python 2.6 on
> Windows. I've successfully made my one-dir exe after using py2exe for
> years, and trying out cxFreeze for a month or so. PyInstaller gets me
> much further, and I like the overall architecture.
>
> I have 2 minor issues, which I'll post about in separate threads.
>
> First issue is that I see build-directory cruft in traceback messages
> sent to me via my error reporter. Example:
>
> {{{
> Traceback (most recent call last):
> File "<string>", line 2, in <module>
> File "C:\ss\build\pyi.win32\sbs_studio\outPYZ8.pyz/sbs_studio", line
> 101, in main
> File "C:\ss\build\pyi.win32\sbs_studio\outPYZ8.pyz/App", line 1152,
> in openDatabase
> File "C:\ss\build\pyi.win32\sbs_studio\outPYZ8.pyz/App", line 1200,
> in applyDbUpdates
> File "C:\ss\build\pyi.win32\sbs_studio\outPYZ8.pyz/App", line 1193,
> in doUpdate
> <type 'exceptions.TypeError'>: execute() takes no keyword arguments
> }}}
>
> Any way to suppress that whole path ("c:\ss\build\pyi.win32\sbs_studio
> \outPYZ8.pyz/") ?
This is ticket #154:
http://www.pyinstaller.org/ticket/154
There is no workaround, sorry. It shouldn't be too difficult to
implement, but it's not done yet.
The ticket suggests a way to attack it, and I can give you further
references in PyInstaller's code, in case you feel like trying to
implement it.
--
Giovanni Bajo :: [email protected]
Develer S.r.l. :: http://www.develer.com
My Blog: http://giovanni.bajo.it
Last post: Compile-time Function Execution in D
--
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.
