Eric Firing wrote:
> Jeff Whitaker wrote:
>> Ted Drain wrote:
>>> Could someone point me at a discussion/article that explains the
>>> need for namespace packages? I'm sure there is some good reason for
>>> it but on the surface it seems very confusing. I've always thought
>>> that the purpose
Jeff Whitaker wrote:
> Ted Drain wrote:
>> Could someone point me at a discussion/article that explains the need
>> for namespace packages? I'm sure there is some good reason for it but
>> on the surface it seems very confusing. I've always thought that the
>> purpose of the __init__ file is t
Ted Drain wrote:
> Could someone point me at a discussion/article that explains the need
> for namespace packages? I'm sure there is some good reason for it but
> on the surface it seems very confusing. I've always thought that the
> purpose of the __init__ file is to define the public interfa
Could someone point me at a discussion/article that explains the need
for namespace packages? I'm sure there is some good reason for it
but on the surface it seems very confusing. I've always thought that
the purpose of the __init__ file is to define the public interface
for a package. So wh
Andrew Straw wrote:
> Great -- hopefully that saved you some API re-arrangement pain. No
> problem on shuffling mpl_sizer around -- please go ahead do it if you
> have time.
>
> -Andrew
>
> Jeff Whitaker wrote:
>> Andrew: Thanks, you've convinced me. Is it OK with you if I go
>> ahead and make
Great -- hopefully that saved you some API re-arrangement pain. No
problem on shuffling mpl_sizer around -- please go ahead do it if you
have time.
-Andrew
Jeff Whitaker wrote:
> Andrew: Thanks, you've convinced me. Is it OK with you if I go ahead
> and make those changes to mplsizer at the
Andrew Straw wrote:
> Jeff Whitaker wrote:
>
>> Darren Dale wrote:
>>
>>> On Wednesday 09 January 2008 7:01:14 pm Jeff Whitaker wrote:
>>>
>>>
Andrew Straw wrote:
> As the author of the only other known MPL toolkit (at least in the MPL
> tree), I
Jeff Whitaker wrote:
> Darren Dale wrote:
>> On Wednesday 09 January 2008 7:01:14 pm Jeff Whitaker wrote:
>>
>>> Andrew Straw wrote:
>>>
As the author of the only other known MPL toolkit (at least in the MPL
tree), I'm happy with the idea of using a namespace package for
mpl_to
Darren Dale wrote:
> On Wednesday 09 January 2008 7:01:14 pm Jeff Whitaker wrote:
>
>> Andrew Straw wrote:
>>
>>> As the author of the only other known MPL toolkit (at least in the MPL
>>> tree), I'm happy with the idea of using a namespace package for
>>> mpl_toolkits. I understand your pr
On Wednesday 09 January 2008 7:01:14 pm Jeff Whitaker wrote:
> Andrew Straw wrote:
> > As the author of the only other known MPL toolkit (at least in the MPL
> > tree), I'm happy with the idea of using a namespace package for
> > mpl_toolkits. I understand your proposal to mean that each toolkit wo
Andrew Straw wrote:
> As the author of the only other known MPL toolkit (at least in the MPL
> tree), I'm happy with the idea of using a namespace package for
> mpl_toolkits. I understand your proposal to mean that each toolkit would
> have a directory structure:
>
> setup.py
> lib/
> mpl_tool
Ted Drain wrote:
> Does this proposal change the way people access this
> functionality? We have a lot of scripts (and a lot of users with
> scripts) that use basemap and it tends to be extremely annoying to
> people when their scripts suddenly break.
>
> Ted
>
Ted: Unfortunately it would
Does this proposal change the way people access this
functionality? We have a lot of scripts (and a lot of users with
scripts) that use basemap and it tends to be extremely annoying to
people when their scripts suddenly break.
Ted
At 03:34 PM 1/9/2008, Andrew Straw wrote:
>As the author of th
As the author of the only other known MPL toolkit (at least in the MPL
tree), I'm happy with the idea of using a namespace package for
mpl_toolkits. I understand your proposal to mean that each toolkit would
have a directory structure:
setup.py
lib/
mpl_toolkits/
__i
14 matches
Mail list logo
