Change by Stargirl Flowers :
--
resolution: -> rejected
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Stargirl Flowers added the comment:
@steven.daprano I appreciate your perspective but you laid out a lot of strong
opinions as if they're incontrovertible truths.
The motivation here isn't laziness- I created this bug because I saw actual
people across various skill levels that are bugged
Stargirl Flowers added the comment:
Fair point about semantic behavior and complexity, but hopefully we can come up
with a solution that's easier for users.
I do like the PR suggested.
--
___
Python tracker
<https://bugs.python.org/issue44
Stargirl Flowers added the comment:
I do want to be cautious of saying that we can't do it because of the way the
REPL is currently implemented- which appears to be an implementation driven by
convenience more than necessity.
I also find pushing against special-case behavior in the REPL
Stargirl Flowers added the comment:
Also, if a PEP is recommended, I will be happy to author it.
--
___
Python tracker
<https://bugs.python.org/issue44
Stargirl Flowers added the comment:
I don't think we should completely write off the possibility of doing this just
because the *current* implementation is counter-intuitive. As I expressed in
the original post, the explanation of this behavior is rather unsatisfying to
newcomers.
Also
New submission from Stargirl Flowers :
Presently, when using REPL if a user types simply "exit", they are greeted with
a message instructing them to do it "correctly":
>>> exit
Use exit() or Ctrl-Z plus Return to exit
It comes across as a little surprising that
New submission from Stargirl Flowers :
Presently the documentation for os.path
(https://docs.python.org/3.8/library/os.path.html) doesn't contain any concrete
examples of the input and outputs of the various path manipulation functions.
Contrast this to the Node.js documentation for similar
