Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I use a single <code>_version.py</code> file as the "once cannonical place" to store version information:</p> <ol> <li><p>It provides a <code>__version__</code> attribute.</p></li> <li><p>It provides the standard metadata version. Therefore it will be detected by <code>pkg_resources</code> or other tools that parse the package metadata (EGG-INFO and/or PKG-INFO, PEP 0345).</p></li> <li><p>It doesn't import your package (or anything else) when building your package, which can cause problems in some situations. (See the comments below about what problems this can cause.)</p></li> <li><p>There is only one place that the version number is written down, so there is only one place to change it when the version number changes, and there is less chance of inconsistent versions.</p></li> </ol> <p>Here is how it works: the "one canonical place" to store the version number is a .py file, named "_version.py" which is in your Python package, for example in <code>myniftyapp/_version.py</code>. This file is a Python module, but your setup.py doesn't import it! (That would defeat feature 3.) Instead your setup.py knows that the contents of this file is very simple, something like:</p> <pre><code>__version__ = "3.6.5" </code></pre> <p>And so your setup.py opens the file and parses it, with code like:</p> <pre><code>import re VERSIONFILE="myniftyapp/_version.py" verstrline = open(VERSIONFILE, "rt").read() VSRE = r"^__version__ = ['\"]([^'\"]*)['\"]" mo = re.search(VSRE, verstrline, re.M) if mo: verstr = mo.group(1) else: raise RuntimeError("Unable to find version string in %s." % (VERSIONFILE,)) </code></pre> <p>Then your setup.py passes that string as the value of the "version" argument to <code>setup()</code>, thus satisfying feature 2.</p> <p>To satisfy feature 1, you can have your package (at run-time, not at setup time!) import the _version file from <code>myniftyapp/__init__.py</code> like this:</p> <pre><code>from _version import __version__ </code></pre> <p>Here is <a href="https://github.com/tahoe-lafs/zfec/blob/42dededf9d0ddbb165cdfccbd5acdf6e0600cb4b/setup.py#L91" rel="nofollow noreferrer">an example of this technique</a> that I've been using for years.</p> <p>The code in that example is a bit more complicated, but the simplified example that I wrote into this comment should be a complete implementation.</p> <p>Here is <a href="https://tahoe-lafs.org/trac/zfec/browser/trunk/zfec/zfec/__init__.py?rev=363" rel="nofollow noreferrer">example code of importing the version</a>.</p> <p>If you see anything wrong with this approach, please let me know.</p>
    singulars
    1. This table or related slice is empty.
    1. POStandard way to embed version into python package?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAnto
    1. USZooko
    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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCould you please describe the problems that motivate #3? Glyph said it had something to do with "setuptools likes to pretend that your code isn't anywhere on the system when your setup.py runs", but the details would help convince me and others.
      singulars
      1. PO
      1. USIvan Kozik
    2. CO@IvanKozik: if your `setup.py` is being executed in a freshly created Python process and your current working directory is the directory that contains your project, then it will work. This is the common way that programmers run `setup.py`, so they think it is the only way. But there are other ways! Tools like py2exe run a single Python process and then load and execute the `setup.py` scripts from one project after another (while packing them all together). Suppose that some of the Python code that ran _before_ your `setup.py` script imported a different version of your module.
      singulars
      1. PO
      1. USZooko
    3. CO@IvanKozik I think there can be other problems with importing your package, too. Consider that a tool like `setuptools` or `pip` needs to do two things for packages that declare dependencies: 1. build this package, 2. install (first building, if necessary) its dependencies.
      singulars
      1. PO
      1. USZooko
 

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