| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Do this so I am available as a reference for questions about the changes I
have made
|
| | |
|
| |\
| |
| |
| | |
https://github.com/skwashd/python-semanticversion into skwashd-tilde-caret
|
| | | |
|
| |\ \
| | |
| | |
| | | |
https://github.com/MinchinWeb/python-semanticversion into MinchinWeb-bump-version-2
|
| | |/ |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've updated the `BaseSemVerField` method `get_prep_value` so that it
will return None when the field value is None, rather than the string
representation 'None'. Previously this would break the ORM, which would
save the string 'None' into the database, and then attempt to parse that
as a version number. This change means that the default empty value for
both VersionField and SpecField is None. Both derive from CharField,
which uses an empty string as its default empty value, however it seems
more logical in the case of these objects that no object is null, and
not an empty string.
Includes tests.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
... to guarantee the settings get executed before any code in that app. Since
python's unittest.TestLoader does not guarantee in what order it will import
modules while hunting for test cases, the unit tests could fail to even load if
tests.django_test_app.models was loaded before tests.test_django. This failure
was seen on ARM machines, which happened to traverse the module tree in an
inconvenient order.
|
| | |
|
| |
|
