Alex Martelli wrote:
Fredrik Lundh <[EMAIL PROTECTED]> wrote:
Markus Wankus wrote:
Google his name - he has been banned from Netbeans and Eclipse (and
Hibernate, and others...) for good reason. Can you imagine how much of
a Troll you need to be to *actually* get "banned" from the newsgroups of
o
Istvan Albert wrote:
[EMAIL PROTECTED] wrote:
it seems to be invalid syntax if I give "/a/b[0]" to the findall()
method. Does anyone know the correct syntax?
I think the proper mindset going in should be that
elementtree does not support xpath but that
there are some handy constructs that resemble
Gerhard Häring wrote:
MarcoL wrote:
I am a VB6 programmer and I would like to learn a new high level
language (instead of restarting from scratch with .NET), wich is
opensource and cross-platform, in order to develop cross-platform
business applications
Good for you! And Python is a good cho
[EMAIL PROTECTED] wrote:
A paper finding that OOP can lead to more buggy software is at
http://www.leshatton.org/IEEE_Soft_98a.html
[snip description of paper that compares C++ versus Pascal or C]
What papers have scientific evidence for OOP?
That's of course a good question. I'm sure also that com
Paul McGuire wrote:
"Martijn Faassen" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
Paul McGuire wrote:
[snip]
I would characterize the 80's as the transitional decade from structured
programming (which really started to hit its stride when Djikstra
published
&q
Peter Hansen wrote:
Martijn Faassen wrote:
Paul McGuire wrote:
"Martijn Faassen" <[EMAIL PROTECTED]> wrote in message
Yikes! (or better, "Jikes!" or even "Yijkes!"?) - my bad.
And he was on faculty at UT right here in Austin, too.
It's a very common mist
Jive wrote:
Isn't there a comp.lang.flame or something?
I've doublechecked, but I didn't see any significant flaming in this
article (and I'm generally not very tolerant of it). My PSU posting was
certainly not intended as a flame, in case that was misinterpreted.
What'd I miss?
Regards,
Martijn
Peter Hansen wrote:
Martijn Faassen wrote:
Peter Hansen wrote:
Well, in any case, thanks for setting the record straight, Martjin.
That of course also happens to me once every while. I can take care of
myself though -- Dijkstra however needs an advocate for the correct
spelling of his name in
Maxim Khesin wrote:
I am trying to do some xpath on
http://fluidobjects.com/doc.xhtml
but cannot get past 'point A' (that is, I am totally stuck):
import libxml2
mydoc = libxml2.parseDoc(text)
mydoc.xpathEval('/html')
[]
this returns an empty resultlist, which just seems plain wrong. Can anyone
t
Peter Hansen wrote:
Brian van den Broek wrote:
Peter Hansen said unto the world upon 2004-12-15 17:39:
I could easily see this thread descending into a flame war in,
oh, about another ten posts. That would be so freaky...
Without a doubt that is the most ignorant and small-minded thought
that ev
Luis M. Gonzalez wrote:
MarcoL wrote:
Hello,
I am a VB6 programmer and I would like to learn a new high level
language (instead of restarting from scratch with .NET...
I'd like to add that by going with Python, you'll also be able to
develop for .NET. Check this out: www.ironpython.com .
S
Luis M. Gonzalez wrote:
Martijn Faassen wrote:
Unfortunately this is currently not near production use, and whether
Microsoft is funding IronPython development is up in the air:
It's true that he Ironpython's mailing list is a little bit innactive,
but this is just because there&
Paul McGuire wrote:
[snip]
I would characterize the 80's as the transitional decade from structured
programming (which really started to hit its stride when Djikstra published
"Use of GOTO Considered Harmful") to OOP, and that OOP wasn't really
"joyful" until the early-to-mid 90's.
IMMEDIATE NOTICE
Fellow Pythoneers,
I've started an informal channel "#python2.8" on freenode. It's to
discuss the potential for a Python 2.8 version -- to see whether there
is interest in it, what it could contain, how it could facilitate
porting to Python 3, who would work on it, etc. If you are interested i
On 01/07/2014 01:19 AM, Chris Angelico wrote:
Can we get a run-down of everything that actually must be broken in
2.7 -> 3.3, that can't be backported via __future__, so we can start
cherry-picking which bits to break in 2.8? The biggest one is going to
be Unicode strings, for a large number of
Hi there,
I just tried this out with the future module to see what it actually
does, and I got this:
On 01/07/2014 01:54 PM, Martijn Faassen wrote:
First the Python 3 behavior:
py3str + py3str = py3str
Yup, of course.
py3bytes + py3bytes = py3bytes
Again of course.
py3str
Hi,
I've posted a documentation issue to the 'future' module which includes
a further evolution of my thinking. As I expected, the author of the
'future' module has thought this through more than I had:
https://github.com/PythonCharmers/python-future/issues/27
To get back to a hypothetical P
Hi there,
On 01/07/2014 06:00 PM, Chris Angelico wrote:
I'm still not sure how Python 2.8 needs to differ from 2.7. Maybe the
touted upgrade path is simply a Python 2.7 installer plus a few handy
libraries/modules that will now be preinstalled? These modules look
great (I can't say, as I don't h
On 01/08/2014 01:46 PM, Chris Angelico wrote:
On Wed, Jan 8, 2014 at 11:36 PM, Martijn Faassen wrote:
Well, in the original article I argue that it may be risky for the Python
community to leave the large 2.7 projects behind because they tend to be the
ones that pay us in the end.
I also
Hey,
I'm pointing out possible improvements that Python 2.8 could offer that
would help incremental porting efforts of applications. I'm pointing
about that helping application developers move forward incrementally may
be a worthwhile consideration. Like, there's money there.
You can point o
Hey,
On 01/08/2014 03:30 PM, Mark Lawrence wrote:
But to be serious why not stick with 2.x if there's no compelling reason
to move? Whatever happened to "if it ain't broke, don't fix it"?
That's fine for static applications that don't have to change.
Successful applications tend to grow new
Jarek Zgoda wrote:
[snip]
>> It's a shame the default ns behavior in Elementtree is in such a poort
>> staten. I'm surprised no one's forked Elementtree solely to fix this
>> issue.
>
> There is at least one ElementTree API implementation that retains
> prefixes, lxml.ETree. Go google for it.
22 matches
Mail list logo
