20131219 test build uploaded

Robin · December 20, 2013, 6:38pm

A new test build of wxPython has been uploaded.

    Version: 3.0.0.0.b20131219
    URL: http://wxPython.kosoftworks.com/preview/20131219
    Changes: http://wxPython.kosoftworks.com/preview/20131219/CHANGES.html

Werner2 · December 21, 2013, 5:33pm

Hi Robin,

Thanks a lot for the xmas pressy:)

···

On 20/12/2013 19:38, Robin Dunn wrote:

A new test build of wxPython has been uploaded.

   Version: 3.0.0.0.b20131219
   URL: http://wxPython.kosoftworks.com/preview/20131219
   Changes: http://wxPython.kosoftworks.com/preview/20131219/CHANGES.html

I had a quick go through the demo and only found the following error:

- agw.RibbonBar demo
import error due to the wx.lib.agw import line being commented out

Will try and test against my own stuff sometimes next week.

See you
Werner

Robin · December 21, 2013, 9:37pm

Werner wrote:

Hi Robin,

Thanks a lot for the xmas pressy:)

A new test build of wxPython has been uploaded.

Version: 3.0.0.0.b20131219
URL: http://wxPython.kosoftworks.com/preview/20131219
Changes: http://wxPython.kosoftworks.com/preview/20131219/CHANGES.html

I had a quick go through the demo and only found the following error:

- agw.RibbonBar demo
import error due to the wx.lib.agw import line being commented out

Will try and test against my own stuff sometimes next week.

THanks. I had that change made in my main development environment, but hadn't checked it in yet since it was an SVN submodule instead of git so it didn't make it to the build machine.

I also noticed that I had the attached uncommitted changes made in the development environment that I don't recall any details about. Does anybody recognize this and has a better memory that I do? Should I commit the change? TIA.

persist.patch (3.45 KB)

···

On 20/12/2013 19:38, Robin Dunn wrote:

--
Robin Dunn
Software Craftsman

Werner2 · December 22, 2013, 3:45pm

Hi Robin,

...

I also noticed that I had the attached uncommitted changes made in the development environment that I don't recall any details about. Does anybody recognize this and has a better memory that I do? Should I commit the change? TIA.

That was from me, we didn't get the correct state of the restored persistance back before that patch.

Werner

···

On 21/12/2013 22:37, Robin Dunn wrote:

Metallicow · December 24, 2013, 12:43pm

Thanks for the build Robin.

Noted 1st CRASH with Source Coder here. PropertyGrid. Might be more… will report back again if more found.

print(‘CRASH’)

if not wx.VERSION_STRING.startswith(‘2.8.’):
try:
import wx.propgrid as wxpg
except ImportError as exc:
print(‘FAILED importing wx.propgrid’)

Also, other than the Happy Holidays changelog is there a full list.
Thanks. Merry Christmas.

Metallicow · December 24, 2013, 12:54pm

Hmm… Can’t even get the main demo to run under.

sys.version: 2.7.6 (default, Nov 10 2013, 19:24:18) [MSC v.1500 32 bit (Intel)]
wx.VERSION = (3, 0, 0, 0, ‘.b20131219’)

Seems there is a major problem somewhere as a lot of my sample apps are crashing also.
Individually running the demos works for some but not all.

Metallicow · December 24, 2013, 1:48pm

Here’s the full rundown speed check.

List of individually run demos that crashed/had issues with

WinXPPro SP3 32bit
sys.version: 2.7.6 (default, Nov 10 2013, 19:24:18) [MSC v.1500 32 bit (Intel)]
wx.VERSION = (3, 0, 0, 0, ‘.b20131219’)

ISSUES

···

BitmapComboBox.py - NOT showing Images
DragImage.py - UGLY, NO Background.
GetMouseState.py - AUX1 & AUX2 blip or not working
GLCanvas.py - Cone Canvas
Grid.py - Draggable Rows and Columns
MediaCtrl.py - NOT available on this platform…??? What! BS.
PDFViewer.py - clicking Load PDF button
PrintFramework.py - Print Preview

CRASHES

AboutBox.py
ActiveXWrapper_Acrobat.py
ActiveXWrapper_IE.py
AUI_DockingWindowMgr.py
AUI_MDI.py
Calendar.py - When pressing print calendar button
Dialog.py
EditableListBox.py
Editor.py - On Close Event X
ExpandoTextCtrl.py - SetMaxHeight Pressed
FileBrowseButton.py - File Entry Buttons
FileHistory.py
GenericDirCtrl.py
HtmlWindow.py
I18N.py
ImageBrowser.py
InfoBar.py
MDIDemo.py
MDISashDemo.py
Menu.py
MimeTypesManager.py
MultiChoiceDialog.py
Pickers.py
ProgressDialog.py
PropertyGrid.py
RichTextCtrl.py
SearchCtrl.py
SingleChoiceDialog.py
SizedControls.py
StandardPaths.py
StockButtons.py
TablePrint.py
TextEntryDialog.py
TimeCtrl.py
ToolBar.py
Wizard.py
XmlResource.py
XmlResourceHandler.py
XmlResourceSubclass.py

Mariano_Reingart · December 24, 2013, 7:21pm

Hello!

Except for MediaCtrl, all the demos are working fine in my case:

Ubuntu 13.04

wxPython 3.0.0.0.b20131219 gtk2 (classic)

Python 2.7.4 (default, Sep 26 2013, 03:20:26) [GCC 4.7.3]

The error reported for MediaCtrl is:

The program ‘demo.py’ received an X Window System error.

This probably reflects a bug in the program.

The error was ‘BadDrawable (invalid Pixmap or Window parameter)’.

(Details: serial 43 error_code 9 request_code 149 minor_code 18)

(Note to programmers: normally, X errors are reported asynchronously;

that is, you will receive the error a while after causing it.

To debug your program, run it with the --sync command line

option to change this behavior. You can then get a meaningful

backtrace from your debugger if you break on the gdk_x_error() function.)

Most of my dev project (gui2py) works unmodified from wx2.9, just detected the following warning:

swig/python detected a memory leak of type ‘wxPyHtmlWinTagHandler *’, no destructor found.

I’ll further test classic on windows and phoenix

Thanks for your great work!

Best regards & Merry Christmas

···

Mariano Reingart
http://www.sistemasagiles.com.ar

http://reingart.blogspot.com

Robin · December 25, 2013, 12:09am

Metallicow wrote:

Also, other than the Happy Holidays changelog is there a full list.

No. There were no new features added and only a few bug fixes on the wxPython side of things. On the wxWidgets side there has been lots done, but because of my business I wasn't keeping an eye on commits. Their changelog is here:

http://trac.wxwidgets.org/browser/wxWidgets/branches/wxPy-3.0.0/docs/changes.txt

···

--
Robin Dunn
Software Craftsman

Robin · December 25, 2013, 12:10am

Metallicow wrote:

Here's the full rundown speed check.

List of individually run demos that crashed/had issues with

WinXPPro SP3 32bit
sys.version: 2.7.6 (default, Nov 10 2013, 19:24:18) [MSC v.1500 32 bit
(Intel)]
wx.VERSION = (3, 0, 0, 0, '.b20131219')

ISSUES
-------
BitmapComboBox.py - NOT showing Images

Fixed.

DragImage.py - UGLY, NO Background.

Fixed.

GetMouseState.py - AUX1 & AUX2 blip or not working

This depends on your system sending expected events for the extra buttons. If you have any other mouse drivers loaded that remaps the extra buttons or something like that then you will likely not get them.

GLCanvas.py - Cone Canvas

WFM (Works for me)

Grid.py - Draggable Rows and Columns

WFM

MediaCtrl.py - NOT available on this platform...??? What! BS.

Do you have QuickTime installed? This sample only uses the QuickTIme backend. If you do then please remove the try/excepts and see what the real exception is saying.

PDFViewer.py - clicking Load PDF button

I don't have any of the 3rd party PDF packages installed so I can't test.

PrintFramework.py - Print Preview

WFM

CRASHES
-------
AboutBox.py

WFM

ActiveXWrapper_Acrobat.py
ActiveXWrapper_IE.py

These are old, unmaintained, not expected to work any longer, and also they are not accessible via the demo framework. The samples have been kept just in case someone wanted to keep it working or at least use it as a reference.

AUI_DockingWindowMgr.py

WFM

AUI_MDI.py

WFM

Calendar.py - When pressing print calendar button

WFM

Dialog.py

WFM

EditableListBox.py

WFM

At this point, since all these are WFM I'm leaning towards there being something wrong with your install or something else about your system that is conflicting. In absence of any other confirmations or more details about how to reliably produce a crash I'm just going to start a new build and go enjoy my holiday.

···

Editor.py - On Close Event X
ExpandoTextCtrl.py - SetMaxHeight Pressed
FileBrowseButton.py - File Entry Buttons
FileHistory.py
GenericDirCtrl.py
HtmlWindow.py
I18N.py
ImageBrowser.py
InfoBar.py
MDIDemo.py
MDISashDemo.py
Menu.py
MimeTypesManager.py
MultiChoiceDialog.py
Pickers.py
ProgressDialog.py
PropertyGrid.py
RichTextCtrl.py
SearchCtrl.py
SingleChoiceDialog.py
SizedControls.py
StandardPaths.py
StockButtons.py
TablePrint.py
TextEntryDialog.py
TimeCtrl.py
ToolBar.py
Wizard.py
XmlResource.py
XmlResourceHandler.py
XmlResourceSubclass.py

--
Robin Dunn
Software Craftsman

Metallicow · December 25, 2013, 4:47am

I’ts about time for a cookie break anyway

Well, here is how far I got with main. some small fixes, but comes to crash at the searchctrl???
Also MediaCtrl.py should be backend should be an emptystring.
Here is the debugging notes I took. BTW what windows version are you running? EVT_MEDIA_LOADED works just fine on XP.

Installed

···

wxPython3.0-win32-3.0.0.0.b20131219-py27.exe
wxPython3.0-win32-docs-demos-3.0.0.0.b20131219.exe

Main.py Test.

C:\Program Files\wxPython3.0 Docs and Demos\demo>Main.py
Unable to create process using '/bin/env python “C:\Program Files\wxPython3.0 Docs and Demos\demo\Main.py” ’

Fix: Incorrect Shebang. Needs to be portable.
#!/usr/bin/env python

wx.Trap() in debug section is crashing???.. commented out. lets seek further…

wxPythonDemo init CRASH2 Never gotten too.

print(‘CRASH’)
self.filter = wx.SearchCtrl(leftPanel, style=wx.TE_PROCESS_ENTER)
print(‘CRASH2’)

MediaCtrl.py Fix:

Don’t pick quicktime for windows. This is not a mac. Quicktime is 3rd party and may not be installed.
            ##### backend = wx.media.MEDIABACKEND_QUICKTIME
            # Use this for default Windows Media Player.
            backend = ""

Metallicow · December 25, 2013, 5:15am

MediaCtrl.py QuickTime exception… Couldn’t get one.
This is it.

···

swig/python detected a memory leak of type ‘wxMediaCtrl *’, no destructor found.

Werner2 · December 26, 2013, 2:16pm

Hi,

I'ts about time for a cookie break anyway

Well, here is how far I got with main. some small fixes, but comes to crash at the searchctrl???
Also MediaCtrl.py should be backend should be an emptystring.
Here is the debugging notes I took. BTW what windows version are you running? EVT_MEDIA_LOADED works just fine on XP.

Installed
---------
wxPython3.0-win32-3.0.0.0.b20131219-py27.exe
wxPython3.0-win32-docs-demos-3.0.0.0.b20131219.exe

Main.py Test.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Program Files\wxPython3.0 Docs and Demos\demo>Main.py
Unable to create process using '/bin/env python "C:\Program Files\wxPython3.0 Docs and Demos\demo\Main.py" '

Fix: Incorrect Shebang. Needs to be portable.
#!/usr/bin/env python

Is that even used on Win?

How is your file association for .py setup?

I start the demo either with this in my shortcut:

"C:\Python27\Doc\wxPython3.0 Docs and Demos\demo\demo.pyw"

or this if I want a console and want to control which Python version to use:

C:\Python27\python.exe "C:\Python27\Doc\wxPython3.0 Docs and Demos\demo\demo.pyw"

Werner

···

On 25/12/2013 05:47, Metallicow wrote:

Metallicow · December 27, 2013, 6:51am

Hi,

Is that even used on Win?

#!/usr/bin/env python

works reliably on all of the major platforms.
if for example you have more than one python version installed…
For example I am using 27 currently but when I need to test on 33 I just place a 3 or 33 at the end of the shebang
Python then knows which version of the interpreter to use, so yes the shebangs do work with windows.
It just has to be the portable version, which works reliably.

How is your file association for .py setup?

My Computer>Properties>Environment Variables(Advanced Tab)

C:\Python27;C:\Python27\Lib\site-packages;
… Standard Setup. Change to 33 if wanting 33 to be default.

I start the demo either with this in my shortcut:

The installer makes startmenu shortcuts and all the other stuff just as other installers do also.

StartMenu Shortcut
Target: “C:\Program Files\wxPython3.0 Docs and Demos\demo\demo.pyw”
Start in: “C:\Program Files\wxPython3.0 Docs and Demos\demo”

“C:\Python27\Doc\wxPython3.0 Docs and Demos\demo\demo.pyw”

or this if I want a console and want to control which Python version to use:

C:\Python27\python.exe “C:\Python27\Doc\wxPython3.0 Docs and
Demos\demo\demo.pyw”

Werner

Yep all the same basic stuff. I am thinking it has to do with wx3.0, as every version from 28 to 2.9.5 works fine…
Which is brings me to that conclusion… I would think the problem originated somewhere in the core stuff(what becomes compiled), because the crashing of basic widgets and/or memory leaks isn’t normal.
Can’t even get a traceback on most stuff.
Everyone so far hasn’t provided what version of windows they are using yet in their replies.???
Almost always if wxPy runs on XP, then it will also on later versions…Vista, 7, probably 8(haven’t tested anything on 8 yet tho…) and usually 2000 for most all basic stuff.

So at this point, I am clueless as to where the issue started, but lay a good bet on it being in wx3.0 somewhere.

···

On Thursday, December 26, 2013 8:16:44 AM UTC-6, werner wrote:

Mariano_Reingart · December 27, 2013, 7:47am

Everything seems to be working almost fine on my Win7 box:

2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit (Intel)]
3.0.0.0.b20131219 msw (classic)
platform.platform() -> 'Windows-7-6.1.7601-SP1'

Even HTML2_WebView, ActiveX_IEHtmlWindow, AGW AUI and XLSGrid run ok
DragImage baground has some issue, but in general it looks fine.

When I closed the demo, a wxWidgets Debug Alerts said "module.cpp(194)
assert .... faied in wxModule::DoCleanUpModules(): not initialized module
being cleaned up"

I'll try to test in on Win8, WinXP is a bit old but I could install
python2.7 if you need testers.

Best regards

Mariano Reingart
http://www.sistemasagiles.com.ar

···

On Fri, Dec 27, 2013 at 3:51 AM, Metallicow <metaliobovinus@gmail.com>wrote:

On Thursday, December 26, 2013 8:16:44 AM UTC-6, werner wrote:

Hi,

Is that even used on Win?

#!/usr/bin/env python

works reliably on all of the major platforms.
if for example you have more than one python version installed...
For example I am using 27 currently but when I need to test on 33 I just
place a 3 or 33 at the end of the shebang
Python then knows which version of the interpreter to use, so yes the
shebangs do work with windows.
It just has to be the portable version, which works reliably.

How is your file association for .py setup?

My Computer>Properties>Environment Variables(Advanced Tab)

C:\Python27;C:\Python27\Lib\site-packages;
... Standard Setup. Change to 33 if wanting 33 to be default.

I start the demo either with this in my shortcut:

The installer makes startmenu shortcuts and all the other stuff just as
other installers do also.

StartMenu Shortcut
Target: "C:\Program Files\wxPython3.0 Docs and Demos\demo\demo.pyw"
Start in: "C:\Program Files\wxPython3.0 Docs and Demos\demo"

"C:\Python27\Doc\wxPython3.0 Docs and Demos\demo\demo.pyw"

or this if I want a console and want to control which Python version to
use:

C:\Python27\python.exe "C:\Python27\Doc\wxPython3.0 Docs and
Demos\demo\demo.pyw"

Werner

Yep all the same basic stuff. I am thinking it has to do with wx3.0, as
every version from 28 to 2.9.5 works fine...
Which is brings me to that conclusion... I would think the problem
originated somewhere in the core stuff(what becomes compiled), because the
crashing of basic widgets and/or memory leaks isn't normal.
Can't even get a traceback on most stuff.
Everyone so far hasn't provided what version of windows they are using yet
in their replies.???
Almost always if wxPy runs on XP, then it will also on later
versions...Vista, 7, probably 8(haven't tested anything on 8 yet tho...)
and usually 2000 for most all basic stuff.

So at this point, I am clueless as to where the issue started, but lay a
good bet on it being in wx3.0 somewhere.

Werner2 · December 27, 2013, 12:10pm

Hi,

...

Everyone so far hasn't provided what version of windows they are using yet in their replies.???

I am on Win 7 64 bit, but Python all the stuff I use with it is the 32 bit build(s).

Werner

···

On 27/12/2013 07:51, Metallicow wrote:

On Thursday, December 26, 2013 8:16:44 AM UTC-6, werner wrote: