Re: Conversion: execfile --> exec

2016-06-13 Thread Michael Selik
On Mon, Jun 13, 2016 at 1:51 PM Rustom Mody wrote: > looks (to me) like an intent to import the package chaco with no locals > and globals -- Just guessing of course > And without creating a module object. I suppose that means it doesn't get cached in sys.modules either. Not sure if that's a fea

Re: Conversion: execfile --> exec

2016-06-13 Thread Rustom Mody
On Monday, June 13, 2016 at 10:48:33 PM UTC+5:30, Michael Selik wrote: > On Mon, Jun 13, 2016, 10:36 AM Rustom Mody wrote: > > > On Monday, June 13, 2016 at 7:41:33 PM UTC+5:30, MRAB wrote: > > > On 2016-06-13 14:24, Long Yang wrote: > > > > The python 2.x command is as following: > > > > ---

Re: Conversion: execfile --> exec

2016-06-13 Thread Michael Selik
On Mon, Jun 13, 2016, 10:36 AM Rustom Mody wrote: > On Monday, June 13, 2016 at 7:41:33 PM UTC+5:30, MRAB wrote: > > On 2016-06-13 14:24, Long Yang wrote: > > > The python 2.x command is as following: > > > --- > > > info = {} > > > execfile(join('chaco', '__init__.py'), i

Re: Conversion: execfile --> exec

2016-06-13 Thread Rustom Mody
On Monday, June 13, 2016 at 7:41:33 PM UTC+5:30, MRAB wrote: > On 2016-06-13 14:24, Long Yang wrote: > > The python 2.x command is as following: > > --- > > info = {} > > execfile(join('chaco', '__init__.py'), info) > > -- > > > > But execfile has

Re: Conversion: execfile --> exec

2016-06-13 Thread MRAB
On 2016-06-13 14:24, Long Yang wrote: The python 2.x command is as following: --- info = {} execfile(join('chaco', '__init__.py'), info) -- But execfile has been removed in python 3.x. So my problem is how to convert the above to a 3.x based co

Conversion: execfile --> exec

2016-06-13 Thread Long Yang
The python 2.x command is as following: --- info = {} execfile(join('chaco', '__init__.py'), info) -- But execfile has been removed in python 3.x. So my problem is how to convert the above to a 3.x based command? thanks very much -- https://mai