I'm floating the question to the satchmo user community.  Does anyone here
actually need the python 2.3 compatibility we've been maintaining?
Django is considering dropping support for 2.3 as of Django 1.1 release, and
I'd certainly like to follow suite.  Generators, built-in sets, decorator
syntax, and most importantly, forward compatibility with 2.6 & 3.0 are all
going to be much easier if we drop the compatibility code.

So, anyone use it?  Why?  Did you know that Python.org doesn't even release
security updates for it any more and that it is therefore a bad idea to run
your store which handles payment information on it?  Could you update to 2.4
or preferably 2.5 if you needed to or are you actually stuck with it for
some good reason?

--
Bruce Kroeze
http://gosatchmo.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Satchmo users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/satchmo-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to