[EMAIL PROTECTED]:~$ python
Python 2.5a0 (#4, Dec 14 2005, 22:08:59)
[GCC 3.3.5 (Debian 1:3.3.5-8ubuntu2)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from xml.etree import ElementTree as ET
>>> ET
>>>
Thanks for fix.
--
http://mail.python.org/mailman/l
> > When launching ./python from ./trunk, everything is OK. Is it a problem
> > with me or with installation?
>
> things are being moved around, and installation seems to be broken at the
> moment (it doesn't install the Lib/xmlcore tree)
if you have time, can you update and try again ?
(let me k
Gregory Petrosyan wrote:
> This I've got after
>
> make install
>
> and
>
> [EMAIL PROTECTED]:~$ python
>
> When launching ./python from ./trunk, everything is OK. Is it a problem
> with me or with installation?
things are being moved around, and installation seems to be broken at the
moment (it
Istvan Albert wrote:
> don't know how this works, the link now seems to be:
>
> http://svn.python.org/view/python/trunk/Lib/xmlcore/etree/
people are moving things around, but xml.etree.ElementTree should still
work when they're done.
("xml" dispatches to either xmlcore or _xmlplus, depending on
Istvan Albert wrote:
>>$ python
>>Python 2.5a0 (#1, Dec 12 2005, 19:26:49)
>>
import xml.etree.ElementTree as ET
>
>
> hip hip hurray!
>
>
>>http://svn.python.org/view/python/trunk/Lib/xml/etree/
>
>
> don't know how this works, the link now seems to be:
>
> http://svn.python.org/view/py
> $ python
> Python 2.5a0 (#1, Dec 12 2005, 19:26:49)
>>> import xml.etree.ElementTree as ET
hip hip hurray!
> http://svn.python.org/view/python/trunk/Lib/xml/etree/
don't know how this works, the link now seems to be:
http://svn.python.org/view/python/trunk/Lib/xmlcore/etree/
--
http://mail.
This I've got after
make install
and
[EMAIL PROTECTED]:~$ python
When launching ./python from ./trunk, everything is OK. Is it a problem
with me or with installation?
--
http://mail.python.org/mailman/listinfo/python-list
[EMAIL PROTECTED]:~$ python
Python 2.5a0 (#1, Dec 14 2005, 14:11:55)
[GCC 3.3.5 (Debian 1:3.3.5-8ubuntu2)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import xml.etree.ElementTree as ET
Traceback (most recent call last):
File "", line 1, in
File "/usr/l
[EMAIL PROTECTED] wrote:
> ElementTree on the other hand provides incredibly easy access to XML
> elements and works in a more Pythonic way. Why has the API not been
> included in the Python core?
$ svn up
$ make
...
$ python
Python 2.5a0 (#1, Dec 12 2005, 19:26:49)
>>> import xml.etree.Element
[EMAIL PROTECTED] wrote:
> >> ElementTree on the other hand provides incredibly easy access to XML
> >> elements and works in a more Pythonic way. Why has the API not been
> >> included in the Python core?
>
> Magnus> I'd really like to see that too. Sure, it's fairly trivial to
>
[EMAIL PROTECTED] wrote:
> I think the key here is ElementTree's Pythoninc API. While it's clearly
> possible to install it as a third-party package, I think there's a clear
> best-of-breed aspect here that suggests it belongs in the standard
> distribution simply to discourage continued use of DO
> I still hope that the standard distribution will, in a not too distant future,
> bundle more external libraries. as things are today, "including something
> in the core" means that you have to transfer code and rights to the PSF.
Your description of how to include something in the core isn't en
>> ElementTree on the other hand provides incredibly easy access to XML
>> elements and works in a more Pythonic way. Why has the API not been
>> included in the Python core?
I think the key here is ElementTree's Pythoninc API. While it's clearly
possible to install it as a third-pa
>> ElementTree on the other hand provides incredibly easy access to XML
>> elements and works in a more Pythonic way. Why has the API not been
>> included in the Python core?
Magnus> I'd really like to see that too. Sure, it's fairly trivial to
Magnus> install it, but each di
Fredrik Lundh wrote:
> but seriously, given how easy it is to build things with distutils, I don't
> think your
> configuration folks would have much trouble adding support for "anything that
> has
> a setup file, and is reasonably self-contained" to their build scripts.
True. It's one more thin
Giovanni Bajo wrote:
> One thing I really fear about the otherwise great EasyInstall (and
> Python Eggs) is that we could forget about...
... how important is to have a standard library. The fact that it's easy to
install external modules shouldn't make us drop the standard library. A
standard li
[EMAIL PROTECTED] wrote:
>> I think some people were hoping that instead of adding these things
>> to
>> the standard library, we would come up with a better package manager
>> that would make adding these things to your local library much
>> simpler.
>>
>> STeVe
>>
>>
[1]http://www.python.org/dev
Fredrik Lundh wrote:
> Steven Bethard wrote:
>
> > > ElementTree on the other hand provides incredibly easy access to XML
> > > elements and works in a more Pythonic way. Why has the API not been
> > > included in the Python core?
> >
> > While I fully agree that ElementTree is far more Pythonic
Magnus Lycka wrote:
> We're deploying our software on a number of different platforms. We
> certainly depend on Python, so a standard Python install will always
> be included. Using standard library modules is for free. Using yet
> another third party library has a cost, even if some Cheese Shop o
[EMAIL PROTECTED] wrote:
> ElementTree on the other hand provides incredibly easy access to XML
> elements and works in a more Pythonic way. Why has the API not been
> included in the Python core?
I'd really like to see that too. Sure, it's fairly trivial to install
it, but each different package
<[EMAIL PROTECTED]> wrote:
...
> seems to be asking a lot for some people.) And at some
> companies, one has to jump though beauracratic hoops
> for each external package installed. And I personally
> stear away from packages that have a long list of
> prerequisites.
Funny -- me, I prefer to
"Fredrik Lundh" <[EMAIL PROTECTED]> writes:
> as I've said many times, if the Linux folks can build distributions that con-
> sists of thousands of individually maintained pieces, the Python distributors
> should be able to handle a few dozen components.
Yes, but "distributers" is not necessarily
Steven Bethard wrote:
--snip--
> I think some people were hoping that instead of adding these things to
> the standard library, we would come up with a better package manager
> that would make adding these things to your local library much simpler.
>
> STeVe
>
> [1]http://www.python.org/dev/summar
Before that can happen we'll need some better management of co-existing
different versions of a package. You'll want to be able to use newer
versions of external packages without breakage in the standard library.
--
http://mail.python.org/mailman/listinfo/python-list
Steven Bethard wrote:
> > ElementTree on the other hand provides incredibly easy access to XML
> > elements and works in a more Pythonic way. Why has the API not been
> > included in the Python core?
>
> While I fully agree that ElementTree is far more Pythonic than the
> dom-based stuff in the c
Steven Bethard napisał(a):
>> ElementTree on the other hand provides incredibly easy access to XML
>> elements and works in a more Pythonic way. Why has the API not been
>> included in the Python core?
>
> While I fully agree that ElementTree is far more Pythonic than the
> dom-based stuff in th
[EMAIL PROTECTED] wrote:
> ElementTree on the other hand provides incredibly easy access to XML
> elements and works in a more Pythonic way. Why has the API not been
> included in the Python core?
While I fully agree that ElementTree is far more Pythonic than the
dom-based stuff in the core, thi
Doug,
I agree with you, ElementTree is fast & pythonic.
Certainly does make sense to me.
--
http://mail.python.org/mailman/listinfo/python-list
Why is the ElementTree API not a part of the Python core?
I've recently been developing a script for accessing the Miva API only
to find all the core API's provided by Python for parsing XML is messy
and complicated. Many of the examples I see for parsing the data using
these API's uses a similar
29 matches
Mail list logo
