Re: unexpected from/import statement behaviour

2008-08-27 Thread nisp
On Aug 27, 3:35 pm, Peter Otten <[EMAIL PROTECTED]> wrote: > nisp wrote: > > Thanks first of all ! I read the interesting Diez's link but something > > still remains to me unclear, on the other hand it's clear the my > > problem is concentrated there and on symbols. > > Read it again. If you have t

Re: unexpected from/import statement behaviour

2008-08-27 Thread alex23
On Aug 27, 5:42 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote: > alex23 schrieb: > > > > > nisp <[EMAIL PROTECTED]> wrote: > >> I've always been convinced of the equivalence of the two ways of using > >> the import statement but it's clear I'm wrong :-( > > > Python 2.5.2 (r252:60911, Jul 31 200

Re: unexpected from/import statement behaviour

2008-08-27 Thread Peter Otten
nisp wrote: > Thanks first of all ! I read the interesting Diez's link but something > still remains to me unclear, on the other hand it's clear the my > problem is concentrated there and on symbols. Read it again. If you have two modules module1.py from sys import stderr module2.py from module

Re: unexpected from/import statement behaviour

2008-08-27 Thread nisp
On Aug 27, 2:43 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote: > nisp wrote: > > On Aug 27, 9:56 am, Peter Otten <[EMAIL PROTECTED]> wrote: > >> nisp wrote: > >> > Hi all ! > > >> > I'm trying to capture stderr of an external module I use in my python > >> > program. I'm doing this > >> > by set

Re: unexpected from/import statement behaviour

2008-08-27 Thread Diez B. Roggisch
nisp wrote: > On Aug 27, 9:56 am, Peter Otten <[EMAIL PROTECTED]> wrote: >> nisp wrote: >> > Hi all ! >> >> > I'm trying to capture stderr of an external module I use in my python >> > program. I'm doing this >> > by setting up a class in my module overwriting the stderr file object >> > method wr

Re: unexpected from/import statement behaviour

2008-08-27 Thread nisp
On Aug 27, 9:56 am, Peter Otten <[EMAIL PROTECTED]> wrote: > nisp wrote: > > Hi all ! > > > I'm trying to capture stderr of an external module I use in my python > > program. I'm doing this > > by setting up a class in my module overwriting the stderr file object > > method write. > > The external

Re: unexpected from/import statement behaviour

2008-08-27 Thread Peter Otten
nisp wrote: > Hi all ! > > I'm trying to capture stderr of an external module I use in my python > program. I'm doing this > by setting up a class in my module overwriting the stderr file object > method write. > The external module outputs to stderr this way: > > from sys import std err > > ..

Re: unexpected from/import statement behaviour

2008-08-27 Thread Diez B. Roggisch
alex23 schrieb: nisp <[EMAIL PROTECTED]> wrote: I've always been convinced of the equivalence of the two ways of using the import statement but it's clear I'm wrong :-( Python 2.5.2 (r252:60911, Jul 31 2008, 17:28:52) [GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2 Type "help", "copyright", "cre

Re: unexpected from/import statement behaviour

2008-08-27 Thread alex23
nisp <[EMAIL PROTECTED]> wrote: > I've always been convinced of the equivalence of the two ways of using > the import statement but it's clear I'm wrong :-( Python 2.5.2 (r252:60911, Jul 31 2008, 17:28:52) [GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] on linux2 Type "help", "copyright", "credits" or "licens

Re: unexpected from/import statement behaviour

2008-08-27 Thread Diez B. Roggisch
nisp schrieb: Hi all ! I'm trying to capture stderr of an external module I use in my python program. I'm doing this by setting up a class in my module overwriting the stderr file object method write. The external module outputs to stderr this way: from sys import std err print >