Databases
StackOverflow2013
Postsdbo
POBest way to import python module at the root of a package hierarchy from another module in the same package
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBest way to import python module at the root of a package hierarchy from another module in the same package
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USgae123
    1. USgae123
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBest way to import python module at the root of a package hierarchy from another module in the same package
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POBest way to import python module at the root of a package hierarchy from another module in the same package
      1. USninjagecko
      1. VTFavorite
    3. VO
      singulars
      1. POBest way to import python module at the root of a package hierarchy from another module in the same package
      1. This table or related slice is empty.
      1. VTUpMod
    1. COShort of writing a very introspective hack like `import x` which changes `sys.path`, or overriding the semantics of `builtin.__import__` or creating import hooks as suggested in http://docs.python.org/library/functions.html#__import__ , you are looking for a very reasonable feature that does not exist in most languages I know of as of 2012. In my humble opinion, python is better suited than some other languages, but still particularly ill-suited for non-verbose imports. The "pythonic" view that such verbosity is explicit, and therefore good, will probably not make the feature forthcoming.
      singulars
      1. POBest way to import python module at the root of a package hierarchy from another module in the same package
      1. USninjagecko
    2. COI knew I would get what is the big deal about this, you are doing major refactoring anyways. Writing code is major refactoring all the time. You work with several packages, you put something in one place, then you realize it is major functionality that could be used elsewhere, so you refactor it in another package. There are som many things you need to worry when you move things around I am trying to minimize the overhead. By the way, I have an m0 at the top of every package, so when a module moves to another package and still refers to the m0 at the top of the first package, is error prone.
      singulars
      1. POBest way to import python module at the root of a package hierarchy from another module in the same package
      1. USgae123
    3. COYes, I agree. Yet I am not sure why you are saying what you are saying. I was not asking "what is the big deal about this".
      singulars
      1. POBest way to import python module at the root of a package hierarchy from another module in the same package
      1. USninjagecko
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload