module global variables

pistacchio pistacchio at gmail.com
Tue May 13 09:36:48 EDT 2008


On 12 Mag, 11:11, pistacchio <pistacc... at gmail.com> wrote:
> On 12 Mag, 10:47, Marco Mariani <ma... at sferacarta.com> wrote:
>
> >pistacchiowrote:
> > > On 12 Mag, 10:01, alex23 <wuwe... at gmail.com> wrote:
> > >> On May 12, 5:17 pm,pistacchio<pistacc... at gmail.com> wrote:
>
> > >>> hi to all!
> > >>> can i load a module passing to it, automatically and as default, all
> > >>> the caller's global variables to act as module's global variables?
>
> > Are you positively sure you need this?
>
> > Modifying imported modules is already quite fragile, but this.. it's
> > basically a reversed(import *)
>
> > It's quite messy. Where quite equals to "very"
>
> well, i'm writing a module called pycatrix. within the module i have
> compile / exec statements in a functions that work on global
> variables. ( exec compiledTemplate in globals() ).
>
> now, i don't want to be forced (or force the end user) to import to
> call the module's function with a compulsory "globals()" as argument.

up



More information about the Python-list mailing list