| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Also replace the badge with Github Actions
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Avoids issues with too old pip being unable to download wheels for
cryptography.
|
|
|
|
|
|
| |
We can't use python -m unittest discover directly, as it mistakenly
tries to import the source code of the Django test app without going
through the setup_django module first.
|
| |
|
|
|
|
|
|
|
| |
Instead of relying on setup.py, use setup.cfg.
Dev/doc requirements have been moved there as well, under the `doc` and
`dev` extras.
|
|
|
|
|
|
| |
As caught by Emilio Reyes.
Closes #103.
|
|
|
|
| |
Add missing blank lines.
|
|
|
|
| |
Related to issue #97.
|
| |
|
| |
|
|
|
|
|
|
| |
Including docs and tests.
Closes #98.
|
| |
|
| |
|
|
|
|
|
|
|
| |
A leading zero is forbidden in the SemVer spec, but could be valid under
other schemes; when coercing, it can easily be removed.
Closes #89, thanks to Andrew Ni for the report.
|
|
|
| |
resolves #87
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Thanks to Nathan Walters for spotting this.
Npm ranges with a `<X.Y.Z-P` component were not properly expanded:
they were converted to:
<X.Y.0 || (>=X.Y.0 && <X.Y.Z-P && no-prerelease)
The correct expansion is:
<X.Y.0 || (>=X.Y.0-* && <X.Y.Z-P)
Closes #86.
|
|
|
|
|
|
|
|
| |
This function allows developers to preview the structure of the
resulting clause parsed from a spec, usable with
`print(spec.clause.prettyprint())`.
Apply typical PEP8 indentation rules.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This (deprecated) property failed when used on a `Spec` item based on a
single-term range (e.g. `==0.1.2` `<2.0.0`).
Closes #82.
|
|
|
|
| |
Signed-off-by: Raphaël Barrois <raphael.barrois@polytechnique.org>
|
| |
|
| |
|
|
|
|
| |
This attribute wasn't meant to be removed.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Streamline the release process.
|
|
|
|
| |
Always include every dev/doc/test related files.
|
| |
|
| |
|
|
|
|
| |
Write clear, explicit rules for the `SimpleSpec` syntax.
|
|
|
|
|
| |
Their comparison semantics were ill-defined, and mostly an
implementation detail for the old, 'native' specs.
|
|
|
|
|
| |
- Use proper theme in development
- Use ReadTheDocs version numbers in titles
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will be used in `sort(..., key=lambda v: v.precedence_key)`.
Remove previous comparison/ordering implementation.
The current implementation relies on a 4-tuple:
- major, minor, patch (as integers) - natural order matches precedence
rules
- a tuple of identifiers for the prerelease component.
The identifiers for the prerelease components are based on:
- A `NumericIdentifier` class, that compares number using their natural
order, and always compares lower than non-numeric identifiers
- A `AlphaIdentifier` class for non-numeric identifiers; it compares
versions using ASCII ordering.
- A `MaxIdentifier` class, that compares higher to any other identifier;
used to ensure that a non-prerelease version is greater than any of
its prereleases.
|
|
|
|
|
|
| |
Using `make update` is closer to common patterns than `make
install-deps`; it is also suitable to update the local development
environment.
|
| |
|
|
|
|
|
|
|
|
|
| |
The internal features from those classes will be removed in future
versions:
- The `Spec` class is incompatible with the support of multiple syntaxes
- The `SpecItem` class was an implementation detail, but doesn't support
complex `Range` combinations.
|
|
|
|
|
|
|
|
| |
The code follows closely the specification available at
https://docs.npmjs.com/misc/semver.html.
Despite similarities, the matching logic is fully separate from the
`native` code, since both might evolve at their own scales.
|