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) |
|
|
Thanks for doing all this work. I've put your first patch up as a pull request here, so we can comment on it: https://github.com/matplotlib/matplotlib-py3/pull/7 The examples patch I will combine with my own work to get the print_function stuff consistent, and then put up a pull request for all of that when ready. Mike On 03/11/2011 02:12 PM, Christoph Gohlke wrote: > > On 3/11/2011 10:54 AM, Michael Droettboom wrote: > >> In examples/widgets/menu.py in your patch, you have the line: >> >> print(x,y,w,h) >> >> which prints "(1, 2, 3, 4)" on Python 2.x and "1 2 3 4" on Python 3.x. >> > I missed that one. > > Christoph > > >> On further thought, we should probably put "from __future__ import >> print_function" in all .py files whether they have print functions or >> not, just to avoid this confusion. I can submit that as a separate >> patch, though. >> >> Mike >> >> On 03/11/2011 12:33 PM, Christoph Gohlke wrote: >> >>> On 3/11/2011 8:54 AM, Michael Droettboom wrote: >>> >>> >>>> I think the examples with print functions need a: >>>> >>>> "from __future__ import print_function" >>>> >>>> otherwise, it prints tuples rather than treating the (...) as function >>>> arguments. >>>> >>>> Cheers, >>>> Mike >>>> >>>> >>> I changed all print statements to `print("a string")`, which prints a >>> string, not a tuple, on python 2 and python 3. >>> >>> Christoph >>> >>> >>> >>> >>>> On 03/10/2011 02:18 PM, Christoph Gohlke wrote: >>>> >>>> >>>>> On 3/9/2011 12:01 PM, Benjamin Root wrote: >>>>> >>>>> >>>>>> On Wed, Mar 9, 2011 at 5:23 AM, Christoph Gohlke<cg...@uc... >>>>>> <mailto:cg...@uc...> >>>>>> <mailto:cg...@uc...>> wrote: >>>>>> >>>>>> Hello, >>>>>> >>>>>> please consider the attached patch for the matplotlib-py3 CTPUG fork >>>>>> on github. The patch fixes several build and runtime issues/crashes. >>>>>> Tested on win-amd64-py3.2. >>>>>> >>>>>> Christoph >>>>>> >>>>>> >>>>>> Christoph, >>>>>> >>>>>> A quick point of style looking over this patch. Rather than renaming >>>>>> "collections" to "mplcollections", we really should follow our own >>>>>> conventions and call it "mcoll". The same is probably true for text and >>>>>> other matplotlib objects. >>>>>> >>>>>> http://matplotlib.sourceforge.net/devel/coding_guide.html#style-guide >>>>>> >>>>>> Then again, maybe some of these style changes should be made to master >>>>>> first and then merged into the py3k branch? The coding style is >>>>>> something we have been falling behind on and really should clean up at >>>>>> some point. >>>>>> >>>>>> As for the rest of it, I don't have enough experience with py3k to >>>>>> comment. >>>>>> >>>>>> Ben Root >>>>>> >>>>>> >>>>>> >>>>> OK. The revised patch changes the name to mcoll and fixes further >>>>> issues. I also reworked the examples to be compatible with Python 2.6+ >>>>> and 3.x without the need to run the 2to3 tool. On Windows all but >>>>> three examples now work on Python 3.2. >>>>> >>>>> Christoph >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Colocation vs. Managed Hosting >>>>> A question and answer guide to determining the best fit >>>>> for your organization - today and in the future. >>>>> http://p.sf.net/sfu/internap-sfd2d >>>>> >>>>> _______________________________________________ >>>>> Matplotlib-devel mailing list >>>>> Mat...@li...<mailto:Mat...@li...> >>>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >>>>> >>>>> >>>>> >>>> -- >>>> Michael Droettboom >>>> Science Software Branch >>>> Space Telescope Science Institute >>>> Baltimore, Maryland, USA >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Colocation vs. Managed Hosting >>>> A question and answer guide to determining the best fit >>>> for your organization - today and in the future. >>>> http://p.sf.net/sfu/internap-sfd2d >>>> >>>> >>>> >>>> _______________________________________________ >>>> Matplotlib-devel mailing list >>>> Mat...@li... >>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >>>> >>>> >>> ------------------------------------------------------------------------------ >>> Colocation vs. Managed Hosting >>> A question and answer guide to determining the best fit >>> for your organization - today and in the future. >>> http://p.sf.net/sfu/internap-sfd2d >>> _______________________________________________ >>> Matplotlib-devel mailing list >>> Mat...@li... >>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >>> >>> >> >> > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > -- Michael Droettboom Science Software Branch Space Telescope Science Institute Baltimore, Maryland, USA
On 3/11/2011 10:54 AM, Michael Droettboom wrote:
> In examples/widgets/menu.py in your patch, you have the line:
>
> print(x,y,w,h)
>
> which prints "(1, 2, 3, 4)" on Python 2.x and "1 2 3 4" on Python 3.x.
I missed that one.
Christoph
>
> On further thought, we should probably put "from __future__ import
> print_function" in all .py files whether they have print functions or
> not, just to avoid this confusion. I can submit that as a separate
> patch, though.
>
> Mike
>
> On 03/11/2011 12:33 PM, Christoph Gohlke wrote:
>>
>> On 3/11/2011 8:54 AM, Michael Droettboom wrote:
>>
>>> I think the examples with print functions need a:
>>>
>>> "from __future__ import print_function"
>>>
>>> otherwise, it prints tuples rather than treating the (...) as function
>>> arguments.
>>>
>>> Cheers,
>>> Mike
>>>
>> I changed all print statements to `print("a string")`, which prints a
>> string, not a tuple, on python 2 and python 3.
>>
>> Christoph
>>
>>
>>
>>> On 03/10/2011 02:18 PM, Christoph Gohlke wrote:
>>>
>>>>
>>>> On 3/9/2011 12:01 PM, Benjamin Root wrote:
>>>>
>>>>>
>>>>> On Wed, Mar 9, 2011 at 5:23 AM, Christoph Gohlke<cg...@uc...
>>>>> <mailto:cg...@uc...>
>>>>> <mailto:cg...@uc...>> wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> please consider the attached patch for the matplotlib-py3 CTPUG fork
>>>>> on github. The patch fixes several build and runtime issues/crashes.
>>>>> Tested on win-amd64-py3.2.
>>>>>
>>>>> Christoph
>>>>>
>>>>>
>>>>> Christoph,
>>>>>
>>>>> A quick point of style looking over this patch. Rather than renaming
>>>>> "collections" to "mplcollections", we really should follow our own
>>>>> conventions and call it "mcoll". The same is probably true for text and
>>>>> other matplotlib objects.
>>>>>
>>>>> http://matplotlib.sourceforge.net/devel/coding_guide.html#style-guide
>>>>>
>>>>> Then again, maybe some of these style changes should be made to master
>>>>> first and then merged into the py3k branch? The coding style is
>>>>> something we have been falling behind on and really should clean up at
>>>>> some point.
>>>>>
>>>>> As for the rest of it, I don't have enough experience with py3k to
>>>>> comment.
>>>>>
>>>>> Ben Root
>>>>>
>>>>>
>>>> OK. The revised patch changes the name to mcoll and fixes further
>>>> issues. I also reworked the examples to be compatible with Python 2.6+
>>>> and 3.x without the need to run the 2to3 tool. On Windows all but
>>>> three examples now work on Python 3.2.
>>>>
>>>> Christoph
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Colocation vs. Managed Hosting
>>>> A question and answer guide to determining the best fit
>>>> for your organization - today and in the future.
>>>> http://p.sf.net/sfu/internap-sfd2d
>>>>
>>>> _______________________________________________
>>>> Matplotlib-devel mailing list
>>>> Mat...@li...<mailto:Mat...@li...>
>>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>>
>>>>
>>>
>>> --
>>> Michael Droettboom
>>> Science Software Branch
>>> Space Telescope Science Institute
>>> Baltimore, Maryland, USA
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Colocation vs. Managed Hosting
>>> A question and answer guide to determining the best fit
>>> for your organization - today and in the future.
>>> http://p.sf.net/sfu/internap-sfd2d
>>>
>>>
>>>
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Mat...@li...
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>
>> ------------------------------------------------------------------------------
>> Colocation vs. Managed Hosting
>> A question and answer guide to determining the best fit
>> for your organization - today and in the future.
>> http://p.sf.net/sfu/internap-sfd2d
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>
>
In examples/widgets/menu.py in your patch, you have the line:
print(x,y,w,h)
which prints "(1, 2, 3, 4)" on Python 2.x and "1 2 3 4" on Python 3.x.
On further thought, we should probably put "from __future__ import
print_function" in all .py files whether they have print functions or
not, just to avoid this confusion. I can submit that as a separate
patch, though.
Mike
On 03/11/2011 12:33 PM, Christoph Gohlke wrote:
>
> On 3/11/2011 8:54 AM, Michael Droettboom wrote:
>
>> I think the examples with print functions need a:
>>
>> "from __future__ import print_function"
>>
>> otherwise, it prints tuples rather than treating the (...) as function
>> arguments.
>>
>> Cheers,
>> Mike
>>
> I changed all print statements to `print("a string")`, which prints a
> string, not a tuple, on python 2 and python 3.
>
> Christoph
>
>
>
>> On 03/10/2011 02:18 PM, Christoph Gohlke wrote:
>>
>>>
>>> On 3/9/2011 12:01 PM, Benjamin Root wrote:
>>>
>>>>
>>>> On Wed, Mar 9, 2011 at 5:23 AM, Christoph Gohlke<cg...@uc...
>>>> <mailto:cg...@uc...>
>>>> <mailto:cg...@uc...>> wrote:
>>>>
>>>> Hello,
>>>>
>>>> please consider the attached patch for the matplotlib-py3 CTPUG fork
>>>> on github. The patch fixes several build and runtime issues/crashes.
>>>> Tested on win-amd64-py3.2.
>>>>
>>>> Christoph
>>>>
>>>>
>>>> Christoph,
>>>>
>>>> A quick point of style looking over this patch. Rather than renaming
>>>> "collections" to "mplcollections", we really should follow our own
>>>> conventions and call it "mcoll". The same is probably true for text and
>>>> other matplotlib objects.
>>>>
>>>> http://matplotlib.sourceforge.net/devel/coding_guide.html#style-guide
>>>>
>>>> Then again, maybe some of these style changes should be made to master
>>>> first and then merged into the py3k branch? The coding style is
>>>> something we have been falling behind on and really should clean up at
>>>> some point.
>>>>
>>>> As for the rest of it, I don't have enough experience with py3k to
>>>> comment.
>>>>
>>>> Ben Root
>>>>
>>>>
>>> OK. The revised patch changes the name to mcoll and fixes further
>>> issues. I also reworked the examples to be compatible with Python 2.6+
>>> and 3.x without the need to run the 2to3 tool. On Windows all but
>>> three examples now work on Python 3.2.
>>>
>>> Christoph
>>>
>>> ------------------------------------------------------------------------------
>>> Colocation vs. Managed Hosting
>>> A question and answer guide to determining the best fit
>>> for your organization - today and in the future.
>>> http://p.sf.net/sfu/internap-sfd2d
>>>
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Mat...@li...<mailto:Mat...@li...>
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>
>>>
>>
>> --
>> Michael Droettboom
>> Science Software Branch
>> Space Telescope Science Institute
>> Baltimore, Maryland, USA
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Colocation vs. Managed Hosting
>> A question and answer guide to determining the best fit
>> for your organization - today and in the future.
>> http://p.sf.net/sfu/internap-sfd2d
>>
>>
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
--
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
Baltimore, Maryland, USA
On 3/11/2011 8:54 AM, Michael Droettboom wrote:
> I think the examples with print functions need a:
>
> "from __future__ import print_function"
>
> otherwise, it prints tuples rather than treating the (...) as function
> arguments.
>
> Cheers,
> Mike
I changed all print statements to `print("a string")`, which prints a
string, not a tuple, on python 2 and python 3.
Christoph
>
> On 03/10/2011 02:18 PM, Christoph Gohlke wrote:
>>
>>
>> On 3/9/2011 12:01 PM, Benjamin Root wrote:
>>>
>>>
>>> On Wed, Mar 9, 2011 at 5:23 AM, Christoph Gohlke <cg...@uc...
>>> <mailto:cg...@uc...>
>>> <mailto:cg...@uc...>> wrote:
>>>
>>> Hello,
>>>
>>> please consider the attached patch for the matplotlib-py3 CTPUG fork
>>> on github. The patch fixes several build and runtime issues/crashes.
>>> Tested on win-amd64-py3.2.
>>>
>>> Christoph
>>>
>>>
>>> Christoph,
>>>
>>> A quick point of style looking over this patch. Rather than renaming
>>> "collections" to "mplcollections", we really should follow our own
>>> conventions and call it "mcoll". The same is probably true for text and
>>> other matplotlib objects.
>>>
>>> http://matplotlib.sourceforge.net/devel/coding_guide.html#style-guide
>>>
>>> Then again, maybe some of these style changes should be made to master
>>> first and then merged into the py3k branch? The coding style is
>>> something we have been falling behind on and really should clean up at
>>> some point.
>>>
>>> As for the rest of it, I don't have enough experience with py3k to
>>> comment.
>>>
>>> Ben Root
>>>
>>
>> OK. The revised patch changes the name to mcoll and fixes further
>> issues. I also reworked the examples to be compatible with Python 2.6+
>> and 3.x without the need to run the 2to3 tool. On Windows all but
>> three examples now work on Python 3.2.
>>
>> Christoph
>>
>> ------------------------------------------------------------------------------
>> Colocation vs. Managed Hosting
>> A question and answer guide to determining the best fit
>> for your organization - today and in the future.
>> http://p.sf.net/sfu/internap-sfd2d
>>
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li... <mailto:Mat...@li...>
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>
>
>
> --
> Michael Droettboom
> Science Software Branch
> Space Telescope Science Institute
> Baltimore, Maryland, USA
>
>
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
I think the examples with print functions need a: "from __future__ import print_function" otherwise, it prints tuples rather than treating the (...) as function arguments. Cheers, Mike On 03/10/2011 02:18 PM, Christoph Gohlke wrote: > > > On 3/9/2011 12:01 PM, Benjamin Root wrote: >> >> >> On Wed, Mar 9, 2011 at 5:23 AM, Christoph Gohlke <cg...@uc... >> <mailto:cg...@uc...>> wrote: >> >> Hello, >> >> please consider the attached patch for the matplotlib-py3 CTPUG fork >> on github. The patch fixes several build and runtime issues/crashes. >> Tested on win-amd64-py3.2. >> >> Christoph >> >> >> Christoph, >> >> A quick point of style looking over this patch. Rather than renaming >> "collections" to "mplcollections", we really should follow our own >> conventions and call it "mcoll". The same is probably true for text and >> other matplotlib objects. >> >> http://matplotlib.sourceforge.net/devel/coding_guide.html#style-guide >> >> Then again, maybe some of these style changes should be made to master >> first and then merged into the py3k branch? The coding style is >> something we have been falling behind on and really should clean up at >> some point. >> >> As for the rest of it, I don't have enough experience with py3k to >> comment. >> >> Ben Root >> > > OK. The revised patch changes the name to mcoll and fixes further > issues. I also reworked the examples to be compatible with Python 2.6+ > and 3.x without the need to run the 2to3 tool. On Windows all but > three examples now work on Python 3.2. > > Christoph > > > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > > > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > -- Michael Droettboom Science Software Branch Space Telescope Science Institute Baltimore, Maryland, USA
On Wed, Mar 9, 2011 at 1:23 PM, OriolV <or...@ho...> wrote: > > Hi everyone, > > I get the same error ( 'ImportError: Warning: formlayout requires PyQt4 >>v4.3' ). I have spent a lot of hours but I am not able to solve it. I would > be very grateful if someone could let me know if there is a solution. > > Thanks in advance. Would you please try replacing your backend_qt4.py with the attached file and let me know if it solves the problem?