Handling import conflicts when module has the same name as a library module that it needs to import?

Discussion in 'Python' started by plb, Feb 8, 2005.

  1. plb

    plb Guest

    All:

    I am struggling with an import problem...

    In my package, myapp, there is a module called logging. This module,
    naturally, imports the standard library module logging. However, when
    I try 'import myapp.logging', the 'import logging' statement appears to
    be finding the myapp.logging module instead of the one in the standard
    library.

    How can I ensure that my logging module doesn't try to import itself?

    --PLB
     
    plb, Feb 8, 2005
    #1
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. plb
    Replies:
    0
    Views:
    416
  2. Module Name Conflicts

    , Aug 19, 2005, in forum: Python
    Replies:
    15
    Views:
    576
  3. =?Utf-8?B?QmFoZXJp?=

    Handling Concurrency Conflicts

    =?Utf-8?B?QmFoZXJp?=, Nov 10, 2006, in forum: ASP .Net
    Replies:
    0
    Views:
    300
    =?Utf-8?B?QmFoZXJp?=
    Nov 10, 2006
  4. Replies:
    2
    Views:
    280
    Thomas J. Gritzan
    Feb 13, 2007
  5. Gelonida N

    resolving module name conflicts.

    Gelonida N, Nov 11, 2011, in forum: Python
    Replies:
    0
    Views:
    190
    Gelonida N
    Nov 11, 2011
Loading...

Share This Page