Guido van Rossum wrote:
On 12/12/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Martin It's difficult to establish precise numbers, but I would expect
Martin that most readers of xml-sig are well aware of how DOM and SAX
Martin work, perhaps even better than ElementTree.
Perhaps
Martin v. Löwis wrote:
[...]
It's difficult to establish precise numbers, but I would expect that
most readers of xml-sig are well aware of how DOM and SAX work, perhaps
even better than ElementTree.
My main complaint about this was in the past that it is a Python-only
solution, so
Walter Dörwald wrote:
Having to define classes that conform to a certain API and registering
instances of those classes as callbacks with the parser doesn't look
that pythonic to me. An iterator API seems much more pythonic.
If this is a comment on the ElementTree API, then /F must agree
On 12/12/05, Guido van Rossum [EMAIL PROTECTED] wrote:
Unfortunately that fails one of the other requirements, which (at the
time of implementation) was minimal impact on the rest of the
interpreter. Since __private isn't limited to self, and attribute
lookup doesn't always result in a dict
M.-A. Lemburg wrote:
Some questions:
* Are you going to contribute cElementTree as well ?
yes, but there are some build issues we need to sort out first (both pyexpat
and cET link to their own copies of expat)
we also need to figure out how to import the bundled version; should it be
BTW, what's the policy wrt. Jython-specific modules in the standard library?
Expat isn't available under Jython, but I have a Java/Jython-driver for
ElementTree
on my disk. Can / should this go into the CPython standard library ?
/F
___
Michael Hoffman wrote:
[Ian Bickling]
stdlib, external modules, internal modules seems like enough
ordering to me.
[Jim Fulton]
Personally, I don't find the stdlib/external distinction to be useful.
It's useful because it allows one to quickly see all the prerequisites
need to be
Fred L. Drake, Jr. wrote:
I'd like to propose that a new package be created in the standard library:
xmlcore. This package should contain what's currently in the xml package.
The xml package should be replaced with a single module that's responsible
for the magic that xml/__init__.py
I wrote:
1. add an Include/pyexpat.h header file which contains a structure
similar to the following:
2. during pyexpat initialization, initialize all members of this structure,
and
make it available as a PyCObject:
3. in cElementTree (or _elementtree, or whatever the python version will
On Tue, Dec 13, 2005 at 03:54:00PM -0500, Fred L. Drake, Jr. wrote:
I'd like to propose that a new package be created in the standard library:
xmlcore. This package should contain what's currently in the xml package.
+1; it's what should have been done in the first place.
--amk
On 12/13/05, Martin v. Löwis [EMAIL PROTECTED] wrote:
Fredrik Lundh wrote: BTW, what's the policy wrt. Jython-specific modules in the standard library?I don't think there is enough precedence to have a policy. So far, theonly places that explicitly support Jython is the test suite, pickle,
and
At 11:17 PM 12/13/2005 +0100, Fredrik Lundh wrote:
my current idea is to
1. include it under a different name (_elementtree.so)
2. add a cElementTree.py under xml.etree, which simply does
from _elementtree import *
does anyone have a better idea ?
I was under the
Armin Rigo [EMAIL PROTECTED] wrote:
On Mon, Dec 12, 2005 at 10:23:27PM +0100, Fredrik Lundh wrote:
$(AST_H) $(AST_C): $(AST_ASDL) $(ASDLGEN_FILES)
-$(PYTHON) $(ASDLGEN) $(AST_ASDL)
The same just-ignore-it behavior can bite if the script genuinely fails
after you just made a typo in
On Tuesday 13 December 2005 17:17, Fredrik Lundh wrote:
the remaining issue is how to include cElementTree. the current stand-
alone distribution consists of a single cElementTree module, which is in-
stalled under site-packages, as usual.
to avoid collisions, it's probably best to install
Patch / Bug Summary
___
Patches : 383 open (+11) / 2990 closed (+10) / 3373 total (+21)
Bugs: 927 open (+19) / 5415 closed (+20) / 6342 total (+39)
RFE : 204 open ( +4) / 192 closed ( +1) / 396 total ( +5)
New / Reopened Patches
__
use
Barry Warsaw wrote:
- If your class is intended to be subclassed, and you have attributes
that you do not want subclasses to use, consider naming them with
double leading underscores and no trailing underscores. This invokes
Python's name mangling algorithm,
On 12/13/05, Walter Dörwald [EMAIL PROTECTED] wrote:
Guido van Rossum wrote:
I don't think that SAX is unpythonic, but it's pretty low-level and
mostly of use to people writing higher-level XML parsers (my parsexml
module uses it).
Having to define classes that conform to a certain API
On 12/13/05, Neil Schemenauer [EMAIL PROTECTED] wrote:
Armin Rigo [EMAIL PROTECTED] wrote:
On Mon, Dec 12, 2005 at 10:23:27PM +0100, Fredrik Lundh wrote:
$(AST_H) $(AST_C): $(AST_ASDL) $(ASDLGEN_FILES)
-$(PYTHON) $(ASDLGEN) $(AST_ASDL)
The same just-ignore-it behavior can bite if
Michael McLay wrote:
Avoiding imaginaary name collisions and putting cElementTree into the xml
package
there's nothing imaginary here -- cElementTree is an existing and quite popular
module, and will remain available as a separate distribution.
it would be nice if people could install that
On Tuesday 13 December 2005 18:40, A.M. Kuchling wrote:
+1; it's what should have been done in the first place.
If only I'd understood that when I added the xml/PyXML hack to the stdlib
years ago. :-(
Fixed now. I'll deal with the documentation in a few days; I actually expect
to have some
20 matches
Mail list logo
