On Fri, 2008-07-11 at 04:47 -0700, allisongardner wrote:
> Okay, not sure anyone is going to bother to read this but I hope so: I
> have read the ticket (understood about a 10th) and looked at the
> changeset 6187. I am assuming I copy and paste this somewhere but
> precisely what do i copy and paste it into and how do I find the
> file...not to confident about paths etc. and workign in shells.

Are you using Django 0.96? If you're using Django trunk (a subversion
checkout), that bug should already be fixed.

If you are using 0.96, it might be possible to apply one of the patches
on that ticket, but I don't know for sure if it will work or not. Things
have changed a *lot* in that area over recent months. Particularly if
you're not comfortable working with the "patch" program (which is used
to apply patches like that) and shells, this is going to be a difficult
thing to do, since debugging any consequent problems will be tricky.

At this point, if you're just starting out with Django, I would
*strongly* recommend using a subversion checkout and starting from
there. There have been a lot of changes between 0.96 (released in April
2007) and today and most of those changes have fixed bugs. Don't worry
about a subversion checkout not being a "released version". A lot of
people run production code from subversion checkouts and we are working
very hard on keeping things stable at the moment as we work towards a
1.0 release in 8 weeks.

[Of course, if all this is moot and you're already using a subversion
checkout, then it's either not #1760 or the fix in #1760 isn't correct
for some situation. That will make me sad.]

Regards,
Malcolm



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

Reply via email to