anatoly techtonik writes:
> Fernando clearly showed that IPython rocks, because CPython suxx.
No, IPython rocks because it focuses on doing one thing well:
providing an interactive environment that takes advantage of the many
features that Python provides in support. CPython should do the sam
On Mon, Dec 19, 2011 at 7:47 AM, Stephen J. Turnbull wrote:
> Fernando Perez writes:
>
> > Apology for the advertising,
>
> If there's any apologizing to be done, it's on Anatoly's part. Your
> post was short, to the point, information-packed, and should put a big
> fat open-centered ideographic
Fernando Perez writes:
> Apology for the advertising,
If there's any apologizing to be done, it's on Anatoly's part. Your
post was short, to the point, information-packed, and should put a big
fat open-centered ideographic full stop period to this thread.
__
On Fri, 23 Sep 2011 16:32:30 -0700, Guido van Rossum wrote:
> You can't fix this without completely changing the way the interactive
> console treats blank lines. None that it's not just that a blank line is
> required after a function definition -- you also *can't* have a blank
> line *inside* a
On 12/15/2011 3:58 AM, anatoly techtonik wrote:
1. It is not a proposal, but a defect (well, you may argue, but please,
don't)
You state a controversial opinion as a fact and then request that others
not discuss it. To me, this is a somewhat obnoxious hit-and-run tactic.
If you do not want t
Il 15 dicembre 2011 09:58, anatoly techtonik ha scritto:
> 1. It is not a proposal, but a defect (well, you may argue, but please,
> don't)>
You can't copy/paste multiline scripts into system shell either,
unless you append "\".
It's likely that similar problems exists in a lot of other interact
On Sat, Sep 24, 2011 at 11:27 AM, Georg Brandl wrote:
> Am 24.09.2011 01:32, schrieb Guido van Rossum:
> > On Fri, Sep 23, 2011 at 4:25 PM, anatoly techtonik
> wrote:
> >> Currently if you work in console and define a function and then
> >> immediately call it - it will fail with SyntaxError.
>
On 24/09/2011 00:32, Guido van Rossum wrote:
The interactive console is optimized for people entering code by
typing, not by copying and pasting large gobs of text.
If you think you can have it both, show us the code.
Anatoly wants ipython's new qtconsole.
This "does the right thing" because
I see a lot of flawed "proposals". This is clearly a python-ideas
discussion. (Anatoly, take note -- please post your new gripe there.)
In the mean time, there's a reasonable work-around if you have to
copy/paste a large block of formatted code:
>>> exec('''
.
.
.
.
.
.
''')
>>
You're right that in principle for function definitions there is no ambiguity.
But you also presented the downfall of that proposal: all multi-clause
statements will still need an explicit way of termination, and of course the
"pass" would be exceedingly ugly, not to mention much more confusing tha
Could you elaborate on what would be wrong if function definitions ended
only after an explicitly less indented line? The only problem that comes to
mind is global scope "if" statements that wouldn't execute when expected (we
actually might need to terminate them with a dedented "pass").
On Sep 24,
Am 24.09.2011 01:32, schrieb Guido van Rossum:
> On Fri, Sep 23, 2011 at 4:25 PM, anatoly techtonik
> wrote:
>> Currently if you work in console and define a function and then
>> immediately call it - it will fail with SyntaxError.
>> For example, copy paste this completely valid Python script in
On Fri, Sep 23, 2011 at 18:49, Terry Reedy wrote:
> A interactive lisp interpreter can detect end-of-statement without a blank
> line by matching a closing paren to the open paren that starts every
> expression.
Braces-loving programmers around the world are feverishly writing a
PEP as we speak.
On 9/23/2011 7:25 PM, anatoly techtonik wrote:
Currently if you work in console and define a function and then
immediately call it - it will fail with SyntaxError.
For example, copy paste this completely valid Python script into console:
def some():
print "XXX"
some()
There is an issue for t
I agree that it should and it doesn't. I also recall that not having empty
lines between function/class definitions can cause indentation errors when
pasting to the console on my windows machine.
--Yuval
On Sep 23, 2011 7:26 PM, "anatoly techtonik" wrote:
> Currently if you work in console and de
On Fri, Sep 23, 2011 at 4:25 PM, anatoly techtonik wrote:
> Currently if you work in console and define a function and then
> immediately call it - it will fail with SyntaxError.
> For example, copy paste this completely valid Python script into console:
>
> def some():
> print "XXX"
> some()
>
>
Currently if you work in console and define a function and then
immediately call it - it will fail with SyntaxError.
For example, copy paste this completely valid Python script into console:
def some():
print "XXX"
some()
There is an issue for that that was just closed by Eric. However, I'd
lik
17 matches
Mail list logo
