On Oct 26 2016, Paul Moore <p.f.moore-re5jqeeqqe8avxtiumw...@public.gmane.org>
wrote:
> On 26 October 2016 at 18:25, Nick Coghlan
> <ncoghlan-re5jqeeqqe8avxtiumw...@public.gmane.org> wrote:
>> The built-in REPL serves two quite divergent use cases, and I think
>> we're well past the point where we can't readily support both use
>> cases with a single implementation:
>>
>> - a minimalist interactive environment, that is *always* present, even
>> if parts of the interpreter (most notably the import system) aren't
>> working or have been deliberately disabled
>> - a day-to-day working environment for Python developers
>>
>> The prevalence of the latter use case then leads to it also being used
>> as a tool for introducing new developers to Python.
>
> Thinking a little further about this, I think the reason I don't use
> IPython more, is because my muscle memory types "python" (or more
> often, "py") when I want an interactive prompt. And I do that for the
> reason you mention - it's always there.
>
> So I think that it would be really useful to be able to plug in a new
> REPL, when it's available. This has a number of benefits:
>
> 1. We don't need to worry about incorporating any complex REPL code
> into Python. The default REPL can remain simple.
> 2. Users can choose their preferred REPL, core Python doesn't have to
> get involved in UI decisions.
Uh, these are not advantages of plugging in a new REPL when
available. This describes the current situation.
At least in your email above you seem to be arguing that Python should
change to better accomodate your muscle memory. I don't want to
diminuish your importance, but doesn't that maybe go a little too far?
:-).
Best,
-Niko
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/
