On Tue, Jul 22, 2014 at 4:30 AM, Terry Reedy wrote:
> It would be a lot of work for close to 0 gain. It could not work consistent
> without special-casing sys assignments.
The latter doesn't much matter (this is just a theory to help people
realize what they've done, not an actual preventative -
On 7/21/2014 6:56 AM, Chris Angelico wrote:
On Mon, Jul 21, 2014 at 7:00 PM, Terry Reedy wrote:
In general, Idle should execute user code the same way that the interpreter
does, subject to the limitations of the different execution environment.
Agreed, but I think the setting of prompts is a
On Mon, Jul 21, 2014 at 7:00 PM, Terry Reedy wrote:
> In general, Idle should execute user code the same way that the interpreter
> does, subject to the limitations of the different execution environment.
Agreed, but I think the setting of prompts is a "different execution
environment" case. It's
On 7/20/2014 11:34 PM, Chris Angelico wrote:
On Mon, Jul 21, 2014 at 1:28 PM, Terry Reedy wrote:
A few users have noticed (and complained) that setting sys.ps1 and sys.ps2
*in the batch mode user process* has no effect. The Idle doc should better
explain why this is and should be. User code sh
On 7/20/2014 9:22 PM, Rick Johnson wrote:
On Sunday, July 20, 2014 4:52:36 PM UTC-5, Terry Reedy wrote:
The *real* problem is that the "interactive events" of the
"editor window" and the "interactive events" of the "shell
window" are far too tightly integrated with one another.
I myself appre
On Mon, Jul 21, 2014 at 1:28 PM, Terry Reedy wrote:
> A few users have noticed (and complained) that setting sys.ps1 and sys.ps2
> *in the batch mode user process* has no effect. The Idle doc should better
> explain why this is and should be. User code should not affect the
> operation of Idle. I
On 7/20/2014 8:55 PM, Chris Angelico wrote:
Idea 4 (which I already suggested on the tracker). Put statement input
prompts and output separators on lines by themselves. As with 3. above, use
standard 4 space indents, as with
:
def f(x):
if x:
print('got it')
return 'so
On Mon, Jul 21, 2014 at 11:22 AM, Rick Johnson
wrote:
> How can i offer improvements if i don't know where to find
> the code?
Look in hg.python.org/cpython and see what you find. You never know,
it might even be there!
ChrisA
--
https://mail.python.org/mailman/listinfo/python-list
On Sunday, July 20, 2014 4:52:36 PM UTC-5, Terry Reedy wrote:
> On 7/19/2014 9:31 PM, Rick Johnson wrote:
> > On Saturday, July 19, 2014 3:45:07 PM UTC-5, Terry Reedy wrote:
> * The third paragraph below explains that Shell's prompt
> is a statement prompt rather than line prompt, so that a
> seco
On Mon, Jul 21, 2014 at 7:52 AM, Terry Reedy wrote:
> On 7/19/2014 9:31 PM, Rick Johnson wrote:
> The problem originates in differences between the console - interactive
> python interaction and Idle Shell - execution server interaction.
> Interactive python prints prompts to and reads lines from
On 7/19/2014 9:31 PM, Rick Johnson wrote:
On Saturday, July 19, 2014 3:45:07 PM UTC-5, Terry Reedy wrote:
Idle's Shell currently uses a primary prompt ('>>> '), no secondary
prompt*, and tabs for indents. This is a compromise between conflicting
goals. It works but perhaps we can do better.
11 matches
Mail list logo
