Ian於 2013年1月12日星期六UTC+8下午3時36分43秒寫道：
> On Fri, Jan 11, 2013 at 10:28 PM, Rick Johnson
>
> wrote:
>
> > On Friday, January 11, 2013 12:30:27 AM UTC-6, Chris Angelico wrote:
>
> >> Why is it better to import from the current directory first?
>
> >
>
> > Opps. I was not explicit enough with my e
On Jan 12, 3:28 pm, Rick Johnson wrote:
> I am working on it. Stay tuned. Rick is going to rock your little programming
> world /very/ soon.
I am so confidant that this will never happen that if you _do_ ever
produce _anything_ that even remotely resembles your claims, I pledge
to provide you wi
On 12 Jan, 14:50, Rick Johnson wrote:
> Of course many people will piss and moan about the extra typing.
You just ignored the fact that your original claim was incorrect and
kept going on with your rant anyway.
> Since more time is spent /maintaining/ code bases than /writing/ them
In your case
On Fri, Jan 11, 2013 at 10:28 PM, Rick Johnson
wrote:
> On Friday, January 11, 2013 12:30:27 AM UTC-6, Chris Angelico wrote:
>> Why is it better to import from the current directory first?
>
> Opps. I was not explicit enough with my explanation :). I meant, "look in the
> current directory FIRST
On Sat, Jan 12, 2013 at 4:28 PM, Rick Johnson
wrote:
> On Friday, January 11, 2013 12:30:27 AM UTC-6, Chris Angelico wrote:
>> Welcome back to the list, Rick. Got any demonstrable code
>> for Python 4000 yet?
>
> I am working on it. Stay tuned. Rick is going to rock your little programming
> worl
On Friday, January 11, 2013 12:30:27 AM UTC-6, Chris Angelico wrote:
> Why is it better to import from the current directory first?
Opps. I was not explicit enough with my explanation :). I meant, "look in the
current directory FIRST when in a package". Since many times (most all times)
packages
On Friday, January 11, 2013 7:35:37 AM UTC-6, Terry Reedy wrote:
> On 1/11/2013 1:13 AM, Rick Johnson wrote:
> > The fact that Python looks in the stdlib _first_ is not a good idea.
>
> And the fact is that it does not do so. The order depends on sys.path,
> and '' is the first entry.
>
> > It w
On 01/10/2013 11:13 PM, Rick Johnson wrote:
>
> Python's import resolution order is terrible.[1]
>
> The fact that Python looks in the stdlib _first_ is not a good idea.
Whether or not the default behavior is desirable or not, sys.path is set
by default to look in the current directory first on
On 1/11/2013 1:13 AM, Rick Johnson wrote:
Python's import resolution order is terrible.[1]
The fact that Python looks in the stdlib _first_ is not a good idea.
And the fact is that it does not do so. The order depends on sys.path,
and '' is the first entry.
It would seem more intuitive fo
On Fri, Jan 11, 2013 at 5:13 PM, Rick Johnson
wrote:
> The fact that Python looks in the stdlib _first_ is not a good idea. It would
> seem more intuitive for a custom "math" module (living in the current
> directory) to /override/ the stlib "math" module. The proper order is as
> follows:
>
>
Python's import resolution order is terrible.[1]
The fact that Python looks in the stdlib _first_ is not a good idea. It would
seem more intuitive for a custom "math" module (living in the current
directory) to /override/ the stlib "math" module. The proper order is as
follows:
1. Current pac
11 matches
Mail list logo
