On Thursday 16 February 2006 17:06, Martin v. Löwis wrote:
I'm still unhappy with that change, and still nobody has told me how to
maintain PyXML so that it can continue to work both for 2.5 and for 2.4.
Martin,
I do intend to write a proper response for you, but have been massively
(my mails to python-dev are bouncing; guess that's what you get when
you question the PSF's ability to build web sites... trying again.)
Neal Norwitz wrote:
(is the xmlplus/xmlcore issue still an issue, btw?)
What issue are you talking about?
the changes described here
Neal Norwitz wrote:
On 2/15/06, Alain Poirier [EMAIL PROTECTED] wrote:
- isn't the current implementation of itertools.tee (cache of previous
generated values) incompatible with the new possibility to feed a
generator (PEP 342) ?
I'm not sure what you are referring to. What is
(is the xmlplus/xmlcore issue still an issue, btw?)
What issue are you talking about?
the changes described here
http://mail.python.org/pipermail/python-dev/2005-December/058710.html
I'd like to propose that a new package be created in the standard library:
xmlcore.
which led
Fredrik Lundh wrote:
http://mail.python.org/pipermail/python-dev/2005-December/058752.html
I don't agree with the change. You just broke source compatibility
between the core package and PyXML.
I'm still unhappy with that change, and still nobody has told me how to
maintain PyXML
Hi,
2 questions:
- is (c)ElementTree still planned for inclusion ?
- isn't the current implementation of itertools.tee (cache of previous
generated values) incompatible with the new possibility to feed a
generator (PEP 342) ?
Regards
Neal Norwitz a écrit :
Attached is the 2.5
On Tue, Feb 14, 2006 at 09:58:46PM -0800, Neal Norwitz wrote:
We need to ensure that PEPs 308, 328, and 343 are implemented. We
have possible volunteers for 308 and 343, but not 328. Brett is doing
352 and Martin is doing 353.
I can volunteer for 328 if no one else wants it, I've messed
On Wed, Feb 15, 2006, Thomas Wouters wrote:
I can volunteer for 328 if no one else wants it, I've messed with the import
mechanism before (and besides, it's fun.) I've also written an unfinished
308 implementation to get myself acquainted with the AST code more.
'Unfinished' means that it
Alain Poirier wrote:
- is (c)ElementTree still planned for inclusion ?
It is included already.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
Martin v. Löwis wrote:
- is (c)ElementTree still planned for inclusion ?
It is included already.
in the xml.etree package, in case someone's looking for it in the
usual place.
that is,
import xml.etree.ElementTree as ET
import xml.etree.cElementTree as ET
will work in any 2.5
Neal Norwitz wrote:
Attached is the 2.5 release PEP 356. It's also available from:
http://www.python.org/peps/pep-0356.html
Does anyone have any comments? Is this good or bad? Feel free to
send to me comments.
We need to ensure that PEPs 308, 328, and 343 are implemented. We
have
On 2/15/06, Fredrik Lundh [EMAIL PROTECTED] wrote:
(is the xmlplus/xmlcore issue still an issue, btw?)
What issue are you talking about?
n
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
On 2/15/06, Alain Poirier [EMAIL PROTECTED] wrote:
- isn't the current implementation of itertools.tee (cache of previous
generated values) incompatible with the new possibility to feed a
generator (PEP 342) ?
I'm not sure what you are referring to. What is the issue?
n
Attached is the 2.5 release PEP 356. It's also available from:
http://www.python.org/peps/pep-0356.html
Does anyone have any comments? Is this good or bad? Feel free to
send to me comments.
We need to ensure that PEPs 308, 328, and 343 are implemented. We
have possible volunteers for 308
14 matches
Mail list logo
