So, last time I saw, you had only run against sqlite. Do you need help testing it against postgres, MySQL, and oracle (perhaps some unofficial ones)? What about all the caching backends? Do we need tests Python 3 equivalent tests for the ones that were skipped due to being Python 2-isms? What about some sort of "porting guide" or other needed documentation?
Basically, what's left, besides getting it merged into the official trunk that people can help you with? 2011/12/2 Håkon Erichsen <hakon.erich...@gmail.com> > 2011/12/2 Vinay Sajip <vinay_sa...@yahoo.co.uk> > >> The Python 3 port now has all tests passing on 2.7.2 and 3.2.2 with >> the same codebase: >> >> > Wohoo! Can't wait to try py3 with Django! :) > > > Regards, > Håkon Erichsen > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > -- Joe & Anne Tennies tenn...@gmail.com -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
