On Wed, Feb 2, 2011 at 4:10 PM, Hartmut Goebel
<h.goe...@goebel-consult.de>wrote:
> Am 02.02.2011 15:00, schrieb nap:
> > Why not, but it will complexify the import pass (not a huge problem)
> > and sys.path management (more buggy part) a lot if there are too much
> > of them. It should be easier to read too. What cut do you propose
> exactly?
> Why does this complexify the sys.path handling? I'm not talking about
> sub-direcories, but about sub-packages. This only difference will be the
> import statements.
>
> If we *may* introduce namespace packages some when, there may be some
> path frickling. But we can think about this some when later.
>
> It's for some daemon like Broker that need to load class of some objects in
the modules, and having the good sys.path can help to find them if it's not
already imported. But if all modules work, there is no worry :)
> I can not suggest a sensefull split, since I did not understand the code
> good enough ;-)
>
Ok no problem :)
>
[...]
Jean
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
