yade-dev team mailing list archive

[Anton Gladky <gladky.anton@xxxxxxxxx>]

> 1/ It seems to me that a series of "import" are found at the beginning of
> many scripts (e.g. pack). Couldn't we load them by default, so that we could
> get rid of the imports in scripts?

I support that idea. We just need to decide, what modules are needed
by default on.

> 2/ functions, like sphere(), SpherePack(), aabbWalls(), can't be used just
> like this, we need to always type utils.sphere. I don't see advantage, and
> it's not always obvious which module contains a given function. Would it be
> a problem to make such functions reachable from the global namespace (just
> adding "from utils import *" in yade.py)?

We should be careful with that. A lot of user's scripts will not work
after such modification.
I dont know...

Anton




On Fri, May 6, 2011 at 4:45 PM, Bruno Chareyre
<bruno.chareyre@xxxxxxxxxxx> wrote:
> Hi,
>
> 1/ It seems to me that a series of "import" are found at the beginning of
> many scripts (e.g. pack). Couldn't we load them by default, so that we could
> get rid of the imports in scripts?
> 2/ functions, like sphere(), SpherePack(), aabbWalls(), can't be used just
> like this, we need to always type utils.sphere. I don't see advantage, and
> it's not always obvious which module contains a given function. Would it be
> a problem to make such functions reachable from the global namespace (just
> adding "from utils import *" in yade.py)?
>
> If there are no objections, I'll make this change.
>
> Bruno
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~yade-dev
> Post to     : yade-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~yade-dev
> More help   : https://help.launchpad.net/ListHelp
>
>