Databases
StackOverflow2013
Postsdbo
POAutomatically patching PYTHONPATH (when using Fabric tasks)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAutomatically patching PYTHONPATH (when using Fabric tasks)
    primarykey
    data
    text
    <p>I wrap function calls within my initialization module with a decorator that patches PYTHONPATH to add current directory to it so I can use relative imports within my modules without worrying about adding the package to PYTHONPATH explicitly (edited based on @abarnert's comments)</p> <pre><code>def patch_python_path(f): @wraps(f) def wrap(*args, **kwargs): ROOT = os.pathsep.join([os.path.abspath(os.path.dirname(__file__))]) if not os.environ.has_key("PYTHONPATH"): os.environ["PYTHONPATH"] = "" if not (ROOT in os.environ["PYTHONPATH"].split(":")): os.environ["PYTHONPATH"] = "%s:%s" % (os.environ["PYTHONPATH"], ROOT) if not ROOT in sys.path: sys.path.append(ROOT) return f(*args, **kwargs) return wrap </code></pre> <p>Here's how I use it:</p> <pre><code>@patch_python_path def initialize(): #at this point any code being run has access to local modules through relative imports pass </code></pre> <p>Are there any major issues with this approach that I am not aware of?</p> <hr> <p>My objectives with this are the following:</p> <ul> <li>i want to have a self contained bootstrap that a user can immediately use without any additional env manipulations</li> <li>i also assume that a user can change the name of the bootstrap package so it's imperative that all the imports remain relative </li> </ul> <p>[EDIT] I'm actually realizing that the problem I am facing has more to do with the way Fabric runs tasks as opposed to pure Python module importing. If I attempt to run a task from a python shell (as opposed to fab task1) all the imports are resolved correctly without any patching required. Running a task through fab causes import errors </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPhilip Nuzhnyy
    1. USPhilip Nuzhnyy
    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. POAutomatically patching PYTHONPATH (when using Fabric tasks)
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAutomatically patching PYTHONPATH (when using Fabric tasks)
      1. This table or related slice is empty.
      1. VTUpMod
    1. COTo be clear: You want the user to be able to drop the package into the current directory, without installing it, and use it, right?
      singulars
      1. POAutomatically patching PYTHONPATH (when using Fabric tasks)
      1. USabarnert
    2. COyes. more specifically what I have is a Django based web application that serves as a bootstrap boilerplate. user clones the boilerplate, makes adjustments and it just works
      singulars
      1. POAutomatically patching PYTHONPATH (when using Fabric tasks)
      1. USPhilip Nuzhnyy
 

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