On Thursday, March 3, 2016 at 9:38:11 AM UTC+5:30, Rustom Mody wrote:
> On Thursday, March 3, 2016 at 8:11:20 AM UTC+5:30, Terry Reedy wrote:
> > On 3/2/2016 10:22 AM, Rustom Mody wrote:
> > > On Tuesday, March 1, 2016 at 12:23:02 PM UTC+5:30, Terry Reedy wrote:
> > >> On 2/29/2016 7:42 AM, Rustom
On Thursday, March 3, 2016 at 8:11:20 AM UTC+5:30, Terry Reedy wrote:
> On 3/2/2016 10:22 AM, Rustom Mody wrote:
> > On Tuesday, March 1, 2016 at 12:23:02 PM UTC+5:30, Terry Reedy wrote:
> >> On 2/29/2016 7:42 AM, Rustom Mody wrote:
> >>
> >>> Is import needed at all when trying out in Idle?
> >>
On 3/2/2016 10:22 AM, Rustom Mody wrote:
On Tuesday, March 1, 2016 at 12:23:02 PM UTC+5:30, Terry Reedy wrote:
On 2/29/2016 7:42 AM, Rustom Mody wrote:
Is import needed at all when trying out in Idle?
...
So it does appear that
1. import not necessary with(in) idle
2. However import and f5
On Tuesday, March 1, 2016 at 12:23:02 PM UTC+5:30, Terry Reedy wrote:
> On 2/29/2016 7:42 AM, Rustom Mody wrote:
>
> > Is import needed at all when trying out in Idle?
> ...
> > So it does appear that
> > 1. import not necessary with(in) idle
> > 2. However import and f5 (ie is run as main) are
On 2/29/2016 7:42 AM, Rustom Mody wrote:
Is import needed at all when trying out in Idle?
...
So it does appear that
1. import not necessary with(in) idle
2. However import and f5 (ie is run as main) are different
May some idle experts elaborate on this? Whats the idle idiom of import-ing?
On Monday, February 29, 2016 at 12:10:28 PM UTC+5:30, alien2utoo wrote:
> Hello list,
>
> We can not import a module twice in a session of Python (subsequent attempts
> to import same module don't result in any error though, but it is
> not-effective).
>
> However after making change to
