2.5.3.1rc2 release candidate build uploaded

Hi,

A new RC build of wxPython has been uploaded to starship.

   Version: 2.5.3.1rc2
   URL: http://starship.python.net/crew/robind/wxPython/preview/2.5.3.1rc2
   Changes: http://starship.python.net/crew/robind/wxPython/preview/2.5.3.1rc2/CHANGES.html

Have fun!
R'bot

Maybe is just me but this one looks rock solid compared to the previous candidate. Kudos! :slight_smile:

well... since praise has little constructive value I'll get to criticism :slight_smile:
There must be done something about the errors in the demo... every time there is a error in the demo the notebook tab gets screwed.
Also....Maybe "Samples using an external library" could give users some clues about the libraries like maybe links to PyOpenGL, PIL or whatever...
I know that pressing the "Cube" button shows the SF link to PyOpenGL but I was thinking that this links could be shown in the WxPython tab of the notebook... as a foot note or something and if the library is not present maybe opt-out the sample. Right now the only thing that crashes the demo ( the only one I found so far) is the PyOpenGL bit.... I don't have it installed... :slight_smile:

···

On Tue, 02 Nov 2004 08:51:31 +0200, R'bot <rbot@wxpython.org> wrote:

Hi,

A new RC build of wxPython has been uploaded to starship.

   Version: 2.5.3.1rc2
   URL: http://starship.python.net/crew/robind/wxPython/preview/2.5.3.1rc2
   Changes: http://starship.python.net/crew/robind/wxPython/preview/2.5.3.1rc2/CHANGES.html

Have fun!
R'bot

--
Peter Damoc
Hacker Wannabe
http://www.sigmacore.net/

Peter Damoc wrote:

Maybe is just me but this one looks rock solid compared to the previous candidate. Kudos! :slight_smile:

Thanks. The URL DnD problems you saw are still there, I wasn't able to track that down as it is crashing way deep in the MS code, but I did verify that it is only happening in the unicode build.

well... since praise has little constructive value I'll get to criticism :slight_smile:
There must be done something about the errors in the demo... every time there is a error in the demo the notebook tab gets screwed.

What errors are you seeing now?

Also....Maybe "Samples using an external library" could give users some clues about the libraries like maybe links to PyOpenGL, PIL or whatever...
I know that pressing the "Cube" button shows the SF link to PyOpenGL but I was thinking that this links could be shown in the WxPython tab of the notebook... as a foot note or something and if the library is not present maybe opt-out the sample. Right now the only thing that crashes the demo ( the only one I found so far) is the PyOpenGL bit.... I don't have it installed... :slight_smile:

I don't understand. Are you getting the message dialog or is it crashing when you run the GLCanvas sample?

···

On Tue, 02 Nov 2004 08:51:31 +0200, R'bot <rbot@wxpython.org> wrote:

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Sorry about that... my wrong... :o) I thought that I didn't installed PyOpenGL but actually I did install it and forgot to install glut32.dll
so uppon entering the demo page for PyOpenGL the demo crashed because PyOpenGL couldn't find glut32.dll.

···

On Tue, 02 Nov 2004 11:41:49 -0800, Robin Dunn <robin@alldunn.com> wrote:

Peter Damoc wrote:

On Tue, 02 Nov 2004 08:51:31 +0200, R'bot <rbot@wxpython.org> wrote:

Maybe is just me but this one looks rock solid compared to the previous
candidate. Kudos! :slight_smile:

Thanks. The URL DnD problems you saw are still there, I wasn't able to
track that down as it is crashing way deep in the MS code, but I did
verify that it is only happening in the unicode build.

well... since praise has little constructive value I'll get to criticism :slight_smile:
There must be done something about the errors in the demo... every time
there is a error in the demo the notebook tab gets screwed.

What errors are you seeing now?

Also....Maybe "Samples using an external library" could give users some
clues about the libraries like maybe links to PyOpenGL, PIL or whatever...
I know that pressing the "Cube" button shows the SF link to PyOpenGL but
I was thinking that this links could be shown in the WxPython tab of the
notebook... as a foot note or something and if the library is not
present maybe opt-out the sample. Right now the only thing that crashes
the demo ( the only one I found so far) is the PyOpenGL bit.... I don't
have it installed... :slight_smile:

I don't understand. Are you getting the message dialog or is it
crashing when you run the GLCanvas sample?

--
Peter Damoc
Hacker Wannabe
http://www.sigmacore.net/

There is one small bug related to SetMinSize of a Frame here on Windows:
here is some sample code:

import wx

class Sigmacore(wx.Frame):
     def __init__(self):
         wx.Frame.__init__(self, None, title="Sigmacore")
         self.SetMinSize((640, 480))
         self.Show()

app = wx.App(0)
Sigmacore()
app.MainLoop()

the problem relies in how SetMinSize works, in the above example I get a Frame at a certain dimmension, probably a default, and if I try to move the frame or resize it in any way the size jumps at 640x480. Why isn't the min size checked uppon Show?

Also related to this.... I think the demo should have a minimum size... 640x480 sounds nice.... also, the widgets tree should have a minimum width of about.... 120 px. Most of people might not ever see refinements like this but I consider them good design practices, people should not be able to put the demo in an unusable state (take a look at how usable is at 300x200)

specs: WinXP, py2.3.4, wxpy 2.5.3.1RC2

···

On Tue, 02 Nov 2004 08:51:31 +0200, R'bot <rbot@wxpython.org> wrote:

Hi,

A new RC build of wxPython has been uploaded to starship.

   Version: 2.5.3.1rc2
   URL: http://starship.python.net/crew/robind/wxPython/preview/2.5.3.1rc2
   Changes: http://starship.python.net/crew/robind/wxPython/preview/2.5.3.1rc2/CHANGES.html

Have fun!
R'bot

--
Peter Damoc
Hacker Wannabe
http://www.sigmacore.net/

Peter Damoc wrote:

Hi,

A new RC build of wxPython has been uploaded to starship.

   Version: 2.5.3.1rc2
   URL: http://starship.python.net/crew/robind/wxPython/preview/2.5.3.1rc2
   Changes: http://starship.python.net/crew/robind/wxPython/preview/2.5.3.1rc2/CHANGES.html

Have fun!
R'bot

There is one small bug related to SetMinSize of a Frame here on Windows:
here is some sample code:

import wx

class Sigmacore(wx.Frame):
    def __init__(self):
        wx.Frame.__init__(self, None, title="Sigmacore")
        self.SetMinSize((640, 480))
        self.Show()

app = wx.App(0)
Sigmacore()
app.MainLoop()

the problem relies in how SetMinSize works, in the above example I get a Frame at a certain dimmension, probably a default, and if I try to move the frame or resize it in any way the size jumps at 640x480. Why isn't the min size checked uppon Show?

Show doesn't do any sizing so it shouldn't change anything other than the visibility of the window. OTOH, SetMinSize could probably check the current size and see if it needs adjusted. Please enter a feature request about this.

Also related to this.... I think the demo should have a minimum size... 640x480 sounds nice.... also, the widgets tree should have a minimum width of about.... 120 px. Most of people might not ever see refinements like this but I consider them good design practices, people should not be able to put the demo in an unusable state (take a look at how usable is at 300x200)

Thanks.

···

On Tue, 02 Nov 2004 08:51:31 +0200, R'bot <rbot@wxpython.org> wrote:

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Hi Robin and others,

I recently d/led this build and installed it on my resident Windows XP box (removing 2.5.2.8 when it asked), and after installing it I realized that I'd need to rebuild my wxMozilla extension to test some of my apps on 2.5.3. Feeling lazy (sorry, but I'm working on some other things right now), I wanted to go back to 2.5.2.8 so I uninstalled 2.5.3 using add-remove programs, then I re-installed 2.5.2.8.

But now, "from wxPython.wx import *" imports no longer work. "import wx" does work, and thus the demo works, but apps I have that use the former all choke out on the import line. I know this isn't the most descriptive of error reports, but do you have any idea what might have changed (or remained) by undergoing the install/uninstall process? Can anyone else reproduce this? While usually these things are a serious case of user error on my part, it happened immediately after an install/uninstall/install combo. I did nothing else outside of that.

Help! :wink:

Thanks,

Kevin

···

On Nov 1, 2004, at 7:27 PM, R'bot wrote:

Hi,

A new RC build of wxPython has been uploaded to starship.

   Version: 2.5.3.1rc2
   URL: http://starship.python.net/crew/robind/wxPython/preview/2.5.3.1rc2
   Changes: http://starship.python.net/crew/robind/wxPython/preview/2.5.3.1rc2/CHANGES.html

Have fun!
R'bot

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwidgets.org

Kevin Ollivier wrote:

Hi Robin and others,

I recently d/led this build and installed it on my resident Windows XP box (removing 2.5.2.8 when it asked), and after installing it I realized that I'd need to rebuild my wxMozilla extension to test some of my apps on 2.5.3. Feeling lazy (sorry, but I'm working on some other things right now), I wanted to go back to 2.5.2.8 so I uninstalled 2.5.3 using add-remove programs, then I re-installed 2.5.2.8.

But now, "from wxPython.wx import *" imports no longer work. "import wx" does work, and thus the demo works, but apps I have that use the former all choke out on the import line. I know this isn't the most descriptive of error reports, but do you have any idea what might have changed (or remained) by undergoing the install/uninstall process? Can anyone else reproduce this? While usually these things are a serious case of user error on my part, it happened immediately after an install/uninstall/install combo. I did nothing else outside of that.

What is in your sys.path and in your site-pacakges dir? (I did a similar uninstall/reinstall this morngin to answer the 2.5.2.8u question, and didn't notice anything unusual, but I didn't try "from wxPython.wx import *" either...)

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Robin Dunn wrote:

Kevin Ollivier wrote:

Hi Robin and others,

I recently d/led this build and installed it on my resident Windows XP box (removing 2.5.2.8 when it asked), and after installing it I realized that I'd need to rebuild my wxMozilla extension to test some of my apps on 2.5.3. Feeling lazy (sorry, but I'm working on some other things right now), I wanted to go back to 2.5.2.8 so I uninstalled 2.5.3 using add-remove programs, then I re-installed 2.5.2.8.

But now, "from wxPython.wx import *" imports no longer work. "import wx" does work, and thus the demo works, but apps I have that use the former all choke out on the import line. I know this isn't the most descriptive of error reports, but do you have any idea what might have changed (or remained) by undergoing the install/uninstall process? Can anyone else reproduce this? While usually these things are a serious case of user error on my part, it happened immediately after an install/uninstall/install combo. I did nothing else outside of that.

What is in your sys.path and in your site-pacakges dir? (I did a similar uninstall/reinstall this morngin to answer the 2.5.2.8u question, and didn't notice anything unusual, but I didn't try "from wxPython.wx import *" either...)

I just did it again to be sure:

[C:\] py
Python 2.3.4 (#53, May 25 2004, 21:17:02) [MSC v.1200 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> from wxPython.wx import *
>>> wxVERSION
(2, 5, 2, 8, '')

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Hi Robin,

Kevin Ollivier wrote:

Hi Robin and others,
I recently d/led this build and installed it on my resident Windows XP box (removing 2.5.2.8 when it asked), and after installing it I realized that I'd need to rebuild my wxMozilla extension to test some of my apps on 2.5.3. Feeling lazy (sorry, but I'm working on some other things right now), I wanted to go back to 2.5.2.8 so I uninstalled 2.5.3 using add-remove programs, then I re-installed 2.5.2.8.
But now, "from wxPython.wx import *" imports no longer work. "import wx" does work, and thus the demo works, but apps I have that use the former all choke out on the import line. I know this isn't the most descriptive of error reports, but do you have any idea what might have changed (or remained) by undergoing the install/uninstall process? Can anyone else reproduce this? While usually these things are a serious case of user error on my part, it happened immediately after an install/uninstall/install combo. I did nothing else outside of that.

What is in your sys.path and in your site-pacakges dir? (I did a similar uninstall/reinstall this morngin to answer the 2.5.2.8u question, and didn't notice anything unusual, but I didn't try "from wxPython.wx import *" either...)

I did check for an incomplete wx or wxPython dir, but everything seems to be there. In any case, here's the printout for site.py and the contents of my site-packages:

Python 2.3.4 (#53, May 25 2004, 21:17:02) [MSC v.1200 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> print sys.path
['', 'C:\\WINDOWS\\System32\\python23.zip', 'C:\\Python23\\lib\\site-packages\\P
ythonwin', 'C:\\Python23\\lib\\site-packages\\win32', 'C:\\Python23\\lib\\site-p
ackages\\win32\\lib', 'C:\\Python23\\lib\\site-packages', 'C:\\Python23\\DLLs',
'C:\\Python23\\lib', 'C:\\Python23\\lib\\plat-win', 'C:\\Python23\\lib\\lib-tk',
  'C:\\Python23']

C:\oss\documancer\src>dir /w C:\Python23\lib\site-packages
  Volume in drive C has no label.
  Volume Serial Number is 44AB-7789

  Directory of C:\Python23\lib\site-packages

[.] [..] [Cheetah]
drv_libxml2.py drv_libxml2.pyc drv_libxml2.pyo
em.pyc libxml2.py libxml2.pyc
libxml2.pyo [libxmlmods] libxslt.py
libxslt.pyc libxslt.pyo PyLucene.py
PyLucene.pyc [pypackage] [PythonCardPrototype]
pythoncom.py pythoncom.pyc [Pythonwin]
PyWin32.chm PyWise23.dll README.txt
UnWisePW32.exe [win32] [win32com]
[win32comext] [wx] [wxPython]
_PyLucene.pyd [_xmlplus]
               19 File(s) 7,703,726 bytes
               13 Dir(s) 8,948,871,168 bytes free

Thanks,

Kevin

···

On Nov 4, 2004, at 12:47 PM, Robin Dunn wrote:

Hi Robin,

Robin Dunn wrote:

Kevin Ollivier wrote:

Hi Robin and others,

I recently d/led this build and installed it on my resident Windows XP box (removing 2.5.2.8 when it asked), and after installing it I realized that I'd need to rebuild my wxMozilla extension to test some of my apps on 2.5.3. Feeling lazy (sorry, but I'm working on some other things right now), I wanted to go back to 2.5.2.8 so I uninstalled 2.5.3 using add-remove programs, then I re-installed 2.5.2.8.

But now, "from wxPython.wx import *" imports no longer work. "import wx" does work, and thus the demo works, but apps I have that use the former all choke out on the import line. I know this isn't the most descriptive of error reports, but do you have any idea what might have changed (or remained) by undergoing the install/uninstall process? Can anyone else reproduce this? While usually these things are a serious case of user error on my part, it happened immediately after an install/uninstall/install combo. I did nothing else outside of that.

What is in your sys.path and in your site-pacakges dir? (I did a similar uninstall/reinstall this morngin to answer the 2.5.2.8u question, and didn't notice anything unusual, but I didn't try "from wxPython.wx import *" either...)

I just did it again to be sure:

[C:\] py
Python 2.3.4 (#53, May 25 2004, 21:17:02) [MSC v.1200 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> from wxPython.wx import *
>>> wxVERSION
(2, 5, 2, 8, '')
>>>

Thanks, actually, after doing some more testing, I find that it does work fine from the interpreter, but for some reason in scripts it's failing after subsequent attempts to load wxPython.wx. For example, in EClass, I call "from wxPython.wx import *" and it does work, but then, after importing a number of non-GUI modules, I call a module that also does a "from wxPython.wx import *" and it fails. Even stranger, with Documancer, it is the *third* attempt to import all of wxPython.wx that fails; the first two work just fine, and all three import wxPython.wx in identical manners. I ran python -v to ensure it's loading the libraries from the correct place, and everything seems correct, so I'm stumped. ;-/

Any ideas? Thanks again.

Kevin

···

On Nov 4, 2004, at 12:56 PM, Robin Dunn wrote:

Kevin Ollivier wrote:

Thanks, actually, after doing some more testing, I find that it does work fine from the interpreter, but for some reason in scripts it's failing after subsequent attempts to load wxPython.wx. For example, in EClass, I call "from wxPython.wx import *" and it does work, but then, after importing a number of non-GUI modules, I call a module that also does a "from wxPython.wx import *" and it fails. Even stranger, with Documancer, it is the *third* attempt to import all of wxPython.wx that fails; the first two work just fine, and all three import wxPython.wx in identical manners. I ran python -v to ensure it's loading the libraries from the correct place, and everything seems correct, so I'm stumped. ;-/

In what way is it failing? ImportError? Not loading any names into the module's namespace? ?

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Hi Robin,

···

On Nov 4, 2004, at 1:49 PM, Robin Dunn wrote:

Kevin Ollivier wrote:

Thanks, actually, after doing some more testing, I find that it does work fine from the interpreter, but for some reason in scripts it's failing after subsequent attempts to load wxPython.wx. For example, in EClass, I call "from wxPython.wx import *" and it does work, but then, after importing a number of non-GUI modules, I call a module that also does a "from wxPython.wx import *" and it fails. Even stranger, with Documancer, it is the *third* attempt to import all of wxPython.wx that fails; the first two work just fine, and all three import wxPython.wx in identical manners. I ran python -v to ensure it's loading the libraries from the correct place, and everything seems correct, so I'm stumped. ;-/

In what way is it failing? ImportError? Not loading any names into the module's namespace? ?

Sorry, the exact error is:

"ImportError: No module named wx"

Thanks,

Kevin

Kevin Ollivier wrote:

Hi Robin,

Kevin Ollivier wrote:

Thanks, actually, after doing some more testing, I find that it does work fine from the interpreter, but for some reason in scripts it's failing after subsequent attempts to load wxPython.wx. For example, in EClass, I call "from wxPython.wx import *" and it does work, but then, after importing a number of non-GUI modules, I call a module that also does a "from wxPython.wx import *" and it fails. Even stranger, with Documancer, it is the *third* attempt to import all of wxPython.wx that fails; the first two work just fine, and all three import wxPython.wx in identical manners. I ran python -v to ensure it's loading the libraries from the correct place, and everything seems correct, so I'm stumped. ;-/

In what way is it failing? ImportError? Not loading any names into the module's namespace? ?

Sorry, the exact error is:

"ImportError: No module named wx"

Which module and line number is it coming from?

Take a look at the manipulations done to sys.modules in wxPython/__init__.py and the autogenerated modules such as wxPython/_core.py. It's needed because of the overlap of names between the wxPython.wx module and the wx pacakge. I suspect that what you are seeing has something to do with that, but I can't duplicate any problems here...

Does any of the code you are importing manipulate sys.modules or import wxPython in different ways, such as "import wx" or "from wxPython import wx"?

You might try putting a try/except around the import with problems and take a look at sys.modules at that point.

···

On Nov 4, 2004, at 1:49 PM, Robin Dunn wrote:

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Hi Robin,

[snip]

Take a look at the manipulations done to sys.modules in wxPython/__init__.py and the autogenerated modules such as wxPython/_core.py. It's needed because of the overlap of names between the wxPython.wx module and the wx pacakge. I suspect that what you are seeing has something to do with that, but I can't duplicate any problems here...

Does any of the code you are importing manipulate sys.modules or import wxPython in different ways, such as "import wx" or "from wxPython import wx"?

You might try putting a try/except around the import with problems and take a look at sys.modules at that point.

Thanks for all your help! I found the problem. It was related to wxMozilla... ^_^; Apparently, one of the wxPython uninstallers deleted _mozilla.pyd from the wx package but left the mozilla.py file(s) in place, leaving me to think that wxMozilla didn't need reinstalled.

What happened was that in wxPython/mozilla.py it deletes sys.modules['wxPython.wx'], then imports wx.mozilla, then puts sys.modules['wxPython.wx'] back. Since the import wx.mozilla step was failing due to the missing library, it never got around to putting wxPython.wx back, and thus it ended up being set to None. ;-/

What I don't understand is why this import failure was a silent one in both EClass and Documancer. Thanks to your sys.modules tip, I was able to track the status of wxPython.wx throughout the import process, and that's how I realized that the programs were failing after trying to import wxMozilla.

So now I've got egg on my face, but I do really appreciate your help as next time something like this happens I will know better how to debug it. :wink:

Thanks,

Kevin

···

On Nov 4, 2004, at 3:26 PM, Robin Dunn wrote: