This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
1 file changed
+1
-1
lines changed+1-1
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
7 | | - | |
| 7 | + | |
8 | 8 | | |
9 | 9 | | |
10 | 10 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
7 | | - | |
| 7 | + | |
8 | 8 | | |
9 | 9 | | |
10 | 10 | | |
| |||
5 commit comments
estebistec commentedon Mar 18, 2014
No v1.5?
jmoiron commentedon Mar 18, 2014
master is going to target compatibility with django 1.(4,5,6)
estebistec commentedon Mar 18, 2014
I see, so the version is designed to match the latest compatible version?
jmoiron commentedon Mar 18, 2014
Yep. Despite not releasing a 1.5 (the 1.4.1 tag I think supports it) I still want to follow this:
http://johnny-cache.readthedocs.org/en/latest/#deprecation-policy
pablorecio commentedon Apr 7, 2014
Is there any chance we could get 1.4.1 and 1.6a released to PyPI? It'd be really helpful.