Unicode, and in a broader view, everything which is related
to “characters”. Python itsself is not ok.
···
Le mardi 3 mai 2016 23:54:55 UTC+2, Tim Roberts a écrit :
jmfauth wrote:
Today, there are no more working GUI toolkits for
Python.
Probably, the single remaining options are:
Jython or IronPython.
I don't know what you were trying to say here, but as you have
stated it that statement is just silly. WxPython, Qt, and TkInter
are all alive and well, as well as a plethora of smaller and more
specialized toolkits.
On Tue, May 3, 2016 at 11:07 PM, Scott Talbert swt@techie.net wrote:
I agree with the sentiment that it would be better to release Phoenix for
both Python 2 and 3 soon, even if there are known missing or crippled
features compared to Classic. With only snapshot builds available, I think
that Phoenix is used much less than it could be.
On Tue, 3 May 2016, Matt Newville wrote:
I’m not sure why people are so scared of the snapshot builds. They are generally working pretty well, from my experience.
The snapshots seem to work OK for me too. But they’re not a release. Honestly, they’re even sort of hard to find assuming that one knows the Phoenix wiki page exists and actually reads it.
I do see several Issues and PRs on the github site, but I assume these
aren’t the main problems standing in the way of release. It would be nice
to see a more strategic and complete to-do list for release, if only to
understand what needs the most work. Does such a list exist?
Please everybody ignore this poster. He’s been banned from the main Python mailing list, where he is jokingly known as the RUE, the Resident Unicode Expert, as it is blatantly obvious that he hasn’t got a clue what he’s talking about.
Kindest regards.
Mark Lawrence.
···
On Wednesday, May 4, 2016 at 3:44:42 PM UTC+1, jmfauth wrote:
Le mardi 3 mai 2016 23:54:55 UTC+2, Tim Roberts a écrit :
jmfauth wrote:
Today, there are no more working GUI toolkits for
Python.
Probably, the single remaining options are:
Jython or IronPython.
I don't know what you were trying to say here, but as you have
stated it that statement is just silly. WxPython, Qt, and TkInter
are all alive and well, as well as a plethora of smaller and more
specialized toolkits.
--
Unicode, and in a broader view, everything which is related
to “characters”. Python itsself is not ok.
It's good to hear from you Robin. I think we all appreciate how busy you
are. Like you, I've been involved in other things and have not had much
time to follow the different wxPython-xxxx groups very closely recently,
but in the last few weeks I have been converting my own (commercial)
wxPython software to Python 3.4 & Phoenix. It has all gone pretty well
and I have only a handful of issues to raise - some fairly trivial but
one or two show stoppers - like the classes based on
wx.lib.activex.ActiveXCtrl.
I don't know the best place to report these. Maybe there should be a new
group called *wxPython-phoenix* specifically for raising, discussing and
generally keeping in touch - perhaps at the expense of wxPython-mac
which has only received about six messages this year.
They are generally working pretty well, from my experience.