Menu
▾
▴
matplotlib-devel — matplotlib developers
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(33) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(7) |
Feb
(44) |
Mar
(51) |
Apr
(43) |
May
(43) |
Jun
(36) |
Jul
(61) |
Aug
(44) |
Sep
(25) |
Oct
(82) |
Nov
(97) |
Dec
(47) |
| 2005 |
Jan
(77) |
Feb
(143) |
Mar
(42) |
Apr
(31) |
May
(93) |
Jun
(93) |
Jul
(35) |
Aug
(78) |
Sep
(56) |
Oct
(44) |
Nov
(72) |
Dec
(75) |
| 2006 |
Jan
(116) |
Feb
(99) |
Mar
(181) |
Apr
(171) |
May
(112) |
Jun
(86) |
Jul
(91) |
Aug
(111) |
Sep
(77) |
Oct
(72) |
Nov
(57) |
Dec
(51) |
| 2007 |
Jan
(64) |
Feb
(116) |
Mar
(70) |
Apr
(74) |
May
(53) |
Jun
(40) |
Jul
(519) |
Aug
(151) |
Sep
(132) |
Oct
(74) |
Nov
(282) |
Dec
(190) |
| 2008 |
Jan
(141) |
Feb
(67) |
Mar
(69) |
Apr
(96) |
May
(227) |
Jun
(404) |
Jul
(399) |
Aug
(96) |
Sep
(120) |
Oct
(205) |
Nov
(126) |
Dec
(261) |
| 2009 |
Jan
(136) |
Feb
(136) |
Mar
(119) |
Apr
(124) |
May
(155) |
Jun
(98) |
Jul
(136) |
Aug
(292) |
Sep
(174) |
Oct
(126) |
Nov
(126) |
Dec
(79) |
| 2010 |
Jan
(109) |
Feb
(83) |
Mar
(139) |
Apr
(91) |
May
(79) |
Jun
(164) |
Jul
(184) |
Aug
(146) |
Sep
(163) |
Oct
(128) |
Nov
(70) |
Dec
(73) |
| 2011 |
Jan
(235) |
Feb
(165) |
Mar
(147) |
Apr
(86) |
May
(74) |
Jun
(118) |
Jul
(65) |
Aug
(75) |
Sep
(162) |
Oct
(94) |
Nov
(48) |
Dec
(44) |
| 2012 |
Jan
(49) |
Feb
(40) |
Mar
(88) |
Apr
(35) |
May
(52) |
Jun
(69) |
Jul
(90) |
Aug
(123) |
Sep
(112) |
Oct
(120) |
Nov
(105) |
Dec
(116) |
| 2013 |
Jan
(76) |
Feb
(26) |
Mar
(78) |
Apr
(43) |
May
(61) |
Jun
(53) |
Jul
(147) |
Aug
(85) |
Sep
(83) |
Oct
(122) |
Nov
(18) |
Dec
(27) |
| 2014 |
Jan
(58) |
Feb
(25) |
Mar
(49) |
Apr
(17) |
May
(29) |
Jun
(39) |
Jul
(53) |
Aug
(52) |
Sep
(35) |
Oct
(47) |
Nov
(110) |
Dec
(27) |
| 2015 |
Jan
(50) |
Feb
(93) |
Mar
(96) |
Apr
(30) |
May
(55) |
Jun
(83) |
Jul
(44) |
Aug
(8) |
Sep
(5) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(3) |
Sep
(1) |
Oct
(3) |
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
(7) |
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Michael D. <md...@st...> - 2013-08-15 17:08:46
|
Thanks to everyone who participated in the discussion today. I didn't take great notes, but I thought I would synthesize the discussion into a list of action items on the wiki here: https://github.com/matplotlib/matplotlib/wiki/Mep19-continuous-integration-hangout If I forgot something, please add. My memory gets fuzzier in my old age. Mike |
|
From: Michael D. <md...@st...> - 2013-08-15 14:07:46
|
I *think* (I've never done this before) that the Google Hangout is visible to anyone at this address: https://plus.google.com/hangouts/_/c1aa29f0e2790bf8e77d6bce867772d39ce7c0c6 Mike |
|
From: Michael D. <md...@st...> - 2013-08-15 13:40:20
|
Thanks for advertising this, Phil -- I had meant to do so. I'll post a link to the "Hangout On Air" to matplotlib-devel once this meeting starts. Mike On 08/15/2013 09:20 AM, Phil Elson wrote: > Just in case anybody who wanted to attend the discussion knows, this > meeting is taking place in ~40 minutes. (See > https://www.google.com/calendar/embed?src=79hk8jhvlks8jn8ds4ri1e6q4g%40group.calendar.google.com&ctz=America/New_York > as linked from the matplotlib wiki). > > Cheers, > > Phil > > > On 5 August 2013 16:18, Michael Droettboom <md...@st... > <mailto:md...@st...>> wrote: > > Ok -- I've redone it as 2 hour blocks -- we may not need that much > time, but it seemed like the easiest way to make this work. > > Cheers, > Mike > > > On 08/05/2013 11:11 AM, Michael Droettboom wrote: >> Sorry -- bear with me -- I didn't mean to put in really large >> blocks of time like that. Hold on as I try to fix this. >> >> On 08/05/2013 10:42 AM, Michael Droettboom wrote: >>> I've set up a Doodle poll to find a good time. >>> >>> http://doodle.com/4f3yzii4vv7w93ai >>> >>> Most of the interesting parties are either in North America or >>> Europe (sorry, Eric: you're the outlier). >>> >>> Cheers, >>> Mike >>> >>> On 08/02/2013 10:05 PM, Matt Terry wrote: >>>> >>>> I don't have any useful experience with CI services, but it >>>> would be nice to have the ability to test on macos. >>>> >>>> On Aug 2, 2013 6:10 PM, "Benjamin Root" <ben...@ou... >>>> <mailto:ben...@ou...>> wrote: >>>> > >>>> > +1 for me too >>>> > >>>> > Ben >>>> > >>>> > On Aug 2, 2013 11:04 AM, "Chris Beaumont" >>>> <bea...@ha... <mailto:bea...@ha...>> wrote: >>>> >> >>>> >> I'd like to sit in on this if I'm available. Please keep me >>>> posted >>>> >> >>>> >> Cheers, >>>> >> Chris >>>> >> >>>> >> >>>> ------------------------------------------------------------------------------ >>>> >> Get your SQL database under version control now! >>>> >> Version control is standard for application code, but >>>> databases havent >>>> >> caught up. So what steps can you take to put your SQL >>>> databases under >>>> >> version control? Why should you start doing it? Read more to >>>> find out. >>>> >> >>>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk >>>> >> _______________________________________________ >>>> >> Matplotlib-devel mailing list >>>> >> Mat...@li... >>>> <mailto:Mat...@li...> >>>> >> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >>>> >> >>>> > >>>> > >>>> ------------------------------------------------------------------------------ >>>> > Get your SQL database under version control now! >>>> > Version control is standard for application code, but >>>> databases havent >>>> > caught up. So what steps can you take to put your SQL >>>> databases under >>>> > version control? Why should you start doing it? Read more to >>>> find out. >>>> > >>>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk >>>> > _______________________________________________ >>>> > Matplotlib-devel mailing list >>>> > Mat...@li... >>>> <mailto:Mat...@li...> >>>> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >>>> > >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Get your SQL database under version control now! >>>> Version control is standard for application code, but databases havent >>>> caught up. So what steps can you take to put your SQL databases under >>>> version control? Why should you start doing it? Read more to find out. >>>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk >>>> >>>> >>>> _______________________________________________ >>>> Matplotlib-devel mailing list >>>> Mat...@li... <mailto:Mat...@li...> >>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Get your SQL database under version control now! >>> Version control is standard for application code, but databases havent >>> caught up. So what steps can you take to put your SQL databases under >>> version control? Why should you start doing it? Read more to find out. >>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk >>> >>> >>> _______________________________________________ >>> Matplotlib-devel mailing list >>> Mat...@li... <mailto:Mat...@li...> >>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >> >> >> >> ------------------------------------------------------------------------------ >> Get your SQL database under version control now! >> Version control is standard for application code, but databases havent >> caught up. So what steps can you take to put your SQL databases under >> version control? Why should you start doing it? Read more to find out. >> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk >> >> >> _______________________________________________ >> Matplotlib-devel mailing list >> Mat...@li... <mailto:Mat...@li...> >> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > <mailto:Mat...@li...> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > > > > ------------------------------------------------------------------------------ > Get 100% visibility into Java/.NET code with AppDynamics Lite! > It's a free troubleshooting tool designed for production. > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk > > > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel |
|
From: Phil E. <pel...@gm...> - 2013-08-15 13:20:29
|
Just in case anybody who wanted to attend the discussion knows, this meeting is taking place in ~40 minutes. (See https://www.google.com/calendar/embed?src=79hk8jhvlks8jn8ds4ri1e6q4g%40group.calendar.google.com&ctz=America/New_Yorkas linked from the matplotlib wiki). Cheers, Phil On 5 August 2013 16:18, Michael Droettboom <md...@st...> wrote: > Ok -- I've redone it as 2 hour blocks -- we may not need that much time, > but it seemed like the easiest way to make this work. > > Cheers, > Mike > > > On 08/05/2013 11:11 AM, Michael Droettboom wrote: > > Sorry -- bear with me -- I didn't mean to put in really large blocks of > time like that. Hold on as I try to fix this. > > On 08/05/2013 10:42 AM, Michael Droettboom wrote: > > I've set up a Doodle poll to find a good time. > > http://doodle.com/4f3yzii4vv7w93ai > > Most of the interesting parties are either in North America or Europe > (sorry, Eric: you're the outlier). > > Cheers, > Mike > > On 08/02/2013 10:05 PM, Matt Terry wrote: > > I don't have any useful experience with CI services, but it would be nice > to have the ability to test on macos. > > On Aug 2, 2013 6:10 PM, "Benjamin Root" <ben...@ou...> wrote: > > > > +1 for me too > > > > Ben > > > > On Aug 2, 2013 11:04 AM, "Chris Beaumont" <bea...@ha...> wrote: > >> > >> I'd like to sit in on this if I'm available. Please keep me posted > >> > >> Cheers, > >> Chris > >> > >> > ------------------------------------------------------------------------------ > >> Get your SQL database under version control now! > >> Version control is standard for application code, but databases havent > >> caught up. So what steps can you take to put your SQL databases under > >> version control? Why should you start doing it? Read more to find out. > >> > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > >> _______________________________________________ > >> Matplotlib-devel mailing list > >> Mat...@li... > >> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > >> > > > > > ------------------------------------------------------------------------------ > > Get your SQL database under version control now! > > Version control is standard for application code, but databases havent > > caught up. So what steps can you take to put your SQL databases under > > version control? Why should you start doing it? Read more to find out. > > > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > > _______________________________________________ > > Matplotlib-devel mailing list > > Mat...@li... > > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > > > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out.http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > > > > _______________________________________________ > Matplotlib-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > > > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out.http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > > > > _______________________________________________ > Matplotlib-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > > > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out.http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > > > > _______________________________________________ > Matplotlib-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > > > > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > |
|
From: Eric F. <ef...@ha...> - 2013-08-14 22:22:26
|
On 2013/08/14 12:18 PM, Erik Bray wrote: > Apparently IDLE doesn't set sys.ps1 either: Maybe this is a good thing; interactive mode doesn't work in IDLE. |
|
From: Erik B. <eri...@gm...> - 2013-08-14 22:18:11
|
On Wed, Aug 14, 2013 at 6:14 PM, Erik Bray <eri...@gm...> wrote: > On Mon, Aug 12, 2013 at 10:01 AM, Michael Droettboom <md...@st...> wrote: >> I'm considering changing the behavior of the rcParam interactive (which also >> can be set through matplotlib.interactive() and pyplot.ion() and >> pyplot.ioff()). Currently, when setting interactive to True, running any >> sort of matplotlib plot as a script will fail to display a window. This can >> be very surprising if a user turns on interactive because they prefer its >> behavior in IPython, but are then surprised that none of their scripts >> continue to work. I propose to fix this by turning on interactive only when >> running at an interactive console. >> >> See the pull request http://github.com/matplotlib/matplotlib/pull/2286 for >> an implementation. >> >> I'm trying to rule out any negative impact of this change, and I would >> appreciate any feedback if this change will have a negative impact on your >> application. >> >> Mike > > It appears bpython does not set sys.ps1. I wonder if this shouldn't > be considered a bug/oversight in bpython though. If nothing else it > might be worth pointing out to its developers. I also wonder how this > would impact IDEs (though I don't use any personally). > Apparently IDLE doesn't set sys.ps1 either: http://bugs.python.org/issue13657 I know at least a few people who use IDLE.... ;) I feel like there has to be a better way to determine if an interactive prompt is in use, though I'll admit nothing jumps immediately to mind :/ Erik |
|
From: Erik B. <eri...@gm...> - 2013-08-14 22:14:25
|
On Mon, Aug 12, 2013 at 10:01 AM, Michael Droettboom <md...@st...> wrote: > I'm considering changing the behavior of the rcParam interactive (which also > can be set through matplotlib.interactive() and pyplot.ion() and > pyplot.ioff()). Currently, when setting interactive to True, running any > sort of matplotlib plot as a script will fail to display a window. This can > be very surprising if a user turns on interactive because they prefer its > behavior in IPython, but are then surprised that none of their scripts > continue to work. I propose to fix this by turning on interactive only when > running at an interactive console. > > See the pull request http://github.com/matplotlib/matplotlib/pull/2286 for > an implementation. > > I'm trying to rule out any negative impact of this change, and I would > appreciate any feedback if this change will have a negative impact on your > application. > > Mike It appears bpython does not set sys.ps1. I wonder if this shouldn't be considered a bug/oversight in bpython though. If nothing else it might be worth pointing out to its developers. I also wonder how this would impact IDEs (though I don't use any personally). Erik |
|
From: Michael D. <md...@st...> - 2013-08-13 10:58:51
|
As I'm researching what we may want to do for better continuous integration, I'm remembering that at least one person, Thomas Kluyver, is producing daily automated builds (for Ubuntu) here: https://launchpad.net/~takluyver/+archive/matplotlib-daily <https://launchpad.net/%7Etakluyver/+archive/matplotlib-daily> Is anyone else out there doing anything similar for other Linux distros or other platforms? a) I'd like to list these things on the main website, and b) I'd like to look at how these kinds of things might make sense as part of a broader CI strategy. Cheers, Mike |
|
From: Chris B. - N. F. <chr...@no...> - 2013-08-12 23:54:51
|
On Mon, Aug 12, 2013 at 11:16 AM, Michael Droettboom <md...@st...> wrote: > Would you mind testing the very simple patch in the PR [1] and confirm > that it has no negative consequences for you? > > [1] http://github.com/matplotlib/matplotlib/pull/2286 Hmm -- I'm not set up to build it right now -- but I'll see what I can do. -Chris > Mike > > On 08/12/2013 01:55 PM, Chris Barker - NOAA Federal wrote: >> On Mon, Aug 12, 2013 at 7:01 AM, Michael Droettboom <md...@st...> wrote: >>> I propose to fix this by turning on interactive only when >>> running at an interactive console. >> I embed MPL more than other uses, and this sounds like a fine solution to me/ >> >> Thanks, >> >> -Chris >> >> > > > ------------------------------------------------------------------------------ > Get 100% visibility into Java/.NET code with AppDynamics Lite! > It's a free troubleshooting tool designed for production. > Get down to code-level detail for bottlenecks, with <2% overhead. > Download for free and get started troubleshooting in minutes. > http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chr...@no... |
|
From: Michael D. <md...@st...> - 2013-08-12 18:17:41
|
Would you mind testing the very simple patch in the PR [1] and confirm that it has no negative consequences for you? [1] http://github.com/matplotlib/matplotlib/pull/2286 Mike On 08/12/2013 01:55 PM, Chris Barker - NOAA Federal wrote: > On Mon, Aug 12, 2013 at 7:01 AM, Michael Droettboom <md...@st...> wrote: >> I propose to fix this by turning on interactive only when >> running at an interactive console. > I embed MPL more than other uses, and this sounds like a fine solution to me/ > > Thanks, > > -Chris > > |
|
From: Chris B. - N. F. <chr...@no...> - 2013-08-12 17:56:07
|
On Mon, Aug 12, 2013 at 7:01 AM, Michael Droettboom <md...@st...> wrote: > I propose to fix this by turning on interactive only when > running at an interactive console. I embed MPL more than other uses, and this sounds like a fine solution to me/ Thanks, -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chr...@no... |
|
From: Michael D. <md...@st...> - 2013-08-12 14:08:41
|
I'm considering changing the behavior of the rcParam |interactive| (which also can be set through |matplotlib.interactive()| and |pyplot.ion()| and |pyplot.ioff()|). Currently, when setting |interactive| to |True|, running any sort of matplotlib plot as a script will fail to display a window. This can be very surprising if a user turns on |interactive| because they prefer its behavior in IPython, but are then surprised that none of their scripts continue to work. I propose to fix this by turning on |interactive| only when running at an interactive console. See the pull request http://github.com/matplotlib/matplotlib/pull/2286 for an implementation. I'm trying to rule out any negative impact of this change, and I would appreciate any feedback if this change will have a negative impact on your application. Mike |
|
From: Fernando P. <fpe...@gm...> - 2013-08-09 01:38:16
|
Hi all, I am incredibly thrilled, on behalf of the amazing IPython Dev Team, to announce the official release of IPython 1.0 today, an effort nearly 12 years in the making. The previous version (0.13) was released on June 30, 2012, and in this development cycle we had: ~12 months of work. ~700 pull requests merged. ~600 issues closed (non-pull requests). contributions from ~150 authors. ~4000 commits. # A little context What does "1.0" mean for IPython? Obviously IPython has been a staple of the scientific Python community for years, and we've made every effort to make it a robust and production ready tool for a long time, so what exactly do we mean by tagging this particular release as 1.0? Basically, we feel that the core design of IPython, and the scope of the project, is where we want it to be. What we have today is what we consider a reasonably complete, design- and scope-wise, IPython 1.0: an architecture for interactive computing, that can drive kernels in a number of ways using a well-defined protocol, and rich and powerful clients that let users control those kernels effectively. Our different clients serve different needs, with the old workhorse of the terminal still being very useful, but much of our current development energy going into the Notebook, obviously. The Notebook enables interactive exploration to become Literate Computing, bridging the gaps from individual work to collaboration and publication, all with an open file format that is a direct record of the underlying communication protocol. There are obviously plenty of open issues (many of them very important) that need fixing, and large and ambitious new lines of development for the years to come. But the work of the last four years, since the summer of 2009 when Brian Granger was able to devote a summer (thanks to funding from the NiPy project - nipy.org) to refactoring the old IPython core code, finally opened up or infrastructure for real innovation. By disentangling what was a useful but impenetrable codebase, it became possible for us to start building a flexible, modern system for interactive computing that abstracted the old REPL model into a generic protocol that kernels could use to talk to clients. This led at first to the creation of the Qt console, and then to the Notebook and out-of-process terminal client. It also allowed us to (finally!) unify our parallel computing machinery with the rest of the interactive system, which Min Ragan-Kelley pulled off in a development tour de force that involved rewriting in a few weeks a huge and complex Twisted-based system. We are very happy with how the Notebook work has turned out, and it seems the entire community agrees with us, as the uptake has been phenomenal. Back from the very first "IPython 0.0.1" that I started in 2001: https://gist.github.com/fperez/1579699 there were already hints of tools like Mathematica: it was my everyday workhorse as a theoretical physicist and I found its Notebook environment invaluable. But as a grad student trying out "just an afternoon hack" (IPython was my very first Python program as I was learning the language), I didn't have the resources, skills or vision to attempt building an entire notebook system, and to be honest the tools of the day would have made that enterprise a miserable one. But those ideas were always driving our efforts, and as IPython started becoming a project with a team, we made multiple attempts to get a good Notebook built around IPython. Those interested can read an old blog post of mine with the history (http://blog.fperez.org/2012/01/ipython-notebook-historical.html). The short story is that in 2011, on our sixth attempt, Brian was again able to devote a focused summer into using our client-server architecture and, with the stack of the modern web (Javascript, CSS, websockets, Tornado, ...), finally build a robust system for Literate Computing across programming languages. Today, thanks to the generous support and vision of Josh Greenberg at the Alfred P. Sloan Foundation, we are working very hard on building the notebook infrastructure, and this release contains major advances on that front. We have high hopes for what we'll do next; as a glimpse of the future that this enables, now there is a native Julia kernel that speaks to our clients, notebook included: https://github.com/JuliaLang/IJulia.jl. # Team I can't stress enough how impressed I am with the work people are doing in IPython, and what a privilege it is to work with colleagues like these. Brian Granger and Min Ragan-Kelley joined IPython around 2005, initially working on the parallel machinery, but since ~ 2009 they have become the heart of the project. Today Min is our top committer and knows our codebase better than anyone else, and I can't imagine better partners for an effort like this. And from regulars in our core team like Thomas Kluyver, Matthias Bussonnier, Brad Froehle and Paul Ivanov to newcomers like Jonathan Frederic and Zach Sailer, in addition to the many more whose names are in our logs, we have a crazy amount of energy being poured into IPython. I hope we'll continue to harness it productively! The full list of contributors to this release can be seen here: http://ipython.org/ipython-doc/rel-1.0.0/whatsnew/github-stats-1.0.html # Release highlights * nbconvert: this is the major piece of new functionality in this cycle, and was an explicit part of our roadmap (https://github.com/ipython/ipython/wiki/Roadmap:-IPython). nbconvert is now an IPython subcommand to convert notebooks into other formats such as HTML or LaTeX, but more importantly, it's a very flexible system that lets you write custom templates to generate new output with arbitrary control over the formatting and transformations that are applied to the input. We want to stress that despite the fact that a huge amount of work went into nbconvert, this should be considered a *tech preview* release. We've come to realize how complex this problem is, and while we'll make every effort to keep the high-level command-line syntax and APIs as stable as possible, it is quite likely that the internals will continue to evolve, possibly in backwards-incompatible ways. So if you start building services and libraries that make heavy use of the nbconvert internals, please be prepared for some turmoil in the months to come, and ping us on the dev list with questions or concerns. * Notebook improvements: there has been a ton of polish work in the notebook at many levels, though the file format remains unchanged from 0.13, so you shouldn't have any problems sharing notebooks with colleagues still using 0.13. - Autosave: probably the most oft-requested feature, the notebook server now autosaves your files! You can still hit Ctrl-S to force a manual save (which also creates a special 'checkpoint' you can come back to). - The notebook supports raw_input(), and thus also %debug. This was probably the main deficiency of the notebook as a client compared to the terminal/qtconsole, and it has been finally fixed. - Add %%html, %%svg, %%javascript, and %%latex cell magics for writing raw output in notebook cells. - Fix an issue parsing LaTeX in markdown cells, which required users to type \\\, instead of \\. -Images support width and height metadata, and thereby 2x scaling (retina support). - %%file has been renamed %%writefile (%%file) is deprecated. * The input transofrmation code has been updated and rationalized. This is a somewhat specialized part of IPython, but of importance to projects that build upon it for custom environments, like Sympy and Sage. Our full release notes are here: http://ipython.org/ipython-doc/rel-1.0.0/whatsnew/version1.0.html and the gory details are here: http://ipython.org/ipython-doc/rel-1.0.0/whatsnew/github-stats-1.0.html # Installation Installation links and instructions are at: http://ipython.org/install.html And IPython is also on PyPI: http://pypi.python.org/pypi/ipython # Requirements IPython 1.0 requires Python ≥ 2.6.5 or ≥ 3.2.1. It does not support Python 3.0, 3.1, or 2.5. # Acknowledgments Last but not least, we'd like to acknowledge the generous support of those who make it possible for us to spend our time working on IPython. In particular, the Alfred P. Sloan Foundation today lets us have a solid team working full-time on the project, and without the support of Enthought Inc at multiple points in our history, we wouldn't be where we are today. The full list of our support is here: http://ipython.org/index.html#support Thanks to everyone! Please enjoy IPython 1.0, and report all bugs as usual! Fernando, on behalf of the IPython Dev Team. -- Fernando Perez (@fperez_org; http://fperez.org) fperez.net-at-gmail: mailing lists only (I ignore this when swamped!) fernando.perez-at-berkeley: contact me here for any direct mail |
|
From: Michael D. <md...@st...> - 2013-08-08 17:51:38
|
On 08/08/2013 11:56 AM, Andy Ray Terrel wrote: > Doh, I never got the site up! This looks good, although copyright > shouldn't go to Michael. We don't have copyright on the images or > text just permission to display them. (I would probably just delete > it or be specific what the copyright is.) I like the idea of having a > site next to conference.scipy.org to display these. Yeah -- the copyright ended up to me accidentally because I filled it out as the "author" field in Sphinx in the original version. I think if we want to have an "author" it should say "Scipy Conference Organizers" (without copyright), and maybe we give Nelle some well deserved credit for the web design as well. Mike > > -- Andy > > On Thu, Aug 8, 2013 at 10:48 AM, Nelle Varoquaux > <nel...@gm...> wrote: >> Hi everyone, >> >> Here is my attempt at making the website: >> http://nellev.github.io/tmp/jhepc/index.html >> This is still work in progress, but feedback is welcomed. >> >> I chose to display only the "winners" (three top place + honorable mention). >> >> Cheers, >> N >> >> >> On 31 July 2013 17:54, Andy Ray Terrel <and...@gm...> wrote: >>> Okay, I'll get it up. >>> >>> -- Andy >>> >>> >>> On Wed, Jul 31, 2013 at 10:48 AM, Michael Droettboom <md...@st...> >>> wrote: >>>> On 07/31/2013 11:38 AM, Andy Ray Terrel wrote: >>>> >>>> >>>> The plan was to have it on the SciPy conference website, but we haven't >>>> really got it up. If someone can point me to rendered html, I can ask Jim to >>>> put it up there now. >>>> >>>> The rendered HTML is in the scipy2013_talks github repo. >>>> >>>> https://github.com/scipy/scipy2013_talks/tree/master/plotting_contest >>>> >>>> That will be fine for now, and it sounds like Nelle will make the >>>> presentation much better down the road, at which case we can update it then. >>>> >>>> Mike >>> |
|
From: Thomas K. <th...@kl...> - 2013-08-08 17:46:53
|
On 8 August 2013 09:56, Russell E. Owen <ro...@uw...> wrote: > BTW: pip refuses to install pytz for me, claiming a suitable version was > not found, and listing dozens of versions. Anyone else seen this? I > don't recall seeing it before recently. I ended up downloading the > source and using distutils. > Recent versions of pip don't like pytz's version numbering scheme. It's not quite clear which end will fix this: https://bugs.launchpad.net/pytz/+bug/1204837 https://github.com/pypa/pip/issues/974 Thomas |
|
From: Russell E. O. <ro...@uw...> - 2013-08-08 16:57:21
|
In article <row...@ne...>, "Russell E. Owen" <ro...@uw...> wrote: > In article <51F...@st...>, > Michael Droettboom <md...@st...> > wrote: > > > Ludwig, this is one of the most entertaining e-mails I've read in a > > while, and I think your arguments make a lot of sense. > > > > Given infinite developer resources, do you think there's any logic to > > providing *both* system Python and python.org based binaries? How much > > additional work would that be? > > > > I think the big problems to solve now is > > > > (a) get to the bottom of why the new installer is breaking existing > > installations of dateutil and pytz. Russell: even though they are not > > currently working, could you provide what you have so that others can > > have a look? > > I put the installer here (and announced it earlier -- I thought in this > thread): > <http://www.astro.washington.edu/users/rowen/python/> > > I do not consider it safe because: > - It may trash existing installations of dateutil and pytz (especially > those installed by the matplotlib 1.2.1 binary installer) > - It does not include pytz, dateutil and six (unlike the 1.2.1 binary > installer), so it's a real pain to use > - It is missing its unit tests and so is poorly tested > - It also appears that pylab is broken (something I only recently > discovered) I was able to fix the last two problems and I uploaded a new binary installer to the location mentioned above. It still will delete python-dateutil under some circumstances (not fully tested, but the last one would not trash it if it was installed by pip, but would trash it if installed by the matplotlib 1.2.1 binary installer). I could imagine making it the official installer anyway, for lack of anything better. But it's certainly not ideal. It is surely not that hard to make an installer that can also install other packages. But it's not something I have time to investigate right now. BTW: pip refuses to install pytz for me, claiming a suitable version was not found, and listing dozens of versions. Anyone else seen this? I don't recall seeing it before recently. I ended up downloading the source and using distutils. -- Russell |
|
From: Nelle V. <nel...@gm...> - 2013-08-08 16:05:39
|
> The images are being cut off on the front page slide show thing. > Because of the differences of size and shape in the images, it's hard to do a design that display them all completely in the carousel. Hence, one of them is truncated. Only one of them (the first place) should be truncated. Note that in the gallery, images are also cropped. Also, so far, I only tested this on chrome and firefox (and an old version of chromium). There might be issues with IE. And it hasn't been optimized for very small screens (smartphones). It's not completely awful, but it's not nice either. I hope to fix that soon. I fixed the copyright (Github takes a while to update the pages, hence it might not be up yet). On Thu, Aug 8, 2013 at 10:48 AM, Nelle Varoquaux <nel...@gm...>wrote: > >> Hi everyone, >> >> Here is my attempt at making the website: >> http://nellev.github.io/tmp/jhepc/index.html >> This is still work in progress, but feedback is welcomed. >> >> I chose to display only the "winners" (three top place + honorable >> mention). >> >> Cheers, >> N >> >> >> On 31 July 2013 17:54, Andy Ray Terrel <and...@gm...> wrote: >> >>> Okay, I'll get it up. >>> >>> -- Andy >>> >>> >>> On Wed, Jul 31, 2013 at 10:48 AM, Michael Droettboom <md...@st...>wrote: >>> >>>> On 07/31/2013 11:38 AM, Andy Ray Terrel wrote: >>>> >>>> >>>> The plan was to have it on the SciPy conference website, but we >>>> haven't really got it up. If someone can point me to rendered html, I can >>>> ask Jim to put it up there now. >>>> >>>> The rendered HTML is in the scipy2013_talks github repo. >>>> >>>> https://github.com/scipy/scipy2013_talks/tree/master/plotting_contest >>>> >>>> That will be fine for now, and it sounds like Nelle will make the >>>> presentation much better down the road, at which case we can update it then. >>>> >>>> Mike >>>> >>> >>> >> > |
|
From: Andy R. T. <and...@gm...> - 2013-08-08 15:57:00
|
Doh, I never got the site up! This looks good, although copyright shouldn't go to Michael. We don't have copyright on the images or text just permission to display them. (I would probably just delete it or be specific what the copyright is.) I like the idea of having a site next to conference.scipy.org to display these. -- Andy On Thu, Aug 8, 2013 at 10:48 AM, Nelle Varoquaux <nel...@gm...> wrote: > Hi everyone, > > Here is my attempt at making the website: > http://nellev.github.io/tmp/jhepc/index.html > This is still work in progress, but feedback is welcomed. > > I chose to display only the "winners" (three top place + honorable mention). > > Cheers, > N > > > On 31 July 2013 17:54, Andy Ray Terrel <and...@gm...> wrote: >> >> Okay, I'll get it up. >> >> -- Andy >> >> >> On Wed, Jul 31, 2013 at 10:48 AM, Michael Droettboom <md...@st...> >> wrote: >>> >>> On 07/31/2013 11:38 AM, Andy Ray Terrel wrote: >>> >>> >>> The plan was to have it on the SciPy conference website, but we haven't >>> really got it up. If someone can point me to rendered html, I can ask Jim to >>> put it up there now. >>> >>> The rendered HTML is in the scipy2013_talks github repo. >>> >>> https://github.com/scipy/scipy2013_talks/tree/master/plotting_contest >>> >>> That will be fine for now, and it sounds like Nelle will make the >>> presentation much better down the road, at which case we can update it then. >>> >>> Mike >> >> > |
|
From: Nelle V. <nel...@gm...> - 2013-08-08 15:48:13
|
Hi everyone, Here is my attempt at making the website: http://nellev.github.io/tmp/jhepc/index.html This is still work in progress, but feedback is welcomed. I chose to display only the "winners" (three top place + honorable mention). Cheers, N On 31 July 2013 17:54, Andy Ray Terrel <and...@gm...> wrote: > Okay, I'll get it up. > > -- Andy > > > On Wed, Jul 31, 2013 at 10:48 AM, Michael Droettboom <md...@st...>wrote: > >> On 07/31/2013 11:38 AM, Andy Ray Terrel wrote: >> >> >> The plan was to have it on the SciPy conference website, but we haven't >> really got it up. If someone can point me to rendered html, I can ask Jim >> to put it up there now. >> >> The rendered HTML is in the scipy2013_talks github repo. >> >> https://github.com/scipy/scipy2013_talks/tree/master/plotting_contest >> >> That will be fine for now, and it sounds like Nelle will make the >> presentation much better down the road, at which case we can update it then. >> >> Mike >> > > |
|
From: Fernando P. <fpe...@gm...> - 2013-08-08 00:00:27
|
Hi Mike, thanks a lot for providing these numbers... I think for now, the plan we hatched at the dev meeting continues to look reasonable (integrate interactive webagg support into the %matplotlib magic so it would be seamless to users on localhost or very open networks). But the fact that the overhead is lower than we'd thought lends weight to the idea of giving mpl an easier way to integrate this functionality into our existing design before we cross the binary ws bridge... One way or another, exciting times! Cheers, f |
|
From: MinRK <ben...@gm...> - 2013-08-07 23:08:56
|
On Tue, Jul 30, 2013 at 2:28 PM, Michael Droettboom <md...@st...> wrote: > As promised in last week's Google Hangout to the IPython developers > meeting -- I have some concrete timings and numbers on the matplotlib > WebAgg backend in a couple of different scenarios. > > First, let me apologize -- the way I was timing binary websockets vs. > text websockets previously was wrong. The actual impact of it is much > smaller than I had originally estimated -- so the discussion about > whether to include binary websockets in IPython may have been all for > naught. > Part of our message spec includes binary blobs trailing after the JSONable message dicts. Currently this is used by `data_pub` and `apply` messages, but it could theoretically be extended to display data for streaming output, such as video or audio. Right now, we have no way of propagating that part of the message spec up to notebook frontends, because we do not yet have any binary messages that the notebook frontend can understand. In these cases, a switch to binary websocket may still make sense, even without a performance argument. > > For benchmarking, I used two different plots. One is the classic > "simple_plot.py" sine wave, which tests sort of the "easy case" where > very little of the image is updated in each frame, and the other was > "animation/dynamic_image.py" in which most of the plot is updated in > each frame. > > I tested both scenarios with client and server on my local machine, and > through an ssh tunnel that goes over wifi, the public university > network, to my home's 15/5 MBps cable connection 28 miles away and back. > > For (A), the average frame weighs in at around 20kb. For (B), it's > around 90kb. For base64, multiply by those numbers by 4 / 3. > > On my local machine, I can push through about 18 fps, so a bandwidth of > 2.8MBps (were it sustained, which it rarely is). On the tunnel, I > fluctuate between 7 and 10 fps, which is quite usable, and quite near > the practical upper limit on the bandwidth of that connection. > > However, the problematic thing for the remote connection is the > latency. Locally, I average a fairly steady 250ms to roundtrip from a > mouse event to an updated frame. Remotely, it fluctuates randomly > between 400ms (still usable) and 3000ms. Some more careful dynamic > scaling of events can probably make that easier to use, perhaps. I know > games often use UDP and handle robustness to packet loss in a different > way as a way to remove some of the latency of TCP. I have no idea if > such a thing would be possible over a web socket, of course. > > I could not measure any statistically significant change in framerate or > latency between a binary websocket and a non-binary one. However, there > is a 10% increase in CPU time on both the python side and the browser. > It so happens that I wasn't saturating my CPU, so it had no net impact. > Likewise, I am not saturating my bandwidth, so the additional size > doesn't matter in this case. But I suspect if either one of those > resources is starved, the additional 10% cpu time and 25% bandwidth > increase may matter. > Thanks for these numbers - I suspect the potential penalty for an extra hop between the kernel and the notebook will not be significant in any case where the kernel is local to the server and the client is remote. -MinRK > > Mike > _______________________________________________ > IPython-dev mailing list > IPy...@sc... > http://mail.scipy.org/mailman/listinfo/ipython-dev > |
|
From: Russell O. <ro...@uw...> - 2013-08-07 22:11:27
|
I am glad that the numpy and scipy projects are still creating binary installers for python.org python, but it is a serious problem for users of the matplotlib binary installers that they are so difficult to find. If a user googles for "numpy download" then the user finds this page <http://www.numpy.org> and the link Getting Numpy points to this page <http://www.scipy.org/install.html> which does not the binary installers at all. I agree that most users should probably use Anaconda or its ilk, but I think it would be good to mention the Mac and Windows python.org binary installers quite prominently after that. -- Russell On Aug 7, 2013, at 1:00 PM, Thomas Kluyver <th...@kl...> wrote: > On 7 August 2013 12:54, Russell E. Owen <ro...@uw...> wrote: > P.S. the Mac binary installer for numpy used to be easy to find. I was > quite dismayed to find how buried it had become when I went looking for > it a week or two ago. > > Is this down to the redesign of the SciPy site. If so, blame me ;-). I felt, and others seemed to agree, that setting up individual packages separately wasn't a route that we wanted to promote to newcomers, so the new site emphasises all-in-one installers that get you the whole Scipy Stack (numpy, scipy, matplotlib, etc.) in one go. > > Thomas |
|
From: Benjamin R. <ben...@ou...> - 2013-08-07 21:13:55
|
On Wed, Aug 7, 2013 at 4:00 PM, Thomas Kluyver <th...@kl...> wrote: > On 7 August 2013 12:54, Russell E. Owen <ro...@uw...> wrote: > >> P.S. the Mac binary installer for numpy used to be easy to find. I was >> quite dismayed to find how buried it had become when I went looking for >> it a week or two ago. >> > > Is this down to the redesign of the SciPy site. If so, blame me ;-). I > felt, and others seemed to agree, that setting up individual packages > separately wasn't a route that we wanted to promote to newcomers, so the > new site emphasises all-in-one installers that get you the whole Scipy > Stack (numpy, scipy, matplotlib, etc.) in one go. > > Thomas > > All-in-one installers are fine, but I don't think it should exclude access to the individual installers as well (for the intermediate users, for example). Ben Root |
|
From: Thomas K. <th...@kl...> - 2013-08-07 20:32:36
|
On 7 August 2013 12:54, Russell E. Owen <ro...@uw...> wrote: > P.S. the Mac binary installer for numpy used to be easy to find. I was > quite dismayed to find how buried it had become when I went looking for > it a week or two ago. > Is this down to the redesign of the SciPy site. If so, blame me ;-). I felt, and others seemed to agree, that setting up individual packages separately wasn't a route that we wanted to promote to newcomers, so the new site emphasises all-in-one installers that get you the whole Scipy Stack (numpy, scipy, matplotlib, etc.) in one go. Thomas |
|
From: Russell E. O. <ro...@uw...> - 2013-08-07 19:54:46
|
In article <51F...@st...>, Michael Droettboom <md...@st...> wrote: > Ludwig, this is one of the most entertaining e-mails I've read in a > while, and I think your arguments make a lot of sense. > > Given infinite developer resources, do you think there's any logic to > providing *both* system Python and python.org based binaries? How much > additional work would that be? > > I think the big problems to solve now is > > (a) get to the bottom of why the new installer is breaking existing > installations of dateutil and pytz. Russell: even though they are not > currently working, could you provide what you have so that others can > have a look? I put the installer here (and announced it earlier -- I thought in this thread): <http://www.astro.washington.edu/users/rowen/python/> I do not consider it safe because: - It may trash existing installations of dateutil and pytz (especially those installed by the matplotlib 1.2.1 binary installer) - It does not include pytz, dateutil and six (unlike the 1.2.1 binary installer), so it's a real pain to use - It is missing its unit tests and so is poorly tested - It also appears that pylab is broken (something I only recently discovered) Unless somebody figures out how to include the dependencies, I think a Mac binary installer is a nonstarter. -- Russell P.S. the Mac binary installer for numpy used to be easy to find. I was quite dismayed to find how buried it had become when I went looking for it a week or two ago. |
127 messages has been excluded from this view by a project administrator.
