George Sakkis wrote:
> Unless I missed it, PEP 328 doesn't mention anything about this.
> What's the reason for not allowing "from .relative.module import *' ?
Generally, there's a move away from all "import *" versions these days.
For example, Python 3.0 removes the ability to use "import *" wit
On Jan 14, 2:37 pm, George Sakkis <[EMAIL PROTECTED]> wrote:
> Unless I missed it, PEP 328 doesn't mention anything about this.
> What's the reason for not allowing "from .relative.module import *' ?
I'm just guessing: it could accidentally create infinite recursion.
Or, perhaps something more sub
On Jan 14, 6:01 pm, Ben Finney <[EMAIL PROTECTED]>
wrote:
> George Sakkis <[EMAIL PROTECTED]> writes:
> > Unless I missed it, PEP 328 doesn't mention anything about this.
> > What's the reason for not allowing "from .relative.module import *'
> > ?
>
> It makes the code much harder to follow visua
George Sakkis <[EMAIL PROTECTED]> writes:
> Unless I missed it, PEP 328 doesn't mention anything about this.
> What's the reason for not allowing "from .relative.module import *'
> ?
It makes the code much harder to follow visually and inspect with
static analysis tools, since there's no way to s
Unless I missed it, PEP 328 doesn't mention anything about this.
What's the reason for not allowing "from .relative.module import *' ?
George
--
http://mail.python.org/mailman/listinfo/python-list
