Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This error occurs when installing <code>pytz</code> using pip v1.4 or newer, due to this change in behaviour:</p> <blockquote> <h2><a href="http://pip.readthedocs.org/en/1.4.1/logic.html#pre-release-versions" rel="noreferrer">Pre-release Versions</a></h2> <p>Starting with v1.4, pip will only install stable versions as specified by <a href="http://www.python.org/dev/peps/pep-0426" rel="noreferrer">PEP426</a> by default. If a version cannot be parsed as a compliant <a href="http://www.python.org/dev/peps/pep-0426" rel="noreferrer">PEP426</a> version then it is assumed to be a pre-release.</p> <p>If a Requirement specifier includes a pre-release or development version (e.g. <code>&gt;=0.0.dev0</code>) then pip will allow pre-release and development versions for that requirement. This does not include the <code>!=</code> flag.</p> <p>The <code>pip install</code> command also supports a <code>--pre</code> flag that will enable installing pre-releases and development releases.</p> </blockquote> <p>The version identifiers for the <code>pytz</code> package have a format like <code>2013b</code>. <a href="http://www.python.org/dev/peps/pep-0426" rel="noreferrer">PEP426</a> uses the version identifiers described in <a href="http://www.python.org/dev/peps/pep-0440" rel="noreferrer">PEP440</a>, which specifies that:</p> <blockquote> <p>Public version identifiers MUST comply with the following scheme:</p> <pre><code>N[.N]+[{a|b|c|rc}N][.postN][.devN] </code></pre> </blockquote> <p>Because the <code>pytz</code> versions like <code>2013b</code> do not match this format, version 1.4+ of pip is treating <em>all</em> versions of <code>pytz</code> as pre-release versions, and is not installing them by default.</p> <p>If you are only installing <code>pytz</code>, you can use the <code>--pre</code> flag to avoid this behaviour, but you wouldn't want to use this flag for installing your entire project's requirements: some packages might have unstable pre-release versions you don't want. In that case, use the behaviour described above: if you specify a "pre-release" version number for the package, then pip will search for "pre-release" versions of the package. So I've added this to my <code>requirements.txt</code>:</p> <pre><code>pytz&gt;=2013b </code></pre> <p>When I upgrade my packages, pip will now correctly search for and install the latest version of <code>pytz</code>.</p> <p>This has been filed as <a href="https://bugs.launchpad.net/pytz/+bug/1204837" rel="noreferrer">issue #1204837 in the pytz bug tracker</a> and <a href="https://github.com/pypa/pip/issues/974" rel="noreferrer">issue #974 in the pip bug tracker</a>.</p> <p><strong>Stop Press</strong>: As described in the <a href="https://bugs.launchpad.net/pytz/+bug/1204837" rel="noreferrer">PyTz bug report</a>, the version numbering of pytz has now been changed to, for example, 2013.7 - so once you have upgraded to this, the problem should no longer occur.</p>
    singulars
    1. This table or related slice is empty.
    1. POCould not find a version that satisfies the requirement pytz
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USChris
    1. USJeremy
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCould not find a version that satisfies the requirement pytz
      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. VTApproveEditSuggestion
    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. VTAcceptedByOriginator
    1. COThe [updated PEP 440](http://www.python.org/dev/peps/pep-0440/#olson-database-versioning) seems to say that pytz should be using the format 0.2013.6, not 2013.6. Confusing.
      singulars
      1. PO
      1. USJeremy
 

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