From interstar at gmail.com Wed Feb 5 21:36:44 2014 From: interstar at gmail.com (phil jones) Date: Wed, 5 Feb 2014 18:36:44 -0200 Subject: [Idle-dev] The Future of Python Message-ID: Interesting video : https://www.youtube.com/watch?v=d1a4Jbjc-vU From guido at python.org Thu Feb 6 18:19:44 2014 From: guido at python.org (Guido van Rossum) Date: Thu, 6 Feb 2014 09:19:44 -0800 Subject: [Idle-dev] The Future of Python In-Reply-To: References: Message-ID: Not just interesting. Super inspiring. I almost cried, and was going to propose to give my keynote slot at PyCon away to Jessica, but she's already got her own slot. :-) Awesome! On Wed, Feb 5, 2014 at 12:36 PM, phil jones wrote: > Interesting video : https://www.youtube.com/watch?v=d1a4Jbjc-vU > _______________________________________________ > IDLE-dev mailing list > IDLE-dev at python.org > https://mail.python.org/mailman/listinfo/idle-dev > -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bruce_Sherwood at ncsu.edu Thu Feb 6 19:31:45 2014 From: Bruce_Sherwood at ncsu.edu (Bruce Sherwood) Date: Thu, 6 Feb 2014 11:31:45 -0700 Subject: [Idle-dev] The Future of Python In-Reply-To: References: Message-ID: I was surprised that in talking about the future of Python Jessica didn't touch on what may be really crucial, which is the importance of being able to use Python in client-side browser programming. Running in a browser is of rapidly increasing importance and Python could easily get left behind. There exist multiple projects whose goal is to be able to compile Python to JavaScript to address this issue. It looks to me like Brython may be the best bet, in that it seems to be an active development with a small but growing community of interested parties. What do you think about this, Guido? I'll mention that with the aid of Steve Spicklemire VPython has been converted to be based on wxPython, which was vital in order to get off Carbon and onto Cocoa on the Mac, and which also makes it possible to use wxPython widgets with VPython 3D canvases. I'm happy to report that in the last six months there were nearly 50,000 downloads of VPython, and that it's now featured in four (soon to be five) computational physics textbooks. Inspired by VPython, with a big initial push from David Scherer, the originator of VPython, I'm developing GlowScript (glowscript.org) where you can write VPython-like 3D animations using WebGL, writing in JavaScript or CoffeeScript. A minimal program is the single-line program box() This program places a WebGL canvas in the window, displays a cube in the window, creates lights to illuminate the scene, places the camera so that the cube fills the window, and enables mouse interactions to zoom and rotate. You can of course control all of these elements, but there are lots of good defaults to get going easily. Needless to say writing WebGL programs with other tools is vastly more difficult. It's already the case that it's very nice to be able to send a URL in an email and have the recipient click that link to see a 3D animation rather than asking them to install Python and VPython. Here's a simple example that will run in WebGL-enabled browsers: http://www.glowscript.org/#/user/GlowScriptDemos/folder/Examples/program/Bounce-CoffeeScript Many more demo programs are available at glowscript.org. However: I don't like the syntax of JavaScript, especially for novice programmers, and even though CoffeeScript is more Pythonesque its syntax and use of white space is kind of quirky and, I judge, not good for novices. I would love to enable Python as one of the languages (indeed the major language) for novices and experts to write GlowScript programs. -------------- next part -------------- An HTML attachment was scrubbed... URL: From guido at python.org Thu Feb 6 20:31:48 2014 From: guido at python.org (Guido van Rossum) Date: Thu, 6 Feb 2014 11:31:48 -0800 Subject: [Idle-dev] The Future of Python In-Reply-To: References: Message-ID: On Thu, Feb 6, 2014 at 10:31 AM, Bruce Sherwood wrote: > I was surprised that in talking about the future of Python Jessica didn't > touch on what may be really crucial, which is the importance of being able > to use Python in client-side browser programming. Running in a browser is > of rapidly increasing importance and Python could easily get left behind. > There exist multiple projects whose goal is to be able to compile Python to > JavaScript to address this issue. It looks to me like Brython may be the > best bet, in that it seems to be an active development with a small but > growing community of interested parties. What do you think about this, > Guido? > I think this is a lost cause. Many very smart people have broken their heads against this particular wall. > I'll mention that with the aid of Steve Spicklemire VPython has been > converted to be based on wxPython, which was vital in order to get off > Carbon and onto Cocoa on the Mac, and which also makes it possible to use > wxPython widgets with VPython 3D canvases. I'm happy to report that in the > last six months there were nearly 50,000 downloads of VPython, and that > it's now featured in four (soon to be five) computational physics textbooks. > That's awesome! > Inspired by VPython, with a big initial push from David Scherer, the > originator of VPython, I'm developing GlowScript (glowscript.org) where > you can write VPython-like 3D animations using WebGL, writing in JavaScript > or CoffeeScript. A minimal program is the single-line program > > box() > > This program places a WebGL canvas in the window, displays a cube in the > window, creates lights to illuminate the scene, places the camera so that > the cube fills the window, and enables mouse interactions to zoom and > rotate. You can of course control all of these elements, but there are lots > of good defaults to get going easily. Needless to say writing WebGL > programs with other tools is vastly more difficult. > > It's already the case that it's very nice to be able to send a URL in an > email and have the recipient click that link to see a 3D animation rather > than asking them to install Python and VPython. Here's a simple example > that will run in WebGL-enabled browsers: > > > http://www.glowscript.org/#/user/GlowScriptDemos/folder/Examples/program/Bounce-CoffeeScript > > Many more demo programs are available at glowscript.org. > > However: I don't like the syntax of JavaScript, especially for novice > programmers, and even though CoffeeScript is more Pythonesque its syntax > and use of white space is kind of quirky and, I judge, not good for > novices. I would love to enable Python as one of the languages (indeed the > major language) for novices and experts to write GlowScript programs. > Agreed that CoffeeScript is not newbie-friendly. But browsers have been even more unfriendly to running Python than mobile platforms. At least for the latter we have Kivy. -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: From ether.joe at gmail.com Fri Feb 7 08:57:59 2014 From: ether.joe at gmail.com (Sean Felipe Wolfe) Date: Thu, 6 Feb 2014 23:57:59 -0800 Subject: [Idle-dev] The Future of Python In-Reply-To: References: Message-ID: IDLE!!!!! We are starting up a partnership with a community center here in Oakland, CA, starting kids up with programmming. We're starting with Logo (yay, Logo!) and transitioning to Python with the turtle module. We've been using IDLE on Linux and also a Raspberry Pi. So far, so good! I for one am ecstatic about IDLE. It has a warm place in my heart. I should set aside a few hours a week to help out with it. Anyhow great video, thanks for the link! On Thu, Feb 6, 2014 at 11:31 AM, Guido van Rossum wrote: > On Thu, Feb 6, 2014 at 10:31 AM, Bruce Sherwood > wrote: >> >> I was surprised that in talking about the future of Python Jessica didn't >> touch on what may be really crucial, which is the importance of being able >> to use Python in client-side browser programming. Running in a browser is of >> rapidly increasing importance and Python could easily get left behind. There >> exist multiple projects whose goal is to be able to compile Python to >> JavaScript to address this issue. It looks to me like Brython may be the >> best bet, in that it seems to be an active development with a small but >> growing community of interested parties. What do you think about this, >> Guido? > > > I think this is a lost cause. Many very smart people have broken their heads > against this particular wall. > >> >> I'll mention that with the aid of Steve Spicklemire VPython has been >> converted to be based on wxPython, which was vital in order to get off >> Carbon and onto Cocoa on the Mac, and which also makes it possible to use >> wxPython widgets with VPython 3D canvases. I'm happy to report that in the >> last six months there were nearly 50,000 downloads of VPython, and that it's >> now featured in four (soon to be five) computational physics textbooks. > > > That's awesome! > >> >> Inspired by VPython, with a big initial push from David Scherer, the >> originator of VPython, I'm developing GlowScript (glowscript.org) where you >> can write VPython-like 3D animations using WebGL, writing in JavaScript or >> CoffeeScript. A minimal program is the single-line program >> >> box() >> >> This program places a WebGL canvas in the window, displays a cube in the >> window, creates lights to illuminate the scene, places the camera so that >> the cube fills the window, and enables mouse interactions to zoom and >> rotate. You can of course control all of these elements, but there are lots >> of good defaults to get going easily. Needless to say writing WebGL programs >> with other tools is vastly more difficult. >> >> It's already the case that it's very nice to be able to send a URL in an >> email and have the recipient click that link to see a 3D animation rather >> than asking them to install Python and VPython. Here's a simple example that >> will run in WebGL-enabled browsers: >> >> >> http://www.glowscript.org/#/user/GlowScriptDemos/folder/Examples/program/Bounce-CoffeeScript >> >> Many more demo programs are available at glowscript.org. >> >> However: I don't like the syntax of JavaScript, especially for novice >> programmers, and even though CoffeeScript is more Pythonesque its syntax and >> use of white space is kind of quirky and, I judge, not good for novices. I >> would love to enable Python as one of the languages (indeed the major >> language) for novices and experts to write GlowScript programs. > > > Agreed that CoffeeScript is not newbie-friendly. But browsers have been even > more unfriendly to running Python than mobile platforms. At least for the > latter we have Kivy. > > -- > --Guido van Rossum (python.org/~guido) > > _______________________________________________ > IDLE-dev mailing list > IDLE-dev at python.org > https://mail.python.org/mailman/listinfo/idle-dev > -- A musician must make music, an artist must paint, a poet must write, if he is to be ultimately at peace with himself. - Abraham Maslow From interstar at gmail.com Sat Feb 8 00:40:03 2014 From: interstar at gmail.com (phil jones) Date: Fri, 7 Feb 2014 21:40:03 -0200 Subject: [Idle-dev] The Future of Python In-Reply-To: References: Message-ID: Just putting a couple of thoughts / questions out to the community here : The impression I get about IDLE is that it's a bit of an embarrassment. (Possibly because of tk). Everyone accepts it's substandard. But no-one seems to want it to grow into something else (eg. a full IDE, something more like PythonCard / VisualBasic / Processing). Maybe IDLE is deprecated and the hope is it will die quietly. But if that IS the plan, then it would be nice to have it stated somewhere so that we can stop thinking of it as the "official" default IDE for Python and periodically wondering whether we should try to resuscitate it. And maybe focus our contributions on a project like VPython etc. instead. Bluntly, is IDLE meant to be getting good or to be going away? I don't know. And I can't find out by reading python.org or this mailing list. It feels like this ambiguity isn't only bad for IDLE, but might be lying behind the issues Jessica refers to. As well as a python programmer, I'm a digital artist so I've been doing a fair amount with Processing in the last few years. It's incredible to me that a language as officiously unpleasant and hostile to beginners as Java has managed to become the preferred choice for non-technical artists who want to do cool stuff with graphics, sound and physical computing. How did that happen? It's a niche that would have been perfect for Python. And should have been well within its grasp. As far as I can tell, Processing's success is a combination of beginner-oriented IDE and comprehensive library in a single convenient download. Those are two virtues that Python has been able to boast for 15 years. And yet ... somehow ... the package didn't quite add up. IDLE wasn't quite straight-forward enough, and Python's included batteries didn't include OpenGL, which has become the standard for all the cool graphics. When I've suggested on IDLE-dev that IDLE could evolve to be more like Processing, that idea has been generally rejected on the grounds that IDLE is meant to be a "basic editor". But what's a basic editor? One which never evolves, innovates or adds new functionality? No one is going to be motivated to work on IDLE if it's not allowed to grow into anything new. At the same time, Jessica asks for Python to be a good beginner's development environment, straight out of the box. If IDLE isn't the solution to that requirement then what is? That seems the challenge here : either IDLE gets good for beginners who want to do cool stuff. Which means maybe taking inspiration from Processing. Or HyperCard. Or really exotic things like LightTable (http://www.chris-granger.com/lighttable/) Or perhaps the python community and especially the python.org site, should just drop it and start promoting (and offering easy beginner downloads for) comprehensive packages like VPython, IPython, Enthought etc. Phil On 7 February 2014 05:57, Sean Felipe Wolfe wrote: > IDLE!!!!! > > We are starting up a partnership with a community center here in > Oakland, CA, starting kids up with programmming. We're starting with > Logo (yay, Logo!) and transitioning to Python with the turtle module. > We've been using IDLE on Linux and also a Raspberry Pi. So far, so > good! > > I for one am ecstatic about IDLE. It has a warm place in my heart. I > should set aside a few hours a week to help out with it. > > Anyhow great video, thanks for the link! > > On Thu, Feb 6, 2014 at 11:31 AM, Guido van Rossum wrote: >> On Thu, Feb 6, 2014 at 10:31 AM, Bruce Sherwood >> wrote: >>> >>> I was surprised that in talking about the future of Python Jessica didn't >>> touch on what may be really crucial, which is the importance of being able >>> to use Python in client-side browser programming. Running in a browser is of >>> rapidly increasing importance and Python could easily get left behind. There >>> exist multiple projects whose goal is to be able to compile Python to >>> JavaScript to address this issue. It looks to me like Brython may be the >>> best bet, in that it seems to be an active development with a small but >>> growing community of interested parties. What do you think about this, >>> Guido? >> >> >> I think this is a lost cause. Many very smart people have broken their heads >> against this particular wall. >> >>> >>> I'll mention that with the aid of Steve Spicklemire VPython has been >>> converted to be based on wxPython, which was vital in order to get off >>> Carbon and onto Cocoa on the Mac, and which also makes it possible to use >>> wxPython widgets with VPython 3D canvases. I'm happy to report that in the >>> last six months there were nearly 50,000 downloads of VPython, and that it's >>> now featured in four (soon to be five) computational physics textbooks. >> >> >> That's awesome! >> >>> >>> Inspired by VPython, with a big initial push from David Scherer, the >>> originator of VPython, I'm developing GlowScript (glowscript.org) where you >>> can write VPython-like 3D animations using WebGL, writing in JavaScript or >>> CoffeeScript. A minimal program is the single-line program >>> >>> box() >>> >>> This program places a WebGL canvas in the window, displays a cube in the >>> window, creates lights to illuminate the scene, places the camera so that >>> the cube fills the window, and enables mouse interactions to zoom and >>> rotate. You can of course control all of these elements, but there are lots >>> of good defaults to get going easily. Needless to say writing WebGL programs >>> with other tools is vastly more difficult. >>> >>> It's already the case that it's very nice to be able to send a URL in an >>> email and have the recipient click that link to see a 3D animation rather >>> than asking them to install Python and VPython. Here's a simple example that >>> will run in WebGL-enabled browsers: >>> >>> >>> http://www.glowscript.org/#/user/GlowScriptDemos/folder/Examples/program/Bounce-CoffeeScript >>> >>> Many more demo programs are available at glowscript.org. >>> >>> However: I don't like the syntax of JavaScript, especially for novice >>> programmers, and even though CoffeeScript is more Pythonesque its syntax and >>> use of white space is kind of quirky and, I judge, not good for novices. I >>> would love to enable Python as one of the languages (indeed the major >>> language) for novices and experts to write GlowScript programs. >> >> >> Agreed that CoffeeScript is not newbie-friendly. But browsers have been even >> more unfriendly to running Python than mobile platforms. At least for the >> latter we have Kivy. >> >> -- >> --Guido van Rossum (python.org/~guido) >> >> _______________________________________________ >> IDLE-dev mailing list >> IDLE-dev at python.org >> https://mail.python.org/mailman/listinfo/idle-dev >> > > > > -- > A musician must make music, an artist must paint, a poet must write, > if he is to be ultimately at peace with himself. > - Abraham Maslow > _______________________________________________ > IDLE-dev mailing list > IDLE-dev at python.org > https://mail.python.org/mailman/listinfo/idle-dev From gdsimoes87 at gmail.com Sat Feb 8 01:39:07 2014 From: gdsimoes87 at gmail.com (=?ISO-8859-1?Q?Guilherme_Sim=F5es?=) Date: Fri, 7 Feb 2014 22:39:07 -0200 Subject: [Idle-dev] The Future of Python In-Reply-To: References: Message-ID: I tried to improve IDLE for a little while and I believe the main problem is tk. It's a source of a lot of bugs and some weird behavior. On Fri, Feb 7, 2014 at 9:40 PM, phil jones wrote: > Just putting a couple of thoughts / questions out to the community here : > > The impression I get about IDLE is that it's a bit of an > embarrassment. (Possibly because of tk). Everyone accepts it's > substandard. But no-one seems to want it to grow into something else > (eg. a full IDE, something more like PythonCard / VisualBasic / > Processing). Maybe IDLE is deprecated and the hope is it will die > quietly. But if that IS the plan, then it would be nice to have it > stated somewhere so that we can stop thinking of it as the "official" > default IDE for Python and periodically wondering whether we should > try to resuscitate it. And maybe focus our contributions on a project > like VPython etc. instead. > > Bluntly, is IDLE meant to be getting good or to be going away? I don't > know. And I can't find out by reading python.org or this mailing list. > > It feels like this ambiguity isn't only bad for IDLE, but might be > lying behind the issues Jessica refers to. As well as a python > programmer, I'm a digital artist so I've been doing a fair amount with > Processing in the last few years. It's incredible to me that a > language as officiously unpleasant and hostile to beginners as Java > has managed to become the preferred choice for non-technical artists > who want to do cool stuff with graphics, sound and physical computing. > > How did that happen? It's a niche that would have been perfect for > Python. And should have been well within its grasp. As far as I can > tell, Processing's success is a combination of beginner-oriented IDE > and comprehensive library in a single convenient download. Those are > two virtues that Python has been able to boast for 15 years. And yet > ... somehow ... the package didn't quite add up. IDLE wasn't quite > straight-forward enough, and Python's included batteries didn't > include OpenGL, which has become the standard for all the cool > graphics. > > When I've suggested on IDLE-dev that IDLE could evolve to be more like > Processing, that idea has been generally rejected on the grounds that > IDLE is meant to be a "basic editor". But what's a basic editor? One > which never evolves, innovates or adds new functionality? No one is > going to be motivated to work on IDLE if it's not allowed to grow into > anything new. > > At the same time, Jessica asks for Python to be a good beginner's > development environment, straight out of the box. If IDLE isn't the > solution to that requirement then what is? > > That seems the challenge here : either IDLE gets good for beginners > who want to do cool stuff. Which means maybe taking inspiration from > Processing. Or HyperCard. Or really exotic things like LightTable > (http://www.chris-granger.com/lighttable/) Or perhaps the python > community and especially the python.org site, should just drop it and > start promoting (and offering easy beginner downloads for) > comprehensive packages like VPython, IPython, Enthought etc. > > Phil > > > > On 7 February 2014 05:57, Sean Felipe Wolfe wrote: > > IDLE!!!!! > > > > We are starting up a partnership with a community center here in > > Oakland, CA, starting kids up with programmming. We're starting with > > Logo (yay, Logo!) and transitioning to Python with the turtle module. > > We've been using IDLE on Linux and also a Raspberry Pi. So far, so > > good! > > > > I for one am ecstatic about IDLE. It has a warm place in my heart. I > > should set aside a few hours a week to help out with it. > > > > Anyhow great video, thanks for the link! > > > > On Thu, Feb 6, 2014 at 11:31 AM, Guido van Rossum > wrote: > >> On Thu, Feb 6, 2014 at 10:31 AM, Bruce Sherwood < > Bruce_Sherwood at ncsu.edu> > >> wrote: > >>> > >>> I was surprised that in talking about the future of Python Jessica > didn't > >>> touch on what may be really crucial, which is the importance of being > able > >>> to use Python in client-side browser programming. Running in a browser > is of > >>> rapidly increasing importance and Python could easily get left behind. > There > >>> exist multiple projects whose goal is to be able to compile Python to > >>> JavaScript to address this issue. It looks to me like Brython may be > the > >>> best bet, in that it seems to be an active development with a small but > >>> growing community of interested parties. What do you think about this, > >>> Guido? > >> > >> > >> I think this is a lost cause. Many very smart people have broken their > heads > >> against this particular wall. > >> > >>> > >>> I'll mention that with the aid of Steve Spicklemire VPython has been > >>> converted to be based on wxPython, which was vital in order to get off > >>> Carbon and onto Cocoa on the Mac, and which also makes it possible to > use > >>> wxPython widgets with VPython 3D canvases. I'm happy to report that in > the > >>> last six months there were nearly 50,000 downloads of VPython, and > that it's > >>> now featured in four (soon to be five) computational physics textbooks. > >> > >> > >> That's awesome! > >> > >>> > >>> Inspired by VPython, with a big initial push from David Scherer, the > >>> originator of VPython, I'm developing GlowScript (glowscript.org) > where you > >>> can write VPython-like 3D animations using WebGL, writing in > JavaScript or > >>> CoffeeScript. A minimal program is the single-line program > >>> > >>> box() > >>> > >>> This program places a WebGL canvas in the window, displays a cube in > the > >>> window, creates lights to illuminate the scene, places the camera so > that > >>> the cube fills the window, and enables mouse interactions to zoom and > >>> rotate. You can of course control all of these elements, but there are > lots > >>> of good defaults to get going easily. Needless to say writing WebGL > programs > >>> with other tools is vastly more difficult. > >>> > >>> It's already the case that it's very nice to be able to send a URL in > an > >>> email and have the recipient click that link to see a 3D animation > rather > >>> than asking them to install Python and VPython. Here's a simple > example that > >>> will run in WebGL-enabled browsers: > >>> > >>> > >>> > http://www.glowscript.org/#/user/GlowScriptDemos/folder/Examples/program/Bounce-CoffeeScript > >>> > >>> Many more demo programs are available at glowscript.org. > >>> > >>> However: I don't like the syntax of JavaScript, especially for novice > >>> programmers, and even though CoffeeScript is more Pythonesque its > syntax and > >>> use of white space is kind of quirky and, I judge, not good for > novices. I > >>> would love to enable Python as one of the languages (indeed the major > >>> language) for novices and experts to write GlowScript programs. > >> > >> > >> Agreed that CoffeeScript is not newbie-friendly. But browsers have been > even > >> more unfriendly to running Python than mobile platforms. At least for > the > >> latter we have Kivy. > >> > >> -- > >> --Guido van Rossum (python.org/~guido) > >> > >> _______________________________________________ > >> IDLE-dev mailing list > >> IDLE-dev at python.org > >> https://mail.python.org/mailman/listinfo/idle-dev > >> > > > > > > > > -- > > A musician must make music, an artist must paint, a poet must write, > > if he is to be ultimately at peace with himself. > > - Abraham Maslow > > _______________________________________________ > > IDLE-dev mailing list > > IDLE-dev at python.org > > https://mail.python.org/mailman/listinfo/idle-dev > _______________________________________________ > IDLE-dev mailing list > IDLE-dev at python.org > https://mail.python.org/mailman/listinfo/idle-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From forman.simon at gmail.com Sat Feb 8 03:12:22 2014 From: forman.simon at gmail.com (Simon Forman) Date: Fri, 7 Feb 2014 18:12:22 -0800 Subject: [Idle-dev] The Future of Python In-Reply-To: References: Message-ID: My $0.02 regarding IDLE (and Tk): I am a professional programmer who has been programming primarily in Python (Thank you GVR et. al.!) for nearly a decade. IDLE has been and remains the only editor I want to use. It has its warts and idiosyncrasies, there are things I would love to see (IPython integration is awesome!) But every other editor I've ever tried (and I've tried pretty much all of them) has left me cold. IDLE is not an embarrassment, it is not substandard, and it is certainly not deprecated. It doesn't need to be grown into "a full IDE". Thank you. (Also, TCL/Tk is awesome.) ~Simon On 2/7/14, phil jones wrote: > Just putting a couple of thoughts / questions out to the community here : > > The impression I get about IDLE is that it's a bit of an > embarrassment. (Possibly because of tk). Everyone accepts it's > substandard. But no-one seems to want it to grow into something else > (eg. a full IDE, something more like PythonCard / VisualBasic / > Processing). Maybe IDLE is deprecated and the hope is it will die > quietly. But if that IS the plan, then it would be nice to have it > stated somewhere so that we can stop thinking of it as the "official" > default IDE for Python and periodically wondering whether we should > try to resuscitate it. And maybe focus our contributions on a project > like VPython etc. instead. > > Bluntly, is IDLE meant to be getting good or to be going away? I don't > know. And I can't find out by reading python.org or this mailing list. > > It feels like this ambiguity isn't only bad for IDLE, but might be > lying behind the issues Jessica refers to. As well as a python > programmer, I'm a digital artist so I've been doing a fair amount with > Processing in the last few years. It's incredible to me that a > language as officiously unpleasant and hostile to beginners as Java > has managed to become the preferred choice for non-technical artists > who want to do cool stuff with graphics, sound and physical computing. > > How did that happen? It's a niche that would have been perfect for > Python. And should have been well within its grasp. As far as I can > tell, Processing's success is a combination of beginner-oriented IDE > and comprehensive library in a single convenient download. Those are > two virtues that Python has been able to boast for 15 years. And yet > ... somehow ... the package didn't quite add up. IDLE wasn't quite > straight-forward enough, and Python's included batteries didn't > include OpenGL, which has become the standard for all the cool > graphics. > > When I've suggested on IDLE-dev that IDLE could evolve to be more like > Processing, that idea has been generally rejected on the grounds that > IDLE is meant to be a "basic editor". But what's a basic editor? One > which never evolves, innovates or adds new functionality? No one is > going to be motivated to work on IDLE if it's not allowed to grow into > anything new. > > At the same time, Jessica asks for Python to be a good beginner's > development environment, straight out of the box. If IDLE isn't the > solution to that requirement then what is? > > That seems the challenge here : either IDLE gets good for beginners > who want to do cool stuff. Which means maybe taking inspiration from > Processing. Or HyperCard. Or really exotic things like LightTable > (http://www.chris-granger.com/lighttable/) Or perhaps the python > community and especially the python.org site, should just drop it and > start promoting (and offering easy beginner downloads for) > comprehensive packages like VPython, IPython, Enthought etc. > > Phil > > > > On 7 February 2014 05:57, Sean Felipe Wolfe wrote: >> IDLE!!!!! >> >> We are starting up a partnership with a community center here in >> Oakland, CA, starting kids up with programmming. We're starting with >> Logo (yay, Logo!) and transitioning to Python with the turtle module. >> We've been using IDLE on Linux and also a Raspberry Pi. So far, so >> good! >> >> I for one am ecstatic about IDLE. It has a warm place in my heart. I >> should set aside a few hours a week to help out with it. >> >> Anyhow great video, thanks for the link! >> >> On Thu, Feb 6, 2014 at 11:31 AM, Guido van Rossum >> wrote: >>> On Thu, Feb 6, 2014 at 10:31 AM, Bruce Sherwood >>> >>> wrote: >>>> >>>> I was surprised that in talking about the future of Python Jessica >>>> didn't >>>> touch on what may be really crucial, which is the importance of being >>>> able >>>> to use Python in client-side browser programming. Running in a browser >>>> is of >>>> rapidly increasing importance and Python could easily get left behind. >>>> There >>>> exist multiple projects whose goal is to be able to compile Python to >>>> JavaScript to address this issue. It looks to me like Brython may be >>>> the >>>> best bet, in that it seems to be an active development with a small but >>>> growing community of interested parties. What do you think about this, >>>> Guido? >>> >>> >>> I think this is a lost cause. Many very smart people have broken their >>> heads >>> against this particular wall. >>> >>>> >>>> I'll mention that with the aid of Steve Spicklemire VPython has been >>>> converted to be based on wxPython, which was vital in order to get off >>>> Carbon and onto Cocoa on the Mac, and which also makes it possible to >>>> use >>>> wxPython widgets with VPython 3D canvases. I'm happy to report that in >>>> the >>>> last six months there were nearly 50,000 downloads of VPython, and that >>>> it's >>>> now featured in four (soon to be five) computational physics textbooks. >>> >>> >>> That's awesome! >>> >>>> >>>> Inspired by VPython, with a big initial push from David Scherer, the >>>> originator of VPython, I'm developing GlowScript (glowscript.org) where >>>> you >>>> can write VPython-like 3D animations using WebGL, writing in JavaScript >>>> or >>>> CoffeeScript. A minimal program is the single-line program >>>> >>>> box() >>>> >>>> This program places a WebGL canvas in the window, displays a cube in >>>> the >>>> window, creates lights to illuminate the scene, places the camera so >>>> that >>>> the cube fills the window, and enables mouse interactions to zoom and >>>> rotate. You can of course control all of these elements, but there are >>>> lots >>>> of good defaults to get going easily. Needless to say writing WebGL >>>> programs >>>> with other tools is vastly more difficult. >>>> >>>> It's already the case that it's very nice to be able to send a URL in >>>> an >>>> email and have the recipient click that link to see a 3D animation >>>> rather >>>> than asking them to install Python and VPython. Here's a simple example >>>> that >>>> will run in WebGL-enabled browsers: >>>> >>>> >>>> http://www.glowscript.org/#/user/GlowScriptDemos/folder/Examples/program/Bounce-CoffeeScript >>>> >>>> Many more demo programs are available at glowscript.org. >>>> >>>> However: I don't like the syntax of JavaScript, especially for novice >>>> programmers, and even though CoffeeScript is more Pythonesque its syntax >>>> and >>>> use of white space is kind of quirky and, I judge, not good for novices. >>>> I >>>> would love to enable Python as one of the languages (indeed the major >>>> language) for novices and experts to write GlowScript programs. >>> >>> >>> Agreed that CoffeeScript is not newbie-friendly. But browsers have been >>> even >>> more unfriendly to running Python than mobile platforms. At least for >>> the >>> latter we have Kivy. >>> >>> -- >>> --Guido van Rossum (python.org/~guido) >>> >>> _______________________________________________ >>> IDLE-dev mailing list >>> IDLE-dev at python.org >>> https://mail.python.org/mailman/listinfo/idle-dev >>> >> >> >> >> -- >> A musician must make music, an artist must paint, a poet must write, >> if he is to be ultimately at peace with himself. >> - Abraham Maslow >> _______________________________________________ >> IDLE-dev mailing list >> IDLE-dev at python.org >> https://mail.python.org/mailman/listinfo/idle-dev > _______________________________________________ > IDLE-dev mailing list > IDLE-dev at python.org > https://mail.python.org/mailman/listinfo/idle-dev > -- http://twitter.com/SimonForman My blog: http://firequery.blogspot.com/ Also my blog: http://calroc.blogspot.com/ "The history of mankind for the last four centuries is rather like that of an imprisoned sleeper, stirring clumsily and uneasily while the prison that restrains and shelters him catches fire, not waking but incorporating the crackling and warmth of the fire with ancient and incongruous dreams, than like that of a man consciously awake to danger and opportunity." --H. P. Wells, "A Short History of the World" From guido at python.org Sat Feb 8 03:20:45 2014 From: guido at python.org (Guido van Rossum) Date: Fri, 7 Feb 2014 18:20:45 -0800 Subject: [Idle-dev] The Future of Python In-Reply-To: References: Message-ID: I suspect that how you view IDLE and Tk may have a lot to do with the platform you're using, i.e. Mac or Win. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bruce_Sherwood at ncsu.edu Sat Feb 8 07:41:49 2014 From: Bruce_Sherwood at ncsu.edu (Bruce Sherwood) Date: Fri, 7 Feb 2014 23:41:49 -0700 Subject: [Idle-dev] The Future of Python In-Reply-To: References: Message-ID: I too use only IDLE (in its VIDLE forked version) when writing Python programs, as is the case also of the many thousands of students in our intro physics curriculum, whether on Windows (about 80% of the users) or Mac (about 15%, the remaining 5% being Linux). I have the strong impression, including from Jessica's talk, that IDLE is very objectionable to experienced programmers, and I would say simply that they shouldn't use it. There are plenty of sophisticated IDEs around; I myself use Eclipse for development work on VPython (the C++ part) and GlowScript (JavaScript). For the nonexpert programmers I deal with, and for that matter my own Python programming, IDLE is entirely adequate and appropriate. It would be extremely unfortunate if IDLE were changed to cater to expert programmers, leaving the novices and nonexperts in the lurch. My only concern about IDLE is that there seems to be no clear path for getting improvements into the distributed version of IDLE, which is why the VPython installer installs a version which for clarity is called VIDLE. VIDLE includes important improvements made by Guilherme Polo in a 2009 GSOC project for which I was a mentor, but despite it being a Python-approved project at that time there was no way for the improvements to get into the code base. I'm very pleased to see recent serious work on IDLE, and I think most of Polo's work has been salvaged. I very much hope that these improvements can be incorporated into the distributed IDLE, in which case I'll stop packing VIDLE with VPython. Bruce -------------- next part -------------- An HTML attachment was scrubbed... URL: From ether.joe at gmail.com Sat Feb 8 07:57:34 2014 From: ether.joe at gmail.com (Sean Felipe Wolfe) Date: Fri, 7 Feb 2014 22:57:34 -0800 Subject: [Idle-dev] The Future of Python In-Reply-To: References: Message-ID: On Fri, Feb 7, 2014 at 10:41 PM, Bruce Sherwood wrote: > My only concern about IDLE is that there seems to be no clear path for > getting improvements into the distributed version of IDLE, Yeah this was a bit discouraging to me in the past -- that it didn't seem like good fixes were getting onto the main distribution. IIRC there are a lot of good bits in the fork. It's been a little while but I remember us talking about some useful pieces like having any keystroke take you back to the interpreter prompt, regardless of where you are reading, and having the arrow up/down keys act as alt-p alt-n . Those would be great imo. How can I help??!!! Grab some bugs from the bug tracker? Is there somebody quarterbacking IDLE dev these days? From ether.joe at gmail.com Sat Feb 8 08:10:08 2014 From: ether.joe at gmail.com (Sean Felipe Wolfe) Date: Fri, 7 Feb 2014 23:10:08 -0800 Subject: [Idle-dev] The Future of Python In-Reply-To: References: Message-ID: On Fri, Feb 7, 2014 at 10:57 PM, Sean Felipe Wolfe wrote: > IIRC there are a lot of good bits in the fork. Er, I meant to say, 'the fork of IDLE called IDLEX' . Did we get any of those in? That would be http://idlex.sourceforge.net/ From Bruce_Sherwood at ncsu.edu Sat Feb 8 08:42:04 2014 From: Bruce_Sherwood at ncsu.edu (Bruce Sherwood) Date: Sat, 8 Feb 2014 00:42:04 -0700 Subject: [Idle-dev] The Future of Python In-Reply-To: References: Message-ID: I'll mention that for my own purposes, and those of my students, the interpreter prompt is of absolutely no interest whatsoever. All of our work is done at the program level, in the editor, not at the interpreter prompt. For us the Python Shell is used only for print() output. So I don't care what bells and whistles are added to the Python Shell to suit the needs of experts. Bruce -------------- next part -------------- An HTML attachment was scrubbed... URL: From tjreedy at udel.edu Sat Feb 8 13:22:03 2014 From: tjreedy at udel.edu (Terry Reedy) Date: Sat, 08 Feb 2014 07:22:03 -0500 Subject: [Idle-dev] The Future of Idle Message-ID: Let me try to respond coherently to questions and comments from multiple posts. 1. While Idle is not maintained as well as I and some people would wish, it is untrue to say that 'Idle is not maintained'. It was not true a year ago, 6 months ago, and is not now. 2. In recent years, tkinter has been less well maintained than Idle and pretty much nothing had been done for awhile until Serhiy Storchaka dug into it about 6 months ago. He has greatly expanded the tk/tkinter test suite and fixed several bugs, including some that initially manifested as 'Idle bugs'. 3. For several years, I believe, K.B.Kaiser was the Idle 'quarterback', but he moved on to PSF work a few years ago and has done little Idle work since. At the moment, I seem to be the person spending the most time on Idle. More help is needed. KBK applied patches to whatever versions he felt appropriate. Development after him he stopped working on Idle was hobbled by uncertainty, debate, and disagreement about whether other developers could do the same, and with what patches. Since PEP 434 was approved last March, working on Idle has been more pleasant. Most patches are applied to all current versions without fuss. There currently is no one in charge of a 'grand plan'. PEP 434 sidestepped the issue of 'approval' for big changes. For the rest of Python and the stdlib, big changes normally start with a pre-PEP or discussion on pydev or python-ideas. 4. My personal priorities are 'crash' issues, other fixes and improvements that benefit me, and continuing development on a test suite that should make it easier to patch Idle without introducing too many regressions. There is no developer guide for Idle. Idlelib currently comprises about 70 modules, mostly one class per file, with CamelCase.py names matching the class names. For a couple a reasons, I would like to consolidate some files and rename the rest to lowercase names. However, I would not think of doing so until *all* .py files are imported by the test suite, to verify that all imports within each file work continue to work after changes. I am not sure who would have be involved in approving such a proposal. My personal dream for Idle (in 3.5) is to have multiple multi-tabbed panes. I have a wide-screen monitor and I sometimes work with three Idle windows open side by side. For instance, when working on Idle I might have a Shell window, an Editor window for idlelib/xyz.py, and another Editor window for idle_test/test_xyz.py. Sometimes I would like to be able to switch the latter two to abc.py tabs without closing the xyz tabs. I presume others might do the same with their own code and test files. I am aware that there is a patch for one multi-tabbed pane. Once that is working, adding an option to have two or three such panes should be feasible. 5. Sean asked "How can I help??!!! Grab some bugs from the bug tracker?" In essence, yes. In theory, every bug should be verified on Windows, Linux, and Mac with (currently) 2.7, 3.3, and 3.4. Ditto for patches. Some issues probably need more discussion of options for action. Also look at the developer guide on the site and the core-mentorship list. -- Terry Jan Reedy From vatroslavsuton at aim.com Sun Feb 9 10:33:06 2014 From: vatroslavsuton at aim.com (Vatroslav Suton) Date: Sun, 9 Feb 2014 04:33:06 -0500 (EST) Subject: [Idle-dev] The Future of Python In-Reply-To: References: Message-ID: <8D0F391127AD91B-28C0-11BA0@webmail-m250.sysops.aol.com> porting python to javascript, np Vatroslav Suton vatroslavsuton at aim.com -----Original Message----- From: Bruce Sherwood To: Sean Felipe Wolfe Cc: sforman ; idle ; Guido van Rossum Sent: Sat, Feb 8, 2014 9:36 am Subject: Re: [Idle-dev] The Future of Python I'll mention that for my own purposes, and those of my students, the interpreter prompt is of absolutely no interest whatsoever. All of our work is done at the program level, in the editor, not at the interpreter prompt. For us the Python Shell is used only for print() output. So I don't care what bells and whistles are added to the Python Shell to suit the needs of experts. Bruce _______________________________________________ IDLE-dev mailing list IDLE-dev at python.org https://mail.python.org/mailman/listinfo/idle-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.james.barry at gmail.com Mon Feb 10 11:05:38 2014 From: paul.james.barry at gmail.com (Paul Barry) Date: Mon, 10 Feb 2014 10:05:38 +0000 Subject: [Idle-dev] The Future of Python In-Reply-To: <8D0F391127AD91B-28C0-11BA0@webmail-m250.sysops.aol.com> References: <8D0F391127AD91B-28C0-11BA0@webmail-m250.sysops.aol.com> Message-ID: I used IDLE extensively in the first edition of "Head First Python". For the second edition (which is now very, very late - but that's another story), I took the time to take a look at a bunch of other Python IDEs and, after working with a lot of them, have ended up coming back to IDLE (and have continued to use it in the second edition of my book). IDLE has recently received some development love (helped, I think, by all the activity around 3.4), which has improved some of its stability and usage issues, and it is still the best tool (IMHO) when introducing students to Python for the first time. Those who continue the labor of love which helps to improve IDLE are to be commended. The Python world would be a much poorer place if IDLE wasn't part of it. Paul. On 9 February 2014 09:33, Vatroslav Suton wrote: > porting python to javascript, np > Vatroslav Suton > vatroslavsuton at aim.com > -----Original Message----- > From: Bruce Sherwood > To: Sean Felipe Wolfe > Cc: sforman ; idle ; Guido van > Rossum > Sent: Sat, Feb 8, 2014 9:36 am > Subject: Re: [Idle-dev] The Future of Python > > I'll mention that for my own purposes, and those of my students, the > interpreter prompt is of absolutely no interest whatsoever. All of our work > is done at the program level, in the editor, not at the interpreter prompt. > For us the Python Shell is used only for print() output. So I don't care > what bells and whistles are added to the Python Shell to suit the needs of > experts. > > Bruce > > _______________________________________________ > IDLE-dev mailing listIDLE-dev at python.orghttps://mail.python.org/mailman/listinfo/idle-dev > > > _______________________________________________ > IDLE-dev mailing list > IDLE-dev at python.org > https://mail.python.org/mailman/listinfo/idle-dev > > -- Paul Barry, w: http://paulbarry.itcarlow.ie - e: paul.barry at itcarlow.ie Lecturer, Computer Networking: Institute of Technology, Carlow, Ireland. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tjreedy at udel.edu Mon Feb 10 12:33:05 2014 From: tjreedy at udel.edu (Terry Reedy) Date: Mon, 10 Feb 2014 06:33:05 -0500 Subject: [Idle-dev] The Future of Python In-Reply-To: References: <8D0F391127AD91B-28C0-11BA0@webmail-m250.sysops.aol.com> Message-ID: On 2/10/2014 5:05 AM, Paul Barry wrote: > I used IDLE extensively in the first edition of "Head First Python". For > the second edition (which is now very, very late - but that's another > story), I took the time to take a look at a bunch of other Python IDEs > and, after working with a lot of them, have ended up coming back to IDLE > (and have continued to use it in the second edition of my book). IDLE > has recently received some development love (helped, I think, by all the > activity around 3.4), which has improved some of its stability and usage > issues, and it is still the best tool (IMHO) when introducing students > to Python for the first time. > > Those who continue the labor of love which helps to improve IDLE are to > be commended. The Python world would be a much poorer place if IDLE > wasn't part of it. Thank you Paul, and others who have given positive feedback on Idle in this thread. The negativity about Idle has previously been louder than such positive feedback and a bit dispiriting. It is helpful to know that someone besides me benefits from the improvements I make. -- Terry Jan Reedy From glyph at twistedmatrix.com Tue Feb 11 00:07:45 2014 From: glyph at twistedmatrix.com (Glyph) Date: Mon, 10 Feb 2014 17:07:45 -0600 Subject: [Idle-dev] The Future of Python In-Reply-To: References: Message-ID: <875FC0C9-F9A6-49FD-9915-6DF08F54DF44@twistedmatrix.com> On Feb 6, 2014, at 1:31 PM, Guido van Rossum wrote: > On Thu, Feb 6, 2014 at 10:31 AM, Bruce Sherwood wrote: > I was surprised that in talking about the future of Python Jessica didn't touch on what may be really crucial, which is the importance of being able to use Python in client-side browser programming. Running in a browser is of rapidly increasing importance and Python could easily get left behind. There exist multiple projects whose goal is to be able to compile Python to JavaScript to address this issue. It looks to me like Brython may be the best bet, in that it seems to be an active development with a small but growing community of interested parties. What do you think about this, Guido? > > I think this is a lost cause. Many very smart people have broken their heads against this particular wall. Personally I'm keeping an eye on Brython, but it is basically non-functional from the perspective of running any existing Python code, even code written from scratch specifically to be portable to Brython. PyJS, on the other hand, while somewhat clunky, I've managed to get existing Python libs up and running on with a relatively modest amount of hackery. Nevertheless, Bruce, I would encourage you to contribute to one of these projects; maybe make Brython's parser a bit more of a serious contender, since its way of integrating with JavaScript and HTML is much more sensible, even if it's not really "python" in any meaningful sense yet ;-). Notwithstanding most of python-dev's disinterest (including Guido!), I agree that this is critical to Python's long-term survival. And let me make a halfhearted attempt to bring this on-topic: it would be absolutely amazing if IDLE actually had a plugin to allow you to write some HTML and some CSS and stuff so that new users could easily get up and running with something that looks "real" to modern students (i.e. a web page that they can share, not just some turtle graphics on a canvas). -glyph -------------- next part -------------- An HTML attachment was scrubbed... URL: From guido at python.org Tue Feb 11 00:19:00 2014 From: guido at python.org (Guido van Rossum) Date: Mon, 10 Feb 2014 15:19:00 -0800 Subject: [Idle-dev] The Future of Python In-Reply-To: <875FC0C9-F9A6-49FD-9915-6DF08F54DF44@twistedmatrix.com> References: <875FC0C9-F9A6-49FD-9915-6DF08F54DF44@twistedmatrix.com> Message-ID: On Mon, Feb 10, 2014 at 3:07 PM, Glyph wrote: > > On Feb 6, 2014, at 1:31 PM, Guido van Rossum wrote: > > On Thu, Feb 6, 2014 at 10:31 AM, Bruce Sherwood > wrote: > >> I was surprised that in talking about the future of Python Jessica didn't >> touch on what may be really crucial, which is the importance of being able >> to use Python in client-side browser programming. Running in a browser is >> of rapidly increasing importance and Python could easily get left behind. >> There exist multiple projects whose goal is to be able to compile Python to >> JavaScript to address this issue. It looks to me like Brython may be the >> best bet, in that it seems to be an active development with a small but >> growing community of interested parties. What do you think about this, >> Guido? >> > > I think this is a lost cause. Many very smart people have broken their > heads against this particular wall. > > > Personally I'm keeping an eye on Brython, but it is basically > non-functional from the perspective of running *any* existing Python > code, even code written from scratch specifically to be portable to > Brython. PyJS, on the other hand, while somewhat clunky, I've managed to > get existing Python libs up and running on with a relatively modest amount > of hackery. > > Nevertheless, Bruce, I would encourage you to contribute to one of these > projects; maybe make Brython's parser a bit more of a serious contender, > since its way of integrating with JavaScript and HTML is much more > sensible, even if it's not really "python" in any meaningful sense yet ;-). > Notwithstanding most of python-dev's disinterest (including Guido!), I > agree that this is critical to Python's long-term survival. > Then we're doomed, because this is entirely political (the companies making browsers must want to do it). > And let me make a halfhearted attempt to bring this on-topic: it would be > absolutely *amazing* if IDLE actually had a plugin to allow you to write > some HTML and some CSS and stuff so that new users could easily get up and > running with something that looks "real" to modern students (i.e. a web > page that they can share, not just some turtle graphics on a canvas). > > -glyph > > -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: From glyph at twistedmatrix.com Tue Feb 11 00:35:52 2014 From: glyph at twistedmatrix.com (Glyph) Date: Mon, 10 Feb 2014 17:35:52 -0600 Subject: [Idle-dev] The Future of Python In-Reply-To: References: <875FC0C9-F9A6-49FD-9915-6DF08F54DF44@twistedmatrix.com> Message-ID: <07956762-ADF3-439A-9916-50C4253F54DC@twistedmatrix.com> On Feb 10, 2014, at 5:19 PM, Guido van Rossum wrote: > Then we're doomed, because this is entirely political (the companies making browsers must want to do it). Not at all. There are a number of promising proofs of concept, demonstrating different aspects of this problem: Pyjamas, the PyJS fork of Pyjamas, Skulpt, Empythoned (which actually compiles CPython to run in the browser with surprisingly reasonable performance!), Brython, and PyPy's now defunct JS backend to name a few. With source maps, it's even possible to use native JavaScript debugging and profiling tools on Browser-hosted Python. The political problem is entirely based around getting the various interested parties together and trying to hammer out some kind of common core that they can all get running and contribute to, rather than duplicating tons and tons of effort and only ever getting to a 60% solution. Browser vendors seem perfectly happy to treat JavaScript as a compilation target; efforts like ASM.JS are in fact trying to formalize this process and provide support for it. Most of these Py-to-JS converters work fine on mobile devices, too. Guido, if you haven't checked it out, is a very interesting demo: it literally makes