Today, I found strange error while using py2exe:
1. I wrote simple program and save as 1.py:
import win32ui
import win32con
win32ui.MessageBox('Test messageBox.' , 'Test', win32con.MB_OK |
win32con.MB_TOPMOST )
2. I create 1_setup.py file for py2exe:
> from distutils.core import setup
> import
Python:
ActivePython 2.4.2 Build 10 (ActiveState
Corp.) based on
Python 2.4.2 (#67, Jan 17 2006, 15:36:03) [MSC
v.1310 32 bit (Intel)] on win32
-
win32ui:
Dont know how to get version info.
Little snippet
[code:1:f18a50c332]import win32ui
aa = sorted(dir(win32ui))
for i in
I fixed problem using Atypes:
import ctypes
ctypes.windll.user32.MessageBoxA(0, 'test', 'Title',
win32con.MB_ICONINFORMATION | win32con.MB_OK |
win32con.MB_TOPMOST)
It compiles and runs fine with py2exe.
Dont remember buggy pywin32 :)
--
http://mail.python.org/mailman/listinfo/python-list
> Fredrik Lundhwrote:
Could you perhaps use basic netiquette stuff, such as sticking to the
same sub-
> ject line for followup posts in the same thread, and including a
least some trace
> of the post you're commenting on ?
>
> (this would be less of a problem if everyone was reading your posts
in
> Fredrik Lundhwrote:
Could you perhaps use basic netiquette stuff, such as sticking to the
same sub-
> ject line for followup posts in the same thread, and including a
least some trace
> of the post you're commenting on ?
>
> (this would be less of a problem if everyone was reading your posts
in
> Fredrik Lundhwrote:
Could you perhaps use basic netiquette stuff, such as sticking to the
same sub-
> ject line for followup posts in the same thread, and including a
least some trace
> of the post you're commenting on ?
>
> (this would be less of a problem if everyone was reading your posts
in
