Hi Gianfranco, > Oh... so seems that the django version is not too old to be useless, but > too new, right?
that's correct The django people have a pretty rigorous deprecation schedule where they mark parts of the API as deprecated for a period of time prior to actual removal. The intention of this is to give users of this code time to adjust. The problem is that the scale and speed of the changes is still mismatched to what upstreams like pootle can manage. I don't think an embedded copy of django is something we want to deal with so I'm not even entertaining this thought just yet. thanks for prodding again on this... we might yet come up with a solution to the problem some how! cheers Stuart -- Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7 -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201407290129.23240.stu...@debian.org
