Re: ANN: Django website redesign launched
+1 for keeping it courteous. The Django community is far and away the most helpful e-group of people I've seen in 30 years of programming in dozens of languages. That post was much ruder than anything I've ever seen on a Django forum, and did deserve to be addressed. Thanks, Danielle! --Fred Fred Stluka -- mailto:f...@bristle.com -- http://bristle.com/~fred/ Bristle Software, Inc -- http://bristle.com -- Glad to be of service! Open Source: Without walls and fences, we need no Windows or Gates. On 12/17/14 6:13 AM, Baptiste Mispelon wrote: Hi Torsten, As far as I know, it's not often that people get kicked out of this mailing list (note that Christian was kicked out, not banned, so he can join back if he'd like) so I'm not sure what's "customary". However, we strive to create a friendly and inclusive community here, so toxic and insulting behavior is not simply ignored. In this instance, I think Daniele's response was appropriate and I stand by it too. I hope that answers your question. Cheers, Baptiste PS: The mailing list is publicly viewable at https://groups.google.com/forum/#!forum/django-developers. It's only for posting here that you need to be registered. On 12/17/2014 11:29 AM, Torsten Bronger wrote: Hallöchen! Daniele Procida writes: [...] In the meantime I have removed you from our email lists, since your tone is not welcome here. Please don't come back unless you can communicate in a more acceptable way. Is this customary procedure on this mailing list in such cases? Normally one simply ignores postings/authors one doesn't like. I hope that banned users don't have the answers to my questions. ;-) Besides, a sock puppet is made in minutes ... Tschö, Torsten. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/549376A5.3000108%40bristle.com. For more options, visit https://groups.google.com/d/optout.
Re: Bypassing 1.7+ migrations
Hi Markus, On Thursday 18 December 2014 08:54:30 Markus Holtermann wrote: > > manage=False won't gain you anything, since those models will still show > up in migrations, because they need to be able to be referenced by > managed models. The migration database operations are noops though. > As far as I understood, Marcin wants to treat *all* models as unmanaged; there are no managed models to reference the unmanaged ones. Shai.
Re: ANN: Django website redesign launched
The new Design looks great! Awesome job! One thing I really like about https://docs.python.org/3/ is the ability to show/hide the side bar. The new design features a very large sidebar, being able to toggle it would be awesome. Also as previously mentioned trac doesn't look right yet. On Tuesday, December 16, 2014 11:09:55 AM UTC-5, Jannis Leidel wrote: > > Hi everyone, > > We're incredibly proud to share with you the new design of the Django > website, the documentation and the issue tracker. > > This is a long time coming and we couldn't be happier to finally ship it > :) > > As you can imagine, there will be bugs, so please bear with us and report > issues to the issue tracker at > https://github.com/django/djangoproject.com/issues > > More infos about the redesign and its history can be found in the blog > post: > > > https://www.djangoproject.com/weblog/2014/dec/15/announcing-django-website-redesign/ > > > Happy coding, everyone! > > Jannis > > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/c9438430-7908-464f-82ce-b89131e3bbea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Settings: lists or tuples?
On 12/17/2014 11:49 PM, Russell Keith-Magee wrote:
> On Thu, Dec 18, 2014 at 7:48 AM, Carl Meyer wrote:
>> This is clever, but on second thought I'm trying to figure out in what
>> scenario a backwards-compatibility would actually occur here. In the
>> context of a user's settings modules, global_settings plays no role at
>> all: you can't add to a global setting default in your settings.py
>> (unless you've imported global_settings yourself, which is certainly
>> making use of undocumented internals).
>>
>> So it seems to me that the only scenario in which this would actually
>> cause a back-compat problem would be if someone is using a tuple
>> setting, which they are not setting themselves (and thus are using the
>> global default), and they are adding to it in their runtime code (not in
>> their settings file). For instance:
>>
>> my_ctx_procs = settings.TEMPLATE_CONTEXT_PROCESSORS + ('another',)
>>
>> The common case of appending to a setting in your settings.py (due to
>> use of some kind of split-settings) should not be impacted at all
>>
>
> That's a fair point. The benefit for an __add__ definition is likely to be
> a lot smaller than I originally thought.
>
> The only place I can think that it might pop up is in older (pre
> @override_settings) test harnesses; that said, a failure during test isn't
> a major inconvenience
>
> So - I retract my suggestion - I think I can live with just documenting
> this as a backwards compatibility.
Works for me!
Carl
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/5492CF00.904%40oddbird.net.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
Re: annotate() and generic relations
On Thursday, December 18, 2014 6:20:34 AM UTC+2, Shai Berger wrote: > > > The generic relations still work a bit differently to that of reverse > > foreign key - where reverse foreign keys can be filtered > > with .filter(reverse_relation=some_related_object), that doesn't work > > with reverse relations, instead you have to explicitly provide the > > primary key value by doing .filter(generic_rel=some_related_object.pk). > > > So, I'm not sure if we should document this behavior or try to fix it as > well. > > I think we should fix this, but this isn't a high-priority item, at least not to me. This should be easier to fix in 1.9 when we can drop the backwards compat for pre 1.6 lookups from the ORM. - Anssi -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/18bd83ec-c480-4e12-9627-50f93ef6cbcd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
