note: some files have two versions in them, e.g.:
```
assert CffiRecipe._version == "1.15.1"
class CffiRecipePinned(util.InheritedRecipeMixin, CffiRecipe):
version = "1.17.1"
```
The assert is left there as I think it might be useful to get a failure if we rebase p4a
and the upstream recipe version changes. There might be substantial changes in the upstream
recipe that we need to adapt to. In the happy case, if we rebase p4a, we just have to manually
update these asserts to the new versions at that time.
15 lines
418 B
Python
15 lines
418 B
Python
from pythonforandroid.recipes.six import SixRecipe
|
|
|
|
|
|
assert SixRecipe._version == "1.15.0"
|
|
assert SixRecipe.depends == ['setuptools', 'python3']
|
|
assert SixRecipe.python_depends == []
|
|
|
|
|
|
class SixRecipePinned(SixRecipe):
|
|
version = "1.17.0"
|
|
sha512sum = "fcfa58b03877ac3ac00a4f85b5fea4fecb2a010244451aa95013637a0aa21529f3dcfe25c0a07c72da46da1fa12bc0c16b6c641c40c6ab2133e5b5cbb5a71e4b"
|
|
|
|
|
|
recipe = SixRecipePinned()
|