SourceForge logo
SourceForge logo
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
S M T W T F S


1
(1)
2
(15)
3
(11)
4
(7)
5
(9)
6
(9)
7
(13)
8
(6)
9
(4)
10
(1)
11
(6)
12
13
14
(2)
15
16
(2)
17
(5)
18
19
20
21
22
(2)
23
(4)
24
(7)
25
(8)
26
(5)
27
(2)
28
(11)
29
(6)
30
(5)
31
(6)


Showing 2 results of 2

From: Benjamin R. <ben...@ou...> - 2011年03月22日 21:48:54
On Tue, Mar 22, 2011 at 3:58 PM, Paul Ivanov <piv...@gm...> wrote:
> Hey everyone,
>
> Michael D and I are working on reducing the memory footprint of
> our test suite here at Sage days (we've made very good progress!),
> and came across a behavior of plt.clf() that we wanted feedback
> on.
>
> At the moment, plt.clf (i.e. fig.clf) do not clear all of the
> state variable associated with a figure. I think the most
> consistent thing to do is to have a clf() change the figure to be
> the same as a freshly created plt.figure(), but this is not the
> case. For example:
>
> In [5]: f = plt.figure()
>
> In [6]: f.subplotpars.left
> Out[6]: 0.055
>
> In [7]: f.subplotpars.left = .20
>
> In [8]: f.clf()
>
> In [9]: f.subplotpars.left
> Out[9]: 0.20000000000000001
>
> I propose making clf revert all variables back to their rcParams
> defaults (i.e. make it so that Out[9]: 0.055), and possibly
> creating a new rcParam to allow individuals to preserve the old
> behavior (in case people have code which relies on it, and prefer
> it to stay the same). Additionally, we could have an optional
> bolean parameter to clf, called 'scrub' or 'fresh' or something like
> that, which would implement the rcParam specified behavior by
> default, but allow users to scrub or not scrub on a call by call
> basis.
>
> Does anyone have any thoughts about this?
>
>
My feeling is that it should retain some properties such as the figure
size. Imagine a case where one would be creating figures for saving that is
made of multiple subplots:
fig = plt.figure(figsize=plt.figaspect(0.5))
for index, data in enumerate(datas) :
 ax = fig.add_subplot(1, 2, 1)
 ax.plot(data[0])
 ax = fig.add_subplot(1, 2, 2)
 ax.plot(data[1])
 fig.savefig("foo%d.png" % index)
 fig.clf()
In this case, I think it would be reasonable to expect that the figure
retains its size. Then again, maybe I am doing it wrong...
Just my 2 cents.
Ben Root
From: Paul I. <piv...@gm...> - 2011年03月22日 20:58:40
Hey everyone,
Michael D and I are working on reducing the memory footprint of
our test suite here at Sage days (we've made very good progress!),
and came across a behavior of plt.clf() that we wanted feedback
on.
At the moment, plt.clf (i.e. fig.clf) do not clear all of the
state variable associated with a figure. I think the most
consistent thing to do is to have a clf() change the figure to be
the same as a freshly created plt.figure(), but this is not the
case. For example:
In [5]: f = plt.figure()
In [6]: f.subplotpars.left
Out[6]: 0.055
In [7]: f.subplotpars.left = .20
In [8]: f.clf()
In [9]: f.subplotpars.left
Out[9]: 0.20000000000000001
I propose making clf revert all variables back to their rcParams
defaults (i.e. make it so that Out[9]: 0.055), and possibly
creating a new rcParam to allow individuals to preserve the old
behavior (in case people have code which relies on it, and prefer
it to stay the same). Additionally, we could have an optional
bolean parameter to clf, called 'scrub' or 'fresh' or something like
that, which would implement the rcParam specified behavior by
default, but allow users to scrub or not scrub on a call by call
basis.
Does anyone have any thoughts about this?
-- 
Paul Ivanov
314 address only used for lists, off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 

Showing 2 results of 2

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X





Briefly describe the problem (required):
Upload screenshot of ad (required):
Select a file, or drag & drop file here.
Screenshot instructions:

Click URL instructions:
Right-click on the ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies

Ad destination/click URL:

AltStyle によって変換されたページ (->オリジナル) /