Ronald Oussoren wrote:
Some time ago a warning was introduced for directories on sys.path
that don't contain an __init__.py but have the same name as a package/
module that is being imported.
Is it intentional that this triggers for toplevel imports? These
warnings are triggered in the
On 27-mei-2006, at 8:49, Martin v. Löwis wrote:
Ronald Oussoren wrote:
Some time ago a warning was introduced for directories on sys.path
that don't contain an __init__.py but have the same name as a
package/
module that is being imported.
Is it intentional that this triggers for
Hi,
Some time ago a warning was introduced for directories on sys.path
that don't contain an __init__.py but have the same name as a package/
module that is being imported.
Is it intentional that this triggers for toplevel imports? These
warnings are triggered in the build process for
On 5/26/06, Ronald Oussoren [EMAIL PROTECTED] wrote:
Some time ago a warning was introduced for directories on sys.path
that don't contain an __init__.py but have the same name as a package/
module that is being imported.
Is it intentional that this triggers for toplevel imports?
Yes, since
