On 7 May 2018 at 11:30, Dan Stromberg wrote:
> I'd very much like a live in a world where Jython and IronPython and
> MicroPython and Cython and Pyjamas can all catch up and implement
> Python 3.7, 3.8, and so forth.
>
I'm inclined to agree that a Python 3.8 PEP in the spirit of the PEP 3003
lan
When I think of why Python is so far ahead of Perl in language design,
I think it's simply that Python is the result of cautious design, and
Perl is the result of exuberant design.
I think Python is in danger of becoming a large language - which isn't
a good thing.
A great language, like Scheme o
Thanks for the heads-up; I skimmed python-dev but did not check bpo. - Paul
On Sun, May 6, 2018, 11:35 AM Zachary Ware
wrote:
> On Sun, May 6, 2018 at 3:05 AM, Paul Goins wrote:
> > Hi,
> >
> > Just kind of "looking around" at stuff I can help with, and I noticed a
> few
> > days ago that Wind
For me, Tcl/Tk failed to build with SDK 10.0.16299.0 , I had to
expicitly fall back to 10.0.15063.0 (
https://stackoverflow.com/questions/48559337/error-when-building-tcltk-in-visual-studio-2017
). May be related if VS was (auto)updated on the builders.||
On 06.05.2018 11:05, Paul Goins wrote:
On Mon, May 7, 2018 at 6:04 AM, Terry Reedy wrote:
> On 5/6/2018 10:03 AM, Chris Angelico wrote:
>> If it were up to me, I would deprecate non-threaded mode immediately,
>
>
> Given that 99% of tkinter users do not need threaded tcl, why cut some of
> them off?
"Non-threaded" really just means "n
On 5/6/2018 10:03 AM, Chris Angelico wrote:
On Sun, May 6, 2018 at 6:54 PM, Terry Reedy wrote:
Is it ALL of Tkinter that fails in threaded mode?
No. It is non-threaded tcl that fails in threaded mode, along with
tkinter's attempt to make non-thread tcl work anyway. There are at least
two di
On Sun, May 6, 2018 at 3:05 AM, Paul Goins wrote:
> Hi,
>
> Just kind of "looking around" at stuff I can help with, and I noticed a few
> days ago that Windows 10 AMD64 builds of Python 3.6/3.7/3.x are generally
> failing.
>
> It seems like the failures started April 16th around 1am per BuildBot a
On 5/6/2018 8:51 AM, Stefan Krah wrote:
Steven D'Aprano wrote:
What exactly didn't work? I don't understand.
https://bugs.python.org/issue33412
Isn't the standard solution to use a queue for updating the GUI?
At least I didn't have any problems at all with my one TKinter app, I
think the m
Hi,
Just kind of "looking around" at stuff I can help with, and I noticed a few
days ago that Windows 10 AMD64 builds of Python 3.6/3.7/3.x are generally
failing.
It seems like the failures started April 16th around 1am per BuildBot and
went from consistently passing to consistently failing. The
On Sun, May 6, 2018 at 6:54 PM, Terry Reedy wrote:
>> Is it ALL of Tkinter that fails in threaded mode?
>
> No. It is non-threaded tcl that fails in threaded mode, along with
> tkinter's attempt to make non-thread tcl work anyway. There are at least
> two different cases.
>
> Ivan has clarified
Steven D'Aprano wrote:
>> What exactly didn't work? I don't understand.
>
> https://bugs.python.org/issue33412
Isn't the standard solution to use a queue for updating the GUI?
At least I didn't have any problems at all with my one TKinter app, I
think the method is described in the Python Cookbo
On 5/5/2018 9:45 PM, Chris Angelico wrote:
On Sun, May 6, 2018 at 11:39 AM, Steven D'Aprano wrote:
On Sun, May 06, 2018 at 11:09:21AM +1000, Chris Angelico wrote:
What exactly didn't work? I don't understand.
https://bugs.python.org/issue33412
I've read it and I still don't fully under
On 5 May 2018 at 18:55, Jeroen Demeyer wrote:
> Hello all,
>
> I have updated PEP 575 in response to some posts on this mailing list and
> to some discussions in person with the core Cython developers.
> See https://www.python.org/dev/peps/pep-0575/
>
> The main differences with respect to the pr
13 matches
Mail list logo
