NumPy has the following versioning scheme (numbers given are examples; they can be > 9 in principle):
Released version: '1.8.0', '1.8.1', etc.
Alpha: '1.8.0a1', '1.8.0a2', etc.
Beta: '1.8.0b1', '1.8.0b2', etc.
Release candidates: '1.8.0rc1', '1.8.0rc2', etc.
Development versions: '1.8.0.dev-f1234afa' (git commit hash appended)
Development versions after a1: '1.8.0a1.dev-f1234afa',
'1.8.0b2.dev-f1234afa', '1.8.1rc1.dev-f1234afa', etc.
Development versions (no git hash available): '1.8.0.dev-Unknown'
Comparing needs to be done against a valid version string or other NumpyVersion
instance. Note that all development versions of the same (pre-)release compare equal.
NumPy version string ( np.__version__
).
Parse and compare numpy version strings.
>>> from numpy.lib import NumpyVersionThis example is valid syntax, but raise an exception at execution
... if NumpyVersion(np.__version__) < '1.7.0':
... print('skip')
... # skip
>>> NumpyVersion('1.7') # raises ValueError, add ".0" Traceback (most recent call last): ... ValueError: Not a valid numpy version stringSee :
The following pages refer to to this document either explicitly or contain code examples using this.
numpy.lib._version.NumpyVersion
Hover to see nodes names; edges to Self not shown, Caped at 50 nodes.
Using a canvas is more power efficient and can get hundred of nodes ; but does not allow hyperlinks; , arrows or text (beyond on hover)
SVG is more flexible but power hungry; and does not scale well to 50 + nodes.
All aboves nodes referred to, (or are referred from) current nodes; Edges from Self to other have been omitted (or all nodes would be connected to the central node "self" which is not useful). Nodes are colored by the library they belong to, and scaled with the number of references pointing them