alex23 wuwei23 at gmail.com
Sat Dec 24 08:52:24 EST 2011

• Previous message (by thread): Early and late binding [was Re: what does 'a=b=c=[]' do]
• Next message (by thread): Early and late binding [was Re: what does 'a=b=c=[]' do]
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Dec 24, 2:27 am, Mel Wilson <mwil... at the-wire.com> wrote:
> In a tool that's meant for other people to use to accomplish work of their
> own, breaking workflow is a cardinal sin.
>
> In a research language that's meant always to be up-to-date with the concept
> of the week, not so much.

What on earth gave you the impression Python was bleeding edge? As
there's more to the language than its syntax, "breaking workflow"
disrupts the core library as much as it does the code of everyone
else.

More importantly, you're talking pap. Research is as much about
communication as programming; if you expect every single researcher in
a discipline (or even in the same _building_) to remain in perfect
lockstep with the version releases of a domain-relevant language,
you're either not a researcher or not a very good one. You should get
out to a conference occasionally and see what people think about your
"concept of the week" idea.

---

• Previous message (by thread): Early and late binding [was Re: what does 'a=b=c=[]' do]
• Next message (by thread): Early and late binding [was Re: what does 'a=b=c=[]' do]
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-list mailing list