The "help()" freeze is not really a freeze since you can type input within the terminal from where you started pycons. I managed to find that the IPython import was responsible for this behavior for some unknown reason. If you remove all reference to IPython in the pycons file, then you got the expected behavior. Since IPython is under heavy redesign, I won't investigate further until the next version.
What is the problem when closing with a graph inside ? Nicolas On Tue, 2008-07-01 at 15:37 +0200, David Trem wrote: > Sorry for the trouble, I started testing your "old" pylab wich was > provided without the setup script, which led me testing pycons from the > pycons folder itself (no setup.py install done). > Pycons was actually working fine. > However, I encounter problem when closing the console with a graph > inside and with the >>>help() command which is freezing the windows... > But this is basically usable. > > Thanks you very much considering my license request! > I don't think there could be license issue with matplotlib since it is > also using a quite permissive license. Could the matplotlib gurus > comment on that? > > Thanks, > > David > > Nicolas Rougier a écrit : > > > > Thanks, > > > > I changed the license to a BSD one, hope this is compatible with > > matplotlib. I also changed the module name from 'gtk_console' to pycons > > since it makes more sense. > > > > I also tried to remove the gtk_console.console (now this is > > pycons.console) in favor of console but it does not work as expected I > > would say. In fact, I'm surprised it's working for you. What do you get > > from a simple "import pycons" ? > > > > Nicolas > > > > > > On Tue, 2008-07-01 at 14:32 +0200, David Trem wrote: > >> Hi Nicolas, > >> > >> Your pycons is great! > >> I has to correct a small issue in the tar.gz from your website before > >> being able to test pycons: > >> I had to change: > >> "import gtk_console.console as cons" > >> to "import console as cons" > >> in pycons file around line 12. > >> > >> After that I can report pycons is running on my MacBook (MacOS 10.5) > >> with python, pygtk... from macports. > >> > >> Another point: > >> do you mind releasing your code in a more permissive license that GPL. I > >> mean LGPL or BSD like? I'm interested in including your code in my own > >> LGPL app. > >> > >> Thanks for this great peace of work. > >> > >> All the best, > >> > >> David > >> > >> Nicolas Rougier a écrit : > >>> Hi, > >>> > >>> I've added some basic support for readline shortcuts: > >>> > >>> Ctrl-A: start of line > >>> Ctrl-E: end of line > >>> Ctrl-K: kill from cursor to end of line > >>> Ctrl-Y: yank kill buffer > >>> Ctrl-L: clear console > >>> > >>> I've also added an option for displaying the toolbar(2). > >>> > >>> Usage is now: > >>> > >>> pycons [--ipython] [--pylab] [--toolbar] > >>> > >>> > >>> If the toolbar is not specified, commands can be typed directly within > >>> console: zoom(), pan(), home(), back(), forward(), save() > >>> > >>> There is now a installable package (pycons.tgz) available from: > >>> > >>> http://www.loria.fr/~rougier/pycons.html > >>> > >>> > >>> > >>> Nicolas > >>> > >>> > >>> > >>> On Mon, 2008-06-30 at 21:21 -0500, John Hunter wrote: > >>>> On Sun, Jun 29, 2008 at 9:28 AM, Nicolas Rougier > >>>> <[EMAIL PROTECTED]> wrote: > >>>>> Thanks John, I've update the new version with your code. > >>>>> > >>>>> It is now available at: > >>>>> http://www.loria.fr/~rougier/pylab.html > >>>>> > >>>>> You can now choose between python and ipython (option -s python > >>>>> or -s ipython) and all user events on a figure should be handled > >>>>> properly (mouse, scroll and key). > >>>>> > >>>>> Concerning the toolbar, is is quite easy to add but it is not > >>>>> very pleasant to the eyes. I'm looking for a more asethetic solution. > >>>> I've only had a limited chance to test this but it looks very > >>>> exciting. I am amazed by how quickly you go the ipython shell > >>>> incorporated. I am still a bit vexed by the lack of support for emacs > >>>> key bindings (I guess having ipython and readline support are not > >>>> enough, but I bet there is some gtk console code out there to support > >>>> them). I do miss my CTRL-a and CTRL-k and friends. > >>>> > >>>> As for the toolbar, I think functionality over aesthetics carries the > >>>> day because it is easy to make it pretty after you make it work (and > >>>> you can always make it optional with a flag), but note that you do not > >>>> need to use the standard gtk toolbar widget -- you can write your own > >>>> that works however you want. There is only minimal overhead for the > >>>> toolbar writer that is fairly well documented in backend_bases.py. > >>>> One option is to draw no toolbar at all but just just set up key > >>>> bindings (press 'z' to toggle zoom mode, 'r' to toggle draw to rect > >>>> mode, etc, or draw your own toolbar or whatever. But having the > >>>> functionality is a killer feature, in my opinion. > >>>> > >>>> Keep us posted. > >>>> > >>>> JDH > >>> > >>> ------------------------------------------------------------------------- > >>> Check out the new SourceForge.net Marketplace. > >>> It's the best place to buy or sell services for > >>> just about anything Open Source. > >>> http://sourceforge.net/services/buy/index.php > >>> _______________________________________________ > >>> Matplotlib-devel mailing list > >>> Matplotlib-devel@lists.sourceforge.net > >>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
