|
1 | | -univers: mostly universal version and version ranges comparison and conversion |
| 1 | +univers: mostly universal version and version range comparison and conversion |
2 | 2 | =============================================================================== |
3 | 3 |
|
4 | 4 | |Build Status| |License| |Python 3.6+| |
@@ -62,16 +62,16 @@ For each scheme, **univers** provides an implementation for: |
62 | 62 | - converting a range back to its scheme-native range syntax and to the |
63 | 63 | ``vers`` syntax. |
64 | 64 |
|
65 | | -**univers** implements ``vers``, an experimental unified and mostly universal |
| 65 | +**univers** implements VERS, an experimental unified and mostly universal |
66 | 66 | version range syntax. It can parse and convert an existing native version range |
67 | | -strings to this unified syntax. For example, this means: |
| 67 | +string to this unified syntax. For example, this means: |
68 | 68 |
|
69 | 69 | - converting ">=1.2.3" as used in a Python package into ``vers:pypi/>=1.2.3``, |
70 | 70 |
|
71 | 71 | - or converting "^1.0.2" as used in an npm package dependency declaration into |
72 | 72 | ``vers:npm/>=1.0.2|<2.0.0`` |
73 | 73 |
|
74 | | -The supported package ecosystems versioning schemes and underlying libraries |
| 74 | +The supported package ecosystem versioning schemes and underlying libraries |
75 | 75 | include: |
76 | 76 |
|
77 | 77 | - npm that use the "node-semver" ranges notation and the semver versions syntax |
@@ -124,7 +124,7 @@ Alternative |
124 | 124 | Rather than using ecosystem-specific version schemes and code, another approach |
125 | 125 | is to use a single procedure for all the versions as implemented in `libversion |
126 | 126 | <https://github.com/repology/libversion>`_. ``libversion`` works in the most |
127 | | -common case but may not work correctly when a task that demand precise version |
| 127 | +common cases but may not work correctly when a task that demand precise version |
128 | 128 | comparisons such as for dependency resolution and vulnerability lookup where |
129 | 129 | a "good enough" comparison accuracy is not acceptable. ``libversion`` does not |
130 | 130 | handle version range notations. |
|
0 commit comments