Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It depends. If none of the packages that are importing <code>somepackage</code> use the <code>setuptools</code> API, then it works as described above. If any packages in your virtualenv use <code>setuptools</code> (or <code>Distribute</code>) to specify specific version requirements for <code>somepackage</code>, <code>setuptools</code> will search for a version of <code>somepackage</code> that meets the requirements. If it can't find a suitable installed version at install time, it will search externally and attempt to install it. If it can't find one at runtime, the program fails with an exception.</p> <pre><code>from setuptools import setup setup( name = "HelloWorld", version = "0.1", scripts = ['say_hello.py'], install_requires = ['somepackage == 1.0.0'], ) </code></pre> <p>For example, if <code>somepackage 1.0.0</code> was already installed in the system site-packages, everything is fine. If you then update the system site-packages to <code>somepackage 2.0.0</code> with <code>pip</code>, which uninstalls the old version, the script will fail at runtime with:</p> <pre><code>pkg_resources.DistributionNotFound: somepackage==1.0.0 </code></pre> <p>If you installed both versions of <code>somepackage</code> with <code>easy_install</code> instead of <code>pip</code>, things would normally be different. By default, <code>easy_install</code> does not uninstall packages and it supports multiple versions of packages (multi-version eggs). So both versions of <code>somepackage</code> would be available in the system site-packages and the script would not fail.</p> <p><code>setuptools</code> (and the <code>Distribute</code> clone of it) has to jump through many hoops to make the multiple version support work reasonably. Many developers frown on all that extra complexity and argue that it is easier and more transparent to support multiple versions of packages with separate <code>virutalenv</code>'s and, for that, the simpler model of <code>pip</code> is more appropriate. (In fairness to <code>setuptools</code>, <code>virtualenv</code> came along later.)</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat happens if a site package is updated beyond the version I specified in a virtualenv with pip?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USNed Deily
    1. USNed Deily
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhat happens if a site package is updated beyond the version I specified in a virtualenv with pip?
      singulars
      1. PTQuestion
    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. VTAcceptedByOriginator
    1. This table or related slice is empty.
 

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