Nick Coghlan ncoghlan at gmail.com
Tue Sep 1 12:58:30 CEST 2009

• Previous message: [Python-Dev] how important is setting co_filename for a module being imported to what __file__ is set to?
• Next message: [Python-Dev] [OT] implicit return values
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Brett Cannon wrote:
> On Mon, Aug 31, 2009 at 06:36, Nick Coghlan<ncoghlan at gmail.com> wrote:
>> That said, while actually ditching the C code might cause an argument,
>> expanding runpy with Python equivalents of the C level functionality
>> (i.e. run script by name, run directory/zipfile by name, '-c' switch,
>> and other odds and ends that I'm probably forgetting right now, with all
>> associated modifications to sys.argv and the __main__ module attributes)
>> should be far less controversial.
> 
> It also has the perk of letting alternative VMs not have to implement
> all of that stuff themselves, potentially helping to unify even the
> command-line interfaces for all the VMs.

I created a tracker item for the idea so I don't forget about it:

http://bugs.python.org/issue6816

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
---------------------------------------------------------------

---

• Previous message: [Python-Dev] how important is setting co_filename for a module being imported to what __file__ is set to?
• Next message: [Python-Dev] [OT] implicit return values
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list