Re: WxPython For Python 3.5.1

Hi,

Using the build: 
wxPython_Phoenix-3.0.3.dev1943+fdf739f-cp35-cp35m-win_amd64.whl, 

the notebook methods SetSelection() and ChangeSelection() have a bug. 
Although everything 
seems to work well (the desired page is selected), the following error 
appears in the console: 

wx._core.wxAssertionError: C++ assertion "((nPage) < GetPageCount())" 
failed at ..\..\src\msw\notebook.cpp(355) in wxNotebook::SetSelection(): 
notebook page out of range


In last December after many attempts, following the steps commented in: 

https://groups.google.com/forum/#!topic/wxpython-users/9cUXJVmE8MY

and solving other some additional errors that arose me, I compiled the 
build:

wxPython_Phoenix-3.0.3.dev1836+f764b32.tar.gz

for python 3.5 on windows 10 64bits 
(wxPython_Phoenix-3.0.3.dev1836+f764b32-cp35-none-win_amd64.whl).

Everything looked good except the above methods, but in that case occurred 
a fatal error. 

Searching in google I found (http://trac.wxwidgets.org/ticket/16561) a 
solution to the error 
(in my case it worked):

I only change in:

 sip_corewxNotebook.cpp (1518)

size_t page;   ======> changed for ======> size_t page = 0;
…
sipParseKwdArgs(…)

i compile again and the the error fixed. 

Do you know if someone else mentioned this problem? 
Just happens to python 3.5? The same distribution compiled for 3.4 runs 
fine. 

Thank you. 

PD Excuse my bad English

El martes, 1 de marzo de 2016, 0:33:04 (UTC+1), Robin Dunn escribió:
>
> Dietmar Schwertberger wrote: 
> > Please apply the encoding modification from config.py also to 
> > build_wxwidgets.py. 
> > But still the build may fail if the codepage is not 1252. Maybe 
> > build.py should call "chcp 1252" or this should be added to the build 
> > instructions. 
> > (The use of code page 1252 was recommended by the waf people when I 
> > first ran into encoding problems.) 
>
> Thanks.  I'll make that change and add a note to the README. 
>
> Ideally, now that build_wxwidgets.py has been moved into the Phoenix 
> tree we should refactor the common or otherwise similar helper code in 
> the various buildtools modules into a new module, but that can wait 
> until after more important things.  I think there is still some unused 
> Classic build code in there after-all... 
>
> -- 
> Robin Dunn 
> Software Craftsman 
> http://wxPython.org 
>

-- 
You received this message because you are subscribed to the Google Groups "wxPython-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.