On Tuesday 30 June 2009 22:16:41 John Eikenberry wrote:
> What is wrong with simply importing the most common things in
> Kamaelia/__init__.py so they'd be available to import off the top level
> package? Why all the autoload() magic in the original? It was the latter
> that I was mainly disagreei
Michael Sparks wrote:
> I must admit that I'm more than a little surprised at the overall
> consensus here, but it's a very clear one.
>
> As you can imagine I'm in favour of the idea for obvious reasons...
> but I'd be a fool if I asked for advice on what people thought and
> then ignored it.
>
> Essentially I'm wondering how to best implement the equivalent of
> $PATH for KamaeliaComponents.
>
I think this is perfectly satisfied by virtualenv, which generates a
setup.pth file.
This path file can be checked in and used as part of a project.
easy_install modifies the setup.pth file
I must admit that I'm more than a little surprised at the overall
consensus here, but it's a very clear one.
As you can imagine I'm in favour of the idea for obvious reasons...
but I'd be a fool if I asked for advice on what people thought and
then ignored it.
For now, I'll say that this idea...
Gloria W wrote:
> On 06/23/2009 06:27 AM, Sylvain Hellegouarch wrote:
> > I appreciate the fact that the current verbosity means I know where
> > things are coming from and never worry about name clashing.
> >
> > - Sylvain
> >
> I have to admit, and I agree. I did something similar in PHP5 wi
On 06/23/2009 06:27 AM, Sylvain Hellegouarch wrote:
> Matt Hammond a écrit :
>
>>> So some questions arise:
>>> 1. Good idea or not?
>>> 2. Really? Could be viewed as bad mojo& messing about one step too
>>> far.
>>> 3. If OK, should it be static? ie the list of what gets imported
Matt Hammond a écrit :
>> So some questions arise:
>>1. Good idea or not?
>>2. Really? Could be viewed as bad mojo & messing about one step too
>> far.
>>3. If OK, should it be static? ie the list of what gets imported and
>>handles what dealt with by a table lookup in Kamaelia
> So some questions arise:
>1. Good idea or not?
>2. Really? Could be viewed as bad mojo & messing about one step too
> far.
>3. If OK, should it be static? ie the list of what gets imported and
>handles what dealt with by a table lookup in Kamaelia/__init__.py ?
>4. Or sho
