From: Josh J. <jun...@gm...> - 2009-03-14 18:28:57
|
Upon initial testing it looks like using the latest Django from development works. I have also used the 1.1 alpha and it appears to take care of the issue. I'll continue my Django tests using the 1.1 alpha for now. Thanks for the help on this one. Josh Juneau jun...@gm... http://jj-blogger.blogspot.com http://www.gathereventplanning.com Twitter ID: javajuneau On Sat, Mar 14, 2009 at 1:19 PM, Josh Juneau <jun...@gm...> wrote: > Do you know which release the fix is in? My guess is that it is not yet > available in an official release...I am using 1.0.2 in my environment. > Looks like it was applied in late January. > I will download the latest development version of Django and try it out to > see if it works. > > Thanks Frank > > Josh Juneau > jun...@gm... > http://jj-blogger.blogspot.com > http://www.gathereventplanning.com > Twitter ID: javajuneau > > > On Sat, Mar 14, 2009 at 1:10 PM, Frank Wierzbicki <fwi...@gm...>wrote: > >> >> Sorry this took me a while to recognize, but I sent Django a patch to >> fix this behavior (http://code.djangoproject.com/ticket/9789), but it >> doesn't look like it has been applied. I'm not really sure why older >> versions of Jython work... >> >> -Frank >> >> --~--~---------~--~----~------------~-------~--~----~ >> You received this message because you are subscribed to the Google Groups >> "django-jython-dev" group. >> To post to this group, send email to dja...@go... >> To unsubscribe from this group, send email to >> dja...@go...<django-jython-dev%2Bu...@go...> >> For more options, visit this group at >> http://groups.google.com/group/django-jython-dev?hl=en >> -~----------~----~----~----~------~----~------~--~--- >> >> > |