Re: [ANNOUNCE] Security releases (Django 1.3.5, Django 1.4.3, Django 1.5 beta 2)
Yeah, we know -- we usually wait a bit (24 hours, give or take) before we tag them. Thanks for the spot. Jacob On Mon, Dec 10, 2012 at 11:09 PM, Yo-Yo Ma wrote: > There aren't yet Git tags for the releases. > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-developers/-/ipPpizg3flcJ. > 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. > > -- 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.
[ANNOUNCE] Security releases (Django 1.3.5, Django 1.4.3, Django 1.5 beta 2)
There aren't yet Git tags for the releases. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/ipPpizg3flcJ. 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.
Re: Possible bug with GenericRelations and values_list
On Mon, Dec 10, 2012 at 8:58 PM, Skylar Saveland
wrote:
>
> I posted this in the django-users group but I think it may merit posting
> here, as well. I have a test case which I think should pass.
>
>
> https://github.com/skyl/django/commit/556df1c46146c2fc9c4022d838fa23f652f0ea8d
>
> Is this a bug? If so, is it a bug that is not in the tracker?
>
>
I'd say it's a bug. I can't find an exact match in trac but I'd guess the
root cause is similar to what's underlying:
https://code.djangoproject.com/ticket/11387
The SQL for the query in your test case that attempts to fetch the Animal
object tags using values_list is:
SELECT "generic_relations_taggeditem"."id" FROM "generic_relations_animal"
LEFT OUTER JOIN "generic_relations_taggeditem" ON
("generic_relations_animal"."id" =
"generic_relations_taggeditem"."object_id")
This suffers from the same problem as the sql in #11387: it's not including
any restriction on content type in the query, thus you can get tags that
are pointing to non-Animals.
Karen
--
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.
Re: #19076 - TemplateView does not support setting mime type
Correct me if I'm wrong, but that ticket is marked as a bug. Cheers, AT On Mon, Dec 10, 2012 at 10:06 PM, Russell Keith-Magee < russ...@keith-magee.com> wrote: > Hi Gavin, > > Unfortunately, the deadline for new features in Django 1.5 has passed; > once we release a beta, we only accept bug fixes. > > Yours, > Russ Magee %-) > > > On Tue, Dec 11, 2012 at 7:54 AM, Gavin Wahl wrote: > >> I know this is last minute, but is there any chance of getting this >> change in 1.5? It's a simple change, and is necessary now that >> direct_to_template is gone. >> >> https://code.djangoproject.com/ticket/19076 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/django-developers/-/1ksTGUqQ2Z0J. >> 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. >> > > -- > 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. > -- 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.
Possible bug with GenericRelations and values_list
Hi, I posted this in the django-users group but I think it may merit posting here, as well. I have a test case which I think should pass. https://github.com/skyl/django/commit/556df1c46146c2fc9c4022d838fa23f652f0ea8d Is this a bug? If so, is it a bug that is not in the tracker? Thanks, Skylar -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/QXo71gcsPOcJ. 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.
Re: #19076 - TemplateView does not support setting mime type
Hi Gavin, Unfortunately, the deadline for new features in Django 1.5 has passed; once we release a beta, we only accept bug fixes. Yours, Russ Magee %-) On Tue, Dec 11, 2012 at 7:54 AM, Gavin Wahl wrote: > I know this is last minute, but is there any chance of getting this change > in 1.5? It's a simple change, and is necessary now that direct_to_template > is gone. > > https://code.djangoproject.com/ticket/19076 > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-developers/-/1ksTGUqQ2Z0J. > 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. > -- 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.
#19076 - TemplateView does not support setting mime type
I know this is last minute, but is there any chance of getting this change in 1.5? It's a simple change, and is necessary now that direct_to_template is gone. https://code.djangoproject.com/ticket/19076 -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/1ksTGUqQ2Z0J. 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.
[ANNOUNCE] Security releases (Django 1.3.5, Django 1.4.3, Django 1.5 beta 2)
Django 1.3.5, Django 1.4.3 and Django 1.5 beta 2 have just been issued in response to security issues. Details are available here: https://www.djangoproject.com/weblog/2012/dec/10/security/ -- 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.
Re: Proposal: Django Admin Site and "pretty" app name
Just to add a quick update here. Not much has happened on the branch since Djangocon - but we had some valuable discussions. I'm hoping to get some time over the holidays to get this back up to a more current form. Russ and Karen gave some great feedback, and there is some straightforward but somewhat tedious cleanup - mostly involving backing out the metaclass pattern for app objects. The crux will be a way to introduce this in form that provides some limited, targeted benefits such as the verbose app name, without opening too much of a pandora's box of enabling a range of unintended "features" centered on abuse of the app-cache. As Russ said - this has always had the potential to be a ginormous bike-shed, and if any Django specific interfaces on a application class that go beyond "its just a Python class" are to be introduced, they have to be done so with due consideration. -Preston On Friday, December 7, 2012 8:09:22 PM UTC-8, Russell Keith-Magee wrote: > > It's Preston Holme's app-loading branch - the Github branch Ramiro > referenced earlier in this thread. > > https://github.com/ptone/django/tree/app-loading > > Yours, > Russ Magee %-) > > On Sat, Dec 8, 2012 at 12:02 PM, Pedro J. Aramburu > > > wrote: > >> Which one is the branch? I can't seem to find it. >> >> On Friday, December 7, 2012 10:41:16 PM UTC-3, Russell Keith-Magee wrote: >> >>> >>> On Sat, Dec 8, 2012 at 9:29 AM, Pedro J. Aramburu >> > wrote: >>> Ramiro, I've read the ticket but it seems stuck. I just want it to go forward because I think it's a major UI/UX issue for non-programmers the lack of "pretty" app names. But I want it to be done right with a proper app metadata handling. >>> >>> >>> You won't get any argument from me, or anyone else in the core team. >>> This *is* an important issue. The problem is that the issue *isn't* >>> entirely cosmetic. It's very easy to say that we "just" need to attach a >>> configurable name to applications -- but in order to do this, you need to >>> address the more fundamental issue of what an application *is*. In having >>> that discussion, you hit a whole raft of *other* problems that are related >>> to Django's definition of apps. That's why this patch has taken so long to >>> come to fruition. >>> >>> The thing is that there isn't any consensus about the way to go so I'm terrified of starting with my ideas without anyone accepting them and also because I don't know if anyone is already working on them (as the tickets are open) but there seems to be no constant activity on them. That's why I need some guidance from someone experienced with the process. >>> >>> There's plenty of consensus about the broad strokes. The disagreement is >>> about the little details. There's no constant activity because it's a big >>> problem; that means we've gone through multiple maintainers over time, and >>> the activity level rises and falls as attention is drawn onto other >>> priorities (such as bug fixing for the 1.5 release). >>> >>> I last looked at Preston's Github branch during the DjangoCon US >>> sprints, and at that time, it was extremely close to being ready for >>> merging -- it mostly just needed eyeballs, testing, and documentation. If >>> you want to help out, I'd suggest grabbing that code, and trying to (a) get >>> it up to date, and (b) testing it with your own projects, and © helping to >>> stub out documentation. >>> >>> I'd very much like to see this patch land as part of the 1.6 cycle -- >>> App name translations aren't a big issue for me personally, but all the >>> other related features -- such as having a reliable startup sequence, a >>> place for application-level configuration, and a place for one-time >>> initialisation -- *are* an issue for me, and fixing these problems are all >>> side effects of adding an application configuration object. >>> >>> Yours, >>> Russ Magee %-) >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/django-developers/-/KqGTJ8TPPgcJ. >> >> To post to this group, send email to >> django-d...@googlegroups.com >> . >> To unsubscribe from this group, send email to >> django-develop...@googlegroups.com . >> For more options, visit this group at >> http://groups.google.com/group/django-developers?hl=en. >> > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/cFPu8nmwE1cJ. 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.
