T
Thomas Heller
QOTW?
That's a property of open source projects.
Features nobody really needs are not implemented.
That's what I love most about the Python community. Whenever there is
just a non-standard, platform-dependent or crappy implementation of a
feature you get told that you don't need it. When printf was good for
little David print is good enough for me.
Among the first things I examine about an IDE ( for Python ) is the
integration of a good REPL and how well recursive functions can be
debugged ( yes, I know, Pythonistas can't recurse and so it is not
recommended as well but sometimes ... )
Nicola Musatti said:No, no, you got it all wrong. It's in *commercial* projects that
features nobody really needs are not implemented.
No, no, squared. In a commercial project, the only features that get
implemented are the ones somebody is willing to pay for. Whether there is
any correlation between need and willingness to pay is an open question.
Kay said:That's what I love most about the Python community. Whenever there is
just a non-standard, platform-dependent or crappy implementation of a
feature you get told that you don't need it.
Nicola Musatti said:[...]
That's a property of open source projects.
Features nobody really needs are not implemented.No, no, you got it all wrong. It's in *commercial* projects that
features nobody really needs are not implemented.
No, no, squared. In a commercial project, the only features that get
implemented are the ones somebody is willing to pay for. Whether there is
any correlation between need and willingness to pay is an open question.
Then tell us, pray, who was willing to pay for the epitome of useless
features in MS Word, that Useless Features' Useless Feature, the
ability to format text with the animated effect "Marching Red Ants"?
I'm sure I paid for it, but it wasn't willingly...
No, no, you got it all wrong. It's in *commercial* projects that
features nobody really needs are not implemented. Profit is
fundamental in convincing you that you really need the features.
On the other hand open source projects tend to lack features nobody
enjoys implementing.
Cheers,
Nicola Musatti
P.S. Maybe I should add a ;-)
No, no, squared. In a commercial project, the only features that get
implemented are the ones somebody is willing to pay for. Whether there is
any correlation between need and willingness to pay is an open question.
Profit is fundamental in convincing you that you really
need the features.
.
Hi,
For experienced with Pyhton users, which developing software and
enviroment would you suggest for Pyhton programming? Compiler+Editor
+Debugger.Also what are your suggestions for beginners of Pyhton programming?Thank you.
I just wanted a simple answer to my simple question, however topic has
messed up. Think questioner as a beginner and use more understandable
terms to help
Thanks.
A fairly nice debugger is standard and built-in to the regular Python
distribution on all platforms.
But 95% of what a debugger is used for IME is getting a stack trace--
in Python (or Java or Ruby or most modern languages) you get that
automatically, and the debugger is nowhere near as useful as it is in
C or C++.
Hi,
For experienced with Pyhton users, which developing software and
enviroment would you suggest for Pyhton programming? Compiler+Editor
+Debugger.
Also what are your suggestions for beginners of Pyhton programming?
The problem is simply that the Python community has failed in this
respect. There are many platform dependent and ideology driven ways to
do deal with code editing / debugging but not actually a recommend or
"pythonic" way.
Other than Smalltalk, Python has not created an own
style / identity regarding decent development environments and since
half of the community is happy with Emacs and the other half wants to
program in a VS-like environment, neither consensus nor progress has
to be expected.
Kay Schluehr said:half of the community is happy with Emacs and the other half wants to
program in a VS-like environment, neither consensus nor progress has
I am a Python newbie, but unfortunately I don't agree with that. For
me having a debugger helped understand very quickly the flow
in the libraries for which otherwise I would have had to navigate
through code (which once again is not always easy without a good IDE).
But this is just a newbie opinion,
Kay said:The problem is simply that the Python community has failed in this
respect. There are many platform dependent and ideology driven ways to
do deal with code editing / debugging but not actually a recommend or
"pythonic" way. Other than Smalltalk, Python has not created an own
You should count your blessings. At least it doesn't play
pinball any more. At least, I hope not.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.