Closed GoogleCodeExporter closed 9 years ago
confirmed
Original comment by ericd...@gmail.com
on 27 Sep 2008 at 12:12
Yes, we know we have some 2.5 code that shouldn't be in core and the apps. It
would be much more helpful for
people to start finding those places as it will help fix it. I personally see
Pinax supporting what versions of Python
that the Django that we target supports. We target Django 1.0 and it has
support for Python 2.3. We ought to
force the requirement on apps as well.
Original comment by bros...@gmail.com
on 27 Sep 2008 at 1:13
upstream with patch
http://code.google.com/p/django-crashlog/issues/detail?id=3
Original comment by ericd...@gmail.com
on 27 Sep 2008 at 1:22
are there other known places where python 2.4 breaks? decorator syntax?
Original comment by ericd...@gmail.com
on 27 Sep 2008 at 1:24
Several of the external apps and libs use the hashlib library, which is new to
python
2.5.
I' using 2.4 and I had to download it from the Python package index
(http://pypi.python.org/pypi/hashlib/20060408a).
Original comment by richardb...@gmail.com
on 27 Sep 2008 at 1:21
In pinax/local_apps/account/templatetags/openid_tags.py the any() function is
used,
this function is new to 2.5.
Original comment by richardb...@gmail.com
on 27 Sep 2008 at 1:38
Contrary to my original intentions, we have voted (with discussion on IRC) that
we will not support 2.3. There is
too much work involved for not much gain and 2.3 is over five years old
(seriously, its okay to upgrade now). We
may decide to support 2.4, but no guarantees considering it is almost four
years old.
Original comment by bros...@gmail.com
on 22 Nov 2008 at 4:06
While letting 2.3 go is ok but 2.4 is still the default on Debian etch.
Although it's slated to be updated at the end
of the year it might be around a while still.
Original comment by leidel
on 22 Nov 2008 at 12:21
Original issue reported on code.google.com by
jgra...@gmail.com
on 10 Sep 2008 at 6:04