On 12/19/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> I've written a quick version of PEP 3106, which expresses my ideas
> about how the dict methods to access keys, values and items should be
> redone.
Thanks for all the comments. The new version is in svn:
http://svn.python.org/view/peps/tr
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 12/21/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Actually you *should* post this to python-dev. Let's be aggressive.
> All of those look like we should've stopped supporting them years
> ago... :-)
>
OK, moved it over along with the two comments that came in on this thread.
-Brett
> On
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
Neal Norwitz wrote:
> What do we want to do with the current versionadded/versionchanged
> markups in the doc for 3k? Should we remove all references to 1.x
> changes? all 2.x changes? Keep them? all of them?
the right answer is of course to move the documentation over to an
environment that
12 matches
Mail list logo
