GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • [Python-Dev] Death to string functions!
  • [Python-Dev] Death to string functions!
  • [ date ]
  • [ thread ]
  • [ subject ]
  • [ author ]

This view

  • Original page
  • New address

GeezerVison is showing mail.python.org — [Python-Dev] Death to string functions!

[Python-Dev] Death to string functions!

Barry A. Warsaw [email protected]
Tue, 19 Dec 2000 12:20:07 -0500

  • Previous message: [Python-Dev] Death to string functions!
  • Next message: [Python-Dev] Death to string functions!
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

>>>>> "JvR" == Just van Rossum <[email protected]> writes:

    JvR> Recommending replacing all of these (not to mention all the
    JvR> code "out there") with named constants seems plain silly.

Until there's a tool to do the migration, I don't (personally)
recommend wholesale migration.  For new code I write though, I usually
do it the way I described (which is intuitive to me, but then so is
moving your fingers at a blinding speed up and down 5 long strips of
metal to cause low bowel-tickling rumbly noises).

    JvR> So, making join() a builtin makes a whole lot of sense. Not
    JvR> doing this because people sometimes use a local reference to
    JvR> os.path.join seems awfully backward.

I agree.  Have we agreed on the semantics and signature of builtin
join() though?  Is it just string.join() stuck in builtins?

-Barry



  • Previous message: [Python-Dev] Death to string functions!
  • Next message: [Python-Dev] Death to string functions!
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.