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

  • [ date ]
  • [ thread ]
  • [ subject ]
  • [ author ]

This view

  • Original page
  • New address

GeezerVison is showing mail.python.org — [Python-Dev] Criticism of execfile() removal in Python3

[Python-Dev] Criticism of execfile() removal in Python3

Paul Moore p.f.moore at gmail.com
Tue Jun 10 10:41:16 CEST 2014

  • Previous message: [Python-Dev] Criticism of execfile() removal in Python3
  • Next message: [Python-Dev] Criticism of execfile() removal in Python3
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On 10 June 2014 08:36, Nick Coghlan <ncoghlan at gmail.com> wrote:
> The standard implementation of run_path reads the whole file into
> memory, but MicroPython would be free to optimise that and do
> statement by statement execution instead (while that will pose some
> challenges in terms of handling encoding cookies, future imports, etc
> correctly, it's certainly feasible).

... and if they did optimise that way, I would imagine that the patch
would be a useful contribution back to the core Python stdlib, rather
than remaining a MicroPython-specific optimisation.

Paul

  • Previous message: [Python-Dev] Criticism of execfile() removal in Python3
  • Next message: [Python-Dev] Criticism of execfile() removal in Python3
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Python-Dev mailing list
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.