We implemented this at today's sprint. Andre wrote the transformations
for the 2to3 tools, I copied the raw_input() implementation from the
trunk back into the p3yk branch. Thanks Andre for your efforts in
writing the PEP, pushing for its implementation, and writing the
transformations!
--Guido
O
On 2/20/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Why do you want this *before* PyCon? It would be much easier to do
> this as part of the Py3k sprint.
>
My main interest was to have, prior to Pycon, the PEP recorded as
such; it had been close to 2 months since the last post on this issue
On 2/20/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Why do you want this *before* PyCon? It would be much easier to do
> this as part of the Py3k sprint.
>
My main interest was to have, prior to Pycon, the PEP recorded as
such; it had been close to 2 months since the last post on this issue
Consider the PEP accepted.
Regarding the conversion, please do use the sandbox/2to3 framework.
Write me if you have trouble understanding the many examples already
in fixes/.
On 2/20/07, Andre Roberge <[EMAIL PROTECTED]> wrote:
> On 2/20/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > Why do
Why do you want this *before* PyCon? It would be much easier to do
this as part of the Py3k sprint.
On 2/20/07, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Andre Roberge wrote:
> > Any possibility that (some of) the following can be done before Pycon?
> > Respectfully yours,
> > André Roberge
>
> I'
Andre Roberge wrote:
> Any possibility that (some of) the following can be done before Pycon?
> Respectfully yours,
> André Roberge
I've added the PEP as 3111. I made a few small modifications (and
committed it directly as Accepted) based on Guido's comments in this thread.
The actual change sti
Any possibility that (some of) the following can be done before Pycon?
Respectfully yours,
André Roberge
On 12/23/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
[http://mail.python.org/pipermail/python-3000/2006-December/005257.html]
> BTW, can someone clean up and check in the proto-PEP and star
On 12/23/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 12/23/06, Calvin Spealman <[EMAIL PROTECTED]> wrote:
> > On 12/23/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > > On 12/23/06, Calvin Spealman <[EMAIL PROTECTED]> wrote:
> > > > I was reading the thread and wanted to make a comment
On 12/23/06, Calvin Spealman <[EMAIL PROTECTED]> wrote:
> On 12/23/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > On 12/23/06, Calvin Spealman <[EMAIL PROTECTED]> wrote:
> > > I was reading the thread and wanted to make a comment about the "input
> > > from a GUI". It should be noted that what
On 12/23/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 12/23/06, Calvin Spealman <[EMAIL PROTECTED]> wrote:
> > I was reading the thread and wanted to make a comment about the "input
> > from a GUI". It should be noted that whatever the names of these
> > functions, or their allowed paramete
On 12/23/06, Calvin Spealman <[EMAIL PROTECTED]> wrote:
> I was reading the thread and wanted to make a comment about the "input
> from a GUI". It should be noted that whatever the names of these
> functions, or their allowed parameters, etc., the idea of them being
> more than console IO should be
On 12/23/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 12/23/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> > Guido van Rossum wrote:
> >
> > > But they typically aren't used to entering EOF either; EOF is not
> > > exactly a typical input in an interactive program, and having to enter
> > >
BTW, can someone clean up and check in the proto-PEP and start working
on an implementation or patch? Should be really simple. I'd like to
see a patch for the refactoring tool (sandbox/2to3) as well.
--Guido
--
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
On 12/23/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
>
> > But they typically aren't used to entering EOF either; EOF is not
> > exactly a typical input in an interactive program, and having to enter
> > it typically means you're talking to a Unix utility that's not reall
Guido van Rossum wrote:
> But they typically aren't used to entering EOF either; EOF is not
> exactly a typical input in an interactive program, and having to enter
> it typically means you're talking to a Unix utility that's not really
> designed for interactive use.
the progression I had in min
On 12/22/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
>
> > I like the exact proposal made here better than any of the
> > alternatives mentioned so far.
> >
> > - Against naming it readline(): the "real" readline doesn't strip the
> > \n and returns an empty string for EO
Guido van Rossum wrote:
> I like the exact proposal made here better than any of the
> alternatives mentioned so far.
>
> - Against naming it readline(): the "real" readline doesn't strip the
> \n and returns an empty string for EOF instead of raising EOFError; I
> believe the latter is more help
I like the exact proposal made here better than any of the
alternatives mentioned so far.
- Against naming it readline(): the "real" readline doesn't strip the
\n and returns an empty string for EOF instead of raising EOFError; I
believe the latter is more helpful for true beginners' code.
- Agai
At 12:20 PM 12/22/2006 -0800, Brett Cannon wrote:
>+1 from me as well, although as Ron suggested, you probably want to
>strip off the newline if we are targetting this to new programmers.
In which case, why not go all the way and use say() and ask()? E.g.:
say('Hello,', ask("What's your nam
On 12/22/06, Steven Bethard <[EMAIL PROTECTED]> wrote:
> On 12/22/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> > Andre Roberge wrote:
> >
> > > The various possibilities mentioned in various forums include:
> > >
> > > ask()
> > > ask_user()
> > > get_string()
> > > input() # rejected by BDFL
>
On Dec 22, 2006, at 5:45 AM, Andre Roberge wrote:
> raw_input() provides a simple mean to ask a question and obtain a
> response
> from a user. The proposed plans for Python 3.0 would require the
> replacement
> of the single statement
>
> name = raw_input("What is your name?")
>
> by the mor
On 12/22/06, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> Andre Roberge wrote:
>
> > The various possibilities mentioned in various forums include:
> >
> > ask()
> > ask_user()
> > get_string()
> > input() # rejected by BDFL
> > prompt()
> > read()
> > user_input()
> > get_response()
>
> why not ca
Andre Roberge wrote:
> The various possibilities mentioned in various forums include:
>
> ask()
> ask_user()
> get_string()
> input() # rejected by BDFL
> prompt()
> read()
> user_input()
> get_response()
why not call it "readline", and define it as
import sys
def readline():
A few months ago, there was an active discussion on edu-sig regarding
the proposed fate of raw_input(). The text below is an attempt at
summarizing the discussion in the form of a tentative PEP.
It is respectfully submitted for your consideration.
If it is to be considered, in some form, as an o
24 matches
Mail list logo
