Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
(8) |
Dec
(51) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(105) |
Feb
(93) |
Mar
(194) |
Apr
(145) |
May
(100) |
Jun
(111) |
Jul
(117) |
Aug
(126) |
Sep
(233) |
Oct
(138) |
Nov
(164) |
Dec
(109) |
| 2002 |
Jan
(216) |
Feb
(175) |
Mar
(216) |
Apr
(194) |
May
(157) |
Jun
(140) |
Jul
(158) |
Aug
(73) |
Sep
(105) |
Oct
(164) |
Nov
(104) |
Dec
(95) |
| 2003 |
Jan
(72) |
Feb
(69) |
Mar
(81) |
Apr
(151) |
May
(101) |
Jun
(139) |
Jul
(99) |
Aug
(118) |
Sep
(115) |
Oct
(151) |
Nov
(161) |
Dec
(102) |
| 2004 |
Jan
(120) |
Feb
(175) |
Mar
(106) |
Apr
(111) |
May
(54) |
Jun
(78) |
Jul
(76) |
Aug
(105) |
Sep
(94) |
Oct
(143) |
Nov
(75) |
Dec
(85) |
| 2005 |
Jan
(99) |
Feb
(77) |
Mar
(164) |
Apr
(97) |
May
(79) |
Jun
(57) |
Jul
(65) |
Aug
(102) |
Sep
(95) |
Oct
(129) |
Nov
(123) |
Dec
(52) |
| 2006 |
Jan
(48) |
Feb
(99) |
Mar
(90) |
Apr
(51) |
May
(81) |
Jun
(136) |
Jul
(56) |
Aug
(109) |
Sep
(50) |
Oct
(44) |
Nov
(74) |
Dec
(75) |
| 2007 |
Jan
(92) |
Feb
(137) |
Mar
(93) |
Apr
(79) |
May
(52) |
Jun
(74) |
Jul
(143) |
Aug
(175) |
Sep
(154) |
Oct
(137) |
Nov
(88) |
Dec
(90) |
| 2008 |
Jan
(58) |
Feb
(113) |
Mar
(167) |
Apr
(88) |
May
(105) |
Jun
(37) |
Jul
(87) |
Aug
(72) |
Sep
(56) |
Oct
(41) |
Nov
(102) |
Dec
(70) |
| 2009 |
Jan
(115) |
Feb
(113) |
Mar
(126) |
Apr
(58) |
May
(125) |
Jun
(45) |
Jul
(90) |
Aug
(125) |
Sep
(84) |
Oct
(61) |
Nov
(111) |
Dec
(61) |
| 2010 |
Jan
(85) |
Feb
(86) |
Mar
(130) |
Apr
(58) |
May
(57) |
Jun
(32) |
Jul
(25) |
Aug
(50) |
Sep
(41) |
Oct
(65) |
Nov
(63) |
Dec
(24) |
| 2011 |
Jan
(43) |
Feb
(31) |
Mar
(28) |
Apr
(68) |
May
(53) |
Jun
(42) |
Jul
(58) |
Aug
(26) |
Sep
(51) |
Oct
(76) |
Nov
(60) |
Dec
(9) |
| 2012 |
Jan
(16) |
Feb
(32) |
Mar
(32) |
Apr
(39) |
May
(16) |
Jun
(19) |
Jul
(3) |
Aug
(11) |
Sep
(35) |
Oct
(47) |
Nov
(28) |
Dec
(18) |
| 2013 |
Jan
(18) |
Feb
(36) |
Mar
(10) |
Apr
(7) |
May
(7) |
Jun
(27) |
Jul
(17) |
Aug
(35) |
Sep
(19) |
Oct
(31) |
Nov
(8) |
Dec
(22) |
| 2014 |
Jan
(5) |
Feb
(11) |
Mar
(18) |
Apr
(23) |
May
(26) |
Jun
(14) |
Jul
(18) |
Aug
(26) |
Sep
(20) |
Oct
(48) |
Nov
(13) |
Dec
(9) |
| 2015 |
Jan
(9) |
Feb
(15) |
Mar
(25) |
Apr
(10) |
May
(26) |
Jun
(6) |
Jul
(13) |
Aug
(5) |
Sep
(14) |
Oct
(36) |
Nov
(24) |
Dec
(18) |
| 2016 |
Jan
(24) |
Feb
(11) |
Mar
(1) |
Apr
(6) |
May
(7) |
Jun
(3) |
Jul
(9) |
Aug
(15) |
Sep
(22) |
Oct
(5) |
Nov
(5) |
Dec
(2) |
| 2017 |
Jan
(20) |
Feb
(4) |
Mar
(4) |
Apr
(1) |
May
(5) |
Jun
(7) |
Jul
(14) |
Aug
(9) |
Sep
(18) |
Oct
(2) |
Nov
(3) |
Dec
(3) |
| 2018 |
Jan
(7) |
Feb
(6) |
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
1
|
|
2
(1) |
3
(1) |
4
(5) |
5
(4) |
6
|
7
(4) |
8
|
|
9
|
10
|
11
(10) |
12
|
13
|
14
|
15
|
|
16
|
17
(2) |
18
|
19
|
20
(5) |
21
(1) |
22
(2) |
|
23
|
24
|
25
(10) |
26
(7) |
27
(2) |
28
|
29
|
|
30
(1) |
31
(2) |
|
|
|
|
|
|
From: Chuck Bearden <cfbearden@gm...> - 2010-05-25 18:46:46
|
On Tue, May 25, 2010 at 1:40 PM, Alan Kennedy <jython-dev@...> wrote: > [Chuck] >> The DOM Level 1 and Level 2 [1] recommendations have this: >> >> "When a document is first made available via the DOM, there is only one >> Text node for each block of text." >> >> In the source context, "first made available" sounds like the point at >> which the DOM is hot off the press, er, parser. The CPython minidom >> implementation always presents text nodes as if normalized, in my >> experience. > > OK, that sounds reasonably definitive, in which case we're not compliant. > > Please can I ask you to place your comment, along with a supporting > link, on the bug, so that we have a full record. > > minidom chunks the character input on multi-line values > http://bugs.jython.org/issue1614 Done. Thanks for your work on this. Best wishes, Chuck |
|
From: Alan Kennedy <jython-dev@xh...> - 2010-05-25 18:41:03
|
[Chuck] > The DOM Level 1 and Level 2 [1] recommendations have this: > > "When a document is first made available via the DOM, there is only one > Text node for each block of text." > > In the source context, "first made available" sounds like the point at > which the DOM is hot off the press, er, parser. The CPython minidom > implementation always presents text nodes as if normalized, in my > experience. OK, that sounds reasonably definitive, in which case we're not compliant. Please can I ask you to place your comment, along with a supporting link, on the bug, so that we have a full record. minidom chunks the character input on multi-line values http://bugs.jython.org/issue1614 Or if you don't to register on the bug tracker, I'll copy it there on your behalf. Many thanks, Alan. |
|
From: Chuck Bearden <cfbearden@gm...> - 2010-05-25 18:31:49
|
On Tue, May 25, 2010 at 1:12 PM, Alan Kennedy <jython-dev@...> wrote: > [Chuck] >> It looks like the W3C DOM at both levels 1 & 2 stipulate that adjacent >> text children of an element be presented as a single Text node [1], >> and this seems to be what the CPython minidom does. Both minidoms >> purport to be DOM-1 compliant, with some DOM-2 extensions. I take it >> that the Jython minidom is not entirely compatible with the CPython >> one, and not compliant in this regard with the DOM standard. > > Whether or not adjacent text nodes are added together depends on > whether or not the DOM has been "normalized". > > http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-normalize > > I can't find any reference for whether a DOM should be auto-normalized > when first loaded. If it should be automatically normalized, then > jython is defective here. The DOM Level 1 and Level 2 [1] recommendations have this: "When a document is first made available via the DOM, there is only one Text node for each block of text." In the source context, "first made available" sounds like the point at which the DOM is hot off the press, er, parser. The CPython minidom implementation always presents text nodes as if normalized, in my experience. Thanks for fixing the Unicode decode problem for strings in the XML libraries. [1] <http://www.w3.org/TR/REC-DOM-Level-1/level-one-core.html#ID-1312295772>; <http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-1312295772>; Chuck |
|
From: Alan Kennedy <jython-dev@xh...> - 2010-05-25 18:15:30
|
[Chuck] >> It looks like the W3C DOM at both levels 1 & 2 stipulate that adjacent >> text children of an element be presented as a single Text node [1], >> and this seems to be what the CPython minidom does. Both minidoms >> purport to be DOM-1 compliant, with some DOM-2 extensions. I take it >> that the Jython minidom is not entirely compatible with the CPython >> one, and not compliant in this regard with the DOM standard. [Alan] > Whether or not adjacent text nodes are added together depends on > whether or not the DOM has been "normalized". > > http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-normalize I see that the OP has already open a bug for this: we'll continue discussion there. minidom chunks the character input on multi-line values http://bugs.jython.org/issue1614 Regards, Alan. |
|
From: Alan Kennedy <jython-dev@xh...> - 2010-05-25 18:12:23
|
[Chuck] > It looks like the W3C DOM at both levels 1 & 2 stipulate that adjacent > text children of an element be presented as a single Text node [1], > and this seems to be what the CPython minidom does. Both minidoms > purport to be DOM-1 compliant, with some DOM-2 extensions. I take it > that the Jython minidom is not entirely compatible with the CPython > one, and not compliant in this regard with the DOM standard. Whether or not adjacent text nodes are added together depends on whether or not the DOM has been "normalized". http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-normalize I can't find any reference for whether a DOM should be auto-normalized when first loaded. If it should be automatically normalized, then jython is defective here. If the DOM should not be auto-normalized, then carrying out a normalize() operation on the DOM will certainly ensure that adjacent text nodes should be grouped together. If jython does not return the expected results after a normalize() operation, then it is definitely defective: this should reported as a bug on the bug tracker. > One other thing I noticed is that, for a text node foo, foo.data is of > type 'str', while in CPython all text nodes in DOM trees (as well as > the corresponding constructs in other XML APIs) are Unicode objects. > The Jython behavior is problematic unless you can make assumptions > about the encoding of the text data. I seem to recall reading that > character data in the Python XML standard libraries is always > represented as Unicode rather than string objects. I fixed this bug in trunk (and then Phil Jenvey fixed it properly): unfortunately the fix won't be a part of a release until jython 2.5.2, unless you can upgrade to trunk. xml.dom.Node.data returns bytestrings of decoded unicode http://bugs.jython.org/issue1583 Regards, Alan. |
|
From: <jmpmega-11@ya...> - 2010-05-25 15:20:57
|
Hello, Can anyone provide me with some suggestions for how to handle the console window on Windows? I am having two problems that I would appreciate input on: (1) When using Swing, I would prefer that no console window was launched (like with Python's pythonw launcher) (2) When running a script that encounters an error, the console disappears when the program exits, so I don't have time to read the messages I'm sure these must be frequent questions, but I did not see them answered in the FAQ. Much obliged for any suggestions, J |
|
From: Chuck Bearden <cfbearden@gm...> - 2010-05-25 15:09:49
|
On Tue, May 25, 2010 at 7:15 AM, Stefan Gabriëls
<stefan.gabriels@...> wrote:
> Hello,
>
> When reading the value of character data in xml, ie
>
> from xml.dom import minidom
>
> s = '''<xml>line1
> line2
> line3
> line4</xml>'''
>
> dom = minidom.parseString(s)
> xml = dom.getElementsByTagName("xml")[0]
> xml_text = xml.childNodes[0].nodeValue
> print xml_text
> # prints:
> # line1
> # line2
>
> the output is restricted to the first two lines while
> xml.childNodes[1].nodeValue contains the next two lines. In CPython
> the full contents are read into xml.childNodes[0]. I'm wondering if
> the Jython way is a bug or if it's an implementation detail. What I
> want is the full contents, so now I do
>
> xml_text = ''
> for text_node in xml.childNodes:
> xml_text += text_node.nodeValue
>
> Would this be a good solution?
>
> Thanks!
>
> So I'm wondering if this is a bug or a
It looks like the W3C DOM at both levels 1 & 2 stipulate that adjacent
text children of an element be presented as a single Text node [1],
and this seems to be what the CPython minidom does. Both minidoms
purport to be DOM-1 compliant, with some DOM-2 extensions. I take it
that the Jython minidom is not entirely compatible with the CPython
one, and not compliant in this regard with the DOM standard.
One other thing I noticed is that, for a text node foo, foo.data is of
type 'str', while in CPython all text nodes in DOM trees (as well as
the corresponding constructs in other XML APIs) are Unicode objects.
The Jython behavior is problematic unless you can make assumptions
about the encoding of the text data. I seem to recall reading that
character data in the Python XML standard libraries is always
represented as Unicode rather than string objects.
[1] <http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/level-one-core.html#ID-1312295772>;
<http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/core.html#ID-1312295772>;
Chuck
|
|
From: Stefan Gabriëls <stefan.gabriels@gm...> - 2010-05-25 12:45:12
|
Hello,
When reading the value of character data in xml, ie
from xml.dom import minidom
s = '''<xml>line1
line2
line3
line4</xml>'''
dom = minidom.parseString(s)
xml = dom.getElementsByTagName("xml")[0]
xml_text = xml.childNodes[0].nodeValue
print xml_text
# prints:
# line1
# line2
the output is restricted to the first two lines while
xml.childNodes[1].nodeValue contains the next two lines. In CPython
the full contents are read into xml.childNodes[0]. I'm wondering if
the Jython way is a bug or if it's an implementation detail. What I
want is the full contents, so now I do
xml_text = ''
for text_node in xml.childNodes:
xml_text += text_node.nodeValue
Would this be a good solution?
Thanks!
So I'm wondering if this is a bug or a
|
|
From: Alex Grönholm <alex.gronholm@ne...> - 2010-05-25 05:53:48
|
25.5.2010 7:16, Vigneshwaran Gopalan kirjoitti: > Hi , > > > While I try to run PyWinAuto from Jython, I get the following error. > *ImportError: No module named _ctypes* > I have included the ctypes folder in the Jython search path; still > I get > this error. > Kindly someone help me to get out of this issue. AFAIK Jython does not support ctypes yet. It's being worked on, though. > > Thanks in advance > Vignesh > > > ------------------------------------------------------------------------------ > > > > > _______________________________________________ > Jython-users mailing list > Jython-users@... > https://lists.sourceforge.net/lists/listinfo/jython-users > |
|
From: Vigneshwaran Gopalan <vigneshwaran.gopalan@gm...> - 2010-05-25 04:16:25
|
Hi , While I try to run PyWinAuto from Jython, I get the following error. *ImportError: No module named _ctypes* I have included the ctypes folder in the Jython search path; still I get this error. Kindly someone help me to get out of this issue. Thanks in advance Vignesh |