gmane.comp.python.wxpython.devel

Re: It's Alive!

Robin Dunn — 2012-05-25T00:09:35

Here is the massive changeset in case anybody is curious as to what 
kinds of changes were needed: 
http://trac.wxwidgets.org/changeset/71554.  SIP handles most of the 
heavy lifting, and most of the types of things that I needed to do is 
summarized in the commit message.  I was a little surprised at how many 
files needed to be touched, but considering that there are over a 
thousand files in the source tree I guess it's not too bad.

Re: It's Alive!

Mike Driscoll — 2012-05-24T19:21:03

Have you ever tried Travis CI or ShiningPanda? I was just reading about
them the other day.

Re: Calls to python API without GIL causing crash

Robin Dunn — 2012-05-24T19:12:31

I plan on integrating it (and also look at Werner's bug reports) before 
the next 2.9.4 preview build, which will probably be in a few days.

Re: It's Alive!

Robin Dunn — 2012-05-24T18:15:36

Sure, go ahead.


Not yet.  Once we have some buildbot slaves set up with Python3 then 
there will be daily snapshot builds being made and uploaded to 
http://wxpython.org/Phoenix/snapshot-builds/.

Re: It's Alive!

Robin Dunn — 2012-05-24T18:15:25

I've already made some changes that I'll commit to SVN later.  My 
changes were essentially just the minimum needed to be able to import 
the sphinx-related modules, e.g. correcting for absolute/relative 
imports, syntax errors, and imported modules that have moved or 
disappeared.  I haven't tried running the docs building commands yet.

Re: It's Alive!

Chris Barker — 2012-05-24T17:36:43

Wow!

This is *seriously * geeky fun -- command-line compiler output whooo hoo!

congrats, Robin -- this is really great.

-Chris


On Wed, May 23, 2012 at 11:05 PM, Robin Dunn <robin< at >alldunn.com> wrote:

Re: Calls to python API without GIL causing crash

Sam Partington — 2012-05-24T16:04:54

Hi Robin,

Any progress on this?

Sam

Re: It's Alive!

Mike Driscoll — 2012-05-24T14:20:43

Robin,

On Thu, May 24, 2012 at 1:05 AM, Robin Dunn <robin< at >alldunn.com> wrote:



Nice! Congratulations! I am going to mention this on my blog, if you don't
mind. Do you have an ETA for a preview build or anything too?

-------------------
Mike Driscoll

Blog:   http://blog.pythonlibrary.org

Re: It's Alive!

Andrea Gavana — 2012-05-24T07:02:32

Congratulations! That looks very nice (and I especially liked the
mouse dance :-D ).

Judging from the number of people wishing to have wxPython running on Python 3:

http://www.python.org/3kpoll

I am sure what you have done will be another great success. I guess
now I will have to dive into the sphinx_generator and adapt it to run
on Python 3 as well ;-)

Andrea.

"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/

Re: It's Alive!

Robin Dunn — 2012-05-24T06:44:57

Yeah, I was bouncing around a bit too.  :-)

Re: It's Alive!

Werner — 2012-05-24T06:33:52

Wow!

Great news, is it really just the mouse who does the happy dance?!

Werner

It's Alive!

Robin Dunn — 2012-05-24T06:05:18

Hey all,

I've got some good news.  Here are a few thousand pictures to tell you 
all about it:  http://wxpython.org/Phoenix/ItsAlive/

Re: 20120519 test build uploaded

Werner — 2012-05-22T09:57:00

Hi,

When trying the "ShortcutEditor" demo I get a no such file 
("...../default_help_text.html").

Werner

Re: 20120519 test build uploaded

Werner — 2012-05-20T13:48:03

Hi Robin,

On 20/05/2012 11:45, Werner wrote:
...
The Layout issue is due to masked edit, some time ago I suggested a 
change to how it calculates the control size, obviously this change 
didn't make it.

Any chance the change (see attached email with patch) could be 
considered for inclusion in 2.9.4?

Werner

Re: 20120519 test build uploaded

Werner — 2012-05-20T13:29:46

Hi Robin,

On 20/05/2012 11:45, Werner wrote:
...
The validator problem is due to a change in wx.lib.sized_controls.

self.SetExtraStyle(wx.WS_EX_VALIDATE_RECURSIVELY)

has been removed everywhere except for the SizedDialog?!

Will it be left like that?

Werner

Re: 20120519 test build uploaded

Werner — 2012-05-20T10:01:05

Hi Robin,

A couple more:

- InfoBar the AGW one seems only to be a copy of the wx one, i.e. 
InfoBar is used as wx.InfoBar and no import from AGW.
- XLSGridDemo - when clicking start I get "Error: the file Example_1.xls 
is not in the data directory"

Werner

Re: 20120519 test build uploaded

Werner — 2012-05-20T09:45:56

Hi,

Issues I found in the demo:

- Preview in the print framework shows this error:

Traceback (most recent call last):
   File "PrintFramework.py", line 64, in OnPrintPage
     (w, h) = dc.GetSizeTuple()
AttributeError: 'PySwigObject' object has no attribute 'GetSizeTuple'

Major change in my own app:
2.9.3:


2.9.4:


Layout is not the same and validator do no longer update values into 
controls.

All this by just changing:
wxversion.select('2.9.3')
to:
wxversion.select('2.9.4')

Any hints on what has changed in 2.9.4 which causes such changes?

BTW, what is the status of the StaticBox? Should controls be siblings, 
should one still use StaticBoxSizer?

Will work through the demo and also try to debug where things go wrong 
with my app.

Werner

20120519 test build uploaded

R'bot — 2012-05-19T19:44:56

Hi,

A new test build of wxPython has been uploaded.  

   Version: 2.9.4.0.b20120519
   URL:     http://wxPython.kosoftworks.com/preview/20120519
   Changes: http://wxPython.kosoftworks.com/preview/20120519/CHANGES.html

Have fun!
R'bot

Re: Pheonix buildbot update

jmfauth — 2012-05-18T09:51:46


On 17 mai, 17:58, Chris Barker <chris.bar...< at >noaa.gov> wrote:



It was some kind of a raw warning. I'm aware of this.

I do not wish to enter again in a discussion, which
will quickly and as usually turn into a great confusion.

jmf

Re: Pheonix buildbot update

Kevin Ollivier — 2012-05-17T16:04:45

On May 16, 2012, at 12:57 PM, jmfauth wrote:


So wxPython has a different idea than you of how to handle the encodings issue. Get over it. It isn't perfect but the encoding conversion works for a whole lot of code out there in order to make transitioning to unicode less painful, and that's precisely what it was designed to do. Python 3 support, high on the TODO list, will greatly improve the unicode situation and reduce conversions quite considerably.

Unless you've got some real bugs to report, rather than just repeating "I wouldn't have done it this way" in so many words, please, give the ranting a rest. All you're doing is annoying people with these vague emails that all say nothing more specific than "I know all this stuff better than you do". This is neither a bug report nor constructive criticism.. nor, I might add, helpful. It is simply a condescending rant. If you really think these condescending rants are an effective a way to get people to listen to you, I encourage you to keep trying and see how that works out for you. I know I, for one, am tired of hearing it, and about ready to start sending your emails straight to /dev/null. 

There are plenty of real problems and injustices in the world far more deserving of the level of attention and frustration you show on this issue.

Regards,

Kevin

Re: Re: Pheonix buildbot update

Chris Barker — 2012-05-17T15:58:07

if you can't explain it -- no one can offer solutions -- so please
give an explaination a try!


how is that relevant -- wx doesn't change python sysntax or parsing --
what that does is essentially add the "u" before the "" automatically