Hi.
While I was trying to get our docs published on readthedocs.org I stumbled on a odd thing. Apparently they use django 1.3 internally and our requirement on django << 1.3 conflicts with that.
I have quickly upgraded lava-server to use 1.3 and (surprisingly) all tests passed. I will play around with 1.3 to see if there are any issues that test suite does not spot.
Apart from staticfiles transition (which I just realized can happen in parallel, as we can keep using staticfiles 0.3.4 and django 1.3 (and only transition to contrib.staticfiles or staticfiles 1.x when we wish) I found one issue: openid
It seems that the openid backend we are using is somewhat outdated and does not implement the required interfaces. For 1.3 that's okay but 1.4 will not be compatible with that API any more.
This causes three tests to be skipped, and a warning message to be logged. I was wondering how we should proceed:
1) Upgrade to latest django-openid-auth/openid in hopes that it works better.
2) Ignore the problem
3) Upgrade as in 1) and fix any missing issues.
What do you guys think? ZK
On Tue, 19 Jul 2011 14:07:53 +0200, Zygmunt Krynicki zygmunt.krynicki@linaro.org wrote:
Hi.
While I was trying to get our docs published on readthedocs.org I stumbled on a odd thing. Apparently they use django 1.3 internally and our requirement on django << 1.3 conflicts with that.
I have quickly upgraded lava-server to use 1.3 and (surprisingly) all tests passed. I will play around with 1.3 to see if there are any issues that test suite does not spot.
Oh good.
Apart from staticfiles transition (which I just realized can happen in parallel, as we can keep using staticfiles 0.3.4 and django 1.3 (and only transition to contrib.staticfiles or staticfiles 1.x when we wish) I found one issue: openid
It seems that the openid backend we are using is somewhat outdated and does not implement the required interfaces. For 1.3 that's okay but 1.4 will not be compatible with that API any more.
This causes three tests to be skipped, and a warning message to be logged. I was wondering how we should proceed:
- Upgrade to latest django-openid-auth/openid in hopes that it works
better.
This makes sense to me.
Ignore the problem
Upgrade as in 1) and fix any missing issues.
django-openid-auth is maintained by Canonical ISD so I expect we'll be able to bully them into fixing any bugs in this area.
Cheers, mwh