Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <ol> <li><code>os.environ</code> is global. You're modifying it, and not modifying it back afterward. So, after doing <code>@patch_python_path</code> on any function, you've now done the equivalent for everything else you define after that—including in other modules and in the top-level script.</li> <li><code>sys.path</code> is also global, and again you're modifying it and not restoring it.</li> <li>You shouldn't ever need to modify both <code>PYTHONPATH</code> and <code>sys.path</code>. (In particular, it's the former that you usually shouldn't need.)</li> <li>You're adding <code>.</code> to <code>PYTHONPATH</code>, but <code>os.getcwd()</code> to <code>sys.path</code>. If you ever <em>do</em> need to modify both, everything will stop working after an <code>os.chdir()</code>, which will effectively change the <code>PYTHONPATH</code> but not the <code>sys.path</code>.</li> <li>Any wrapped function will lose its docstring, name, etc.; use <code>@functools.wraps</code> on your <code>wrap</code> function.</li> </ol> <p>Those are all just issues with your implementation, without getting into whether it's a good idea in the first place. </p> <p>The most common reasons people want something like this are (a) make Python X.Y packages work like Python V.W, and (b) allow importing a package from the source tree to work the same as importing it after install, even from the interpreter shell. The former is probably a bad idea; the latter is handy, but there are other ways to accomplish it. If you have some different higher-level goal, you'll have to tell us what that goal is before anyone can tell you whether this is the best way to accomplish it.</p>
    singulars
    1. This table or related slice is empty.
    1. POAutomatically patching PYTHONPATH (when using Fabric tasks)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USabarnert
    1. USabarnert
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COthanks for your analysis. i have updated my post outlining the objetives i am trying to achieve.
      singulars
      1. PO
      1. USPhilip Nuzhnyy
    2. COAs per your comments. 1 and 2: i don't see modifying environ and sys.path as an issue in the context of a boilerplate used to establish the base for a project (my case). As far I understand the scope for these is a running interpreter instance 3: You might need both patched to insure that both 'import' statements and other python based processes spawned function correctly (e.g. python manage.py runserver --settings=modules.settings) 4 and 5: good calls
      singulars
      1. PO
      1. USPhilip Nuzhnyy
    3. CO@PhilipNuzhnyy: If you want these to be modified globally for the scope of your interpreter instance, why not do it on import of your top module, instead of decorating functions to do it? It's much simpler (and, on the off chance that one of your functions needs to get called millions of times, it'll avoid a performance problem, but that's less likely to matter).
      singulars
      1. PO
      1. USabarnert
 

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