Re: Settings: lists or tuples?

> On Dec 18, 2014, at 12:49 AM, Russell Keith-Magee > wrote: > > So - I retract my suggestion - I think I can live with just documenting this > as a backwards compatibility. Sounds good. In case anyone is interested, I made a pull request (not complete) with an implementation of a ‘ConfList’

Re: Bypassing 1.7+ migrations

Hey Shai, 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. /Markus On Thu, Dec 18, 2014 at 06:08:52AM +0200, Shai Berger wrote: FWIW, t

Re: Settings: lists or tuples?

On Thu, Dec 18, 2014 at 7:48 AM, Carl Meyer wrote: > > On 12/17/2014 04:39 PM, Russell Keith-Magee wrote: > > On Thu, Dec 18, 2014 at 5:03 AM, Aymeric Augustin < > > aymeric.augus...@polytechnique.org> wrote: > > > >> On 17 déc. 2014, at 21:54, Carl Meyer wrote: > >> > >>> So I think there is a b

Re: annotate() and generic relations

Hi Anssi, Thanks for that quick fix. On Wednesday 17 December 2014 10:16:27 Anssi Kääriäinen wrote: > > It turns out this is easy to fix. There is a patch for this at > https://github.com/django/django/pull/3743. > (All: In case you're interested but lazy -- this was committed) > The generic r

Re: Bypassing 1.7+ migrations

FWIW, the approach I would go for is to try to monkeypatch managed=False into the base model Meta. Shai. On Tuesday 16 December 2014 14:49:25 Andrew Godwin wrote: > Hi Marcin, > > You can't bypass migrations as much as you can't bypass syncdb; that is, > the commands are separate and you can ch

Re: Settings: lists or tuples?

> On Dec 17, 2014, at 6:12 PM, Carl Meyer wrote: > > On 12/17/2014 04:57 PM, Ryan Hiebert wrote: >>> >> What would __iadd__ do in this subclass? Would it behave like tuple and >> create a new DjangoList, or would it behave like list and extend the >> original list? > > For maximum backwards-co

Re: Settings: lists or tuples?

On 12/17/2014 04:57 PM, Ryan Hiebert wrote: > >> On Dec 17, 2014, at 5:48 PM, Carl Meyer wrote: >> >> On 12/17/2014 04:39 PM, Russell Keith-Magee wrote: >>> >>> I agree that lists are preferable to tuples. >>> >>> One option for handling existing projects might be to define our own >>> subclass o

Re: Settings: lists or tuples?

> On Dec 17, 2014, at 5:48 PM, Carl Meyer wrote: > > On 12/17/2014 04:39 PM, Russell Keith-Magee wrote: >> >> I agree that lists are preferable to tuples. >> >> One option for handling existing projects might be to define our own >> subclass of list that defines __add__, __iadd__, and __radd__

Re: Settings: lists or tuples?

On 12/17/2014 04:39 PM, Russell Keith-Magee wrote: > On Thu, Dec 18, 2014 at 5:03 AM, Aymeric Augustin < > aymeric.augus...@polytechnique.org> wrote: > >> On 17 déc. 2014, at 21:54, Carl Meyer wrote: >> >>> So I think there is a backwards-compatibility issue. >> >> Indeed. >> >>> Personally, I wo

Re: Settings: lists or tuples?

On Thu, Dec 18, 2014 at 5:03 AM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > On 17 déc. 2014, at 21:54, Carl Meyer wrote: > > > So I think there is a backwards-compatibility issue. > > Indeed. > > > Personally, I would love to decide to just bite this bullet and > > normalize

Re: Migrations in Django 1.7 make unit testing models harder

At the risk of reviving an old topic, I wanted to add one significant point in favor of (and mitigation for) running tests with migrations disabled: Speed. Creating a test DB in sqlite for our project (~100 database tables) takes approximately 1-2 minutes on most developer machines. 1-2 minutes

Re: Settings: lists or tuples?

On Wed, Dec 17, 2014 at 9:48 PM, Aymeric Augustin wrote: Surprisingly, it seems that there isn’t a backwards compatibility problem with changing the type to lists, as the following pattern still works: # myproject/settings.py from django.conf.global_settings import FILE_UPLOAD_HANDLERS FILE_U

Re: Settings: lists or tuples?

I agree lists are the way to go. I have heard that tuples are faster, but I don't think that outweighs comma issue and inconsistency. global_settings isn't completely undocumented, based on greping the docs. Seems to me we should at least make the docs and project_template consistent and use li

Re: Settings: lists or tuples?

On 17 déc. 2014, at 21:54, Carl Meyer wrote: > So I think there is a backwards-compatibility issue. Indeed. > Personally, I would love to decide to just bite this bullet and > normalize to lists, but I think it would need to be marked as a > backwards-incompatibility in the release notes, and i

Re: Settings: lists or tuples?

+1 for lists. On Wed, Dec 17, 2014 at 3:54 PM, Carl Meyer wrote: > > On 12/17/2014 01:48 PM, Aymeric Augustin wrote: > > I’m about to introduce a new setting that is a sequence of things, > TEMPLATES, and I have to decide whether it will be a tuple of a list. > > > > Unfortunately Django is very

Re: Settings: lists or tuples?

On 12/17/2014 01:48 PM, Aymeric Augustin wrote: > I’m about to introduce a new setting that is a sequence of things, TEMPLATES, > and I have to decide whether it will be a tuple of a list. > > Unfortunately Django is very inconsistent in the type of settings. In > global_settings.py: > > - 22 s

Settings: lists or tuples?

Hello, I’m about to introduce a new setting that is a sequence of things, TEMPLATES, and I have to decide whether it will be a tuple of a list. Unfortunately Django is very inconsistent in the type of settings. In global_settings.py: - 22 settings are tuples - 10 are empty, 12 aren't

Windows users around?

Hey, I'm one of the most Windows-breaking committers, also because I don't care any more for this system. Sorry for that! (for you, not for me :-) Tim kindly pointed me to the following list of tickets which need love from some Windows users of Django: https://code.djangoproject.com/query?statu

Re: ANN: Django website redesign launched

For the Documentation, one suggestion I have is that the body font that’s more different from the source code font. It looks like you’re using Roboto (a Helvetica clone) for the body text and Incosolota for the source code. They’re a little too similar. Also, Roboto isn’t a good font for descr

Re: ANN: Django website redesign launched

Hi, I agree with Tino in most points. Thanks to the volunteers who did this and I really love the fact, that I can finally browse the docs on a mobile device. Great! But there certainly is a loss of both originality and the readability. Both of these things are no blockers and don't make the new

Re: ANN: Django website redesign launched

On Wednesday, December 17, 2014 12:59:10 PM UTC+1, Tino de Bruijn wrote: > > Hi, > > > - The font does not look crisp (can be because it's serif, or something > with my comp, dunno) > The association of *roboto* font and *-moz-osx-font-smoothing: grayscale* rule maybe ? Under code.djangoprojec

Re: ANN: Django website redesign launched

On Wednesday, December 17, 2014 8:39:21 AM UTC-5, Daniele Procida wrote: > > > We'd hate you to be "that guy" too. However, so far you are "that guy", > since merely announcing that you have identified numerous accessibility > issues is useless. > Ok. Tell the designer to google "chrome acce

Re: ANN: Django website redesign launched

On Wed, Dec 17, 2014, Rob wrote: >On Tuesday, December 16, 2014 5:58:00 PM UTC-5, Christian Schmitt wrote: >> >> Somehow I hate it. The website is the worst website I've seen since a long >> time. >> The contrast is really aweful. >> The issue Tracker got unusable due to the colors that aren't f

Re: ANN: Django website redesign launched

On Tuesday, December 16, 2014 5:58:00 PM UTC-5, Christian Schmitt wrote: > > Somehow I hate it. The website is the worst website I've seen since a long > time. > The contrast is really aweful. > The issue Tracker got unusable due to the colors that aren't focused on > readability. > Clearly. My

Re: ANN: Django website redesign launched

God job everyone! Do you think the Overview page should have the logos of the "Sites using Django"? it would be more visually appealing, in addition, people might be more aware of the logos than just plain names. What do you think? Best Regards, Rakan

Re: ANN: Django website redesign launched

On Wed, Dec 17, 2014, Torsten Bronger wrote: >> 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? Peopl

Re: Bypassing 1.7+ migrations

On Tuesday, December 16, 2014 1:49:53 PM UTC+1, Andrew Godwin wrote: > > > Also bear in mind that, by doing your own schema management for the > contrib apps, you're kind of implicitly forking the schema; Django 1.8 will > ship with some migrations for these apps, and you're going to have to ma

Re: ANN: Django website redesign launched

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 a

Re: ANN: Django website redesign launched

Hi Jorge, First off, thank you for your feedback, it's very much appreciated. Regarding your question about Trac, the differences in UI that you list are definitely not intended. Ola Sitarska and me did some work to try and adapt the new design to Trac but it's proven to be difficult. Coul

Re: ANN: Django website redesign launched

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 on

Re: ANN: Django website redesign launched

Dear Django community, I would like to congratulate you very much for this. I'm very pleased to see that the work in Django is much better presented to the world, which I think we all agree is an important component of the project. Generally speaking, I like very much the overall look and feel

Re: ANN: Django website redesign launched

On Tue, Dec 16, 2014, Schmitt, Christian wrote: >Somehow I hate it. The website is the worst website I've seen since a long >time. >The contrast is really aweful. >The issue Tracker got unusable due to the colors that aren't focused on >readability. > >Overall it looks like a mess, just to have a

Re: annotate() and generic relations

On Wed, 2014-12-17 at 09:21 +0200, Anssi Kääriäinen wrote: > I investigated this a bit, and the problem is deeper in generic > relations handling. Even filtering on generic relations use the related > field's value, not the related model's primary key value. We should fix > that, too. > > Luckily

Re: ANN: Django website redesign launched

So, I agree sorta with what I think Christian was stating.I don't particularly care for the color scheme. I'm making a slightly modified markup in GIMP. I'm just wondering if there's a reason the original color scheme was abandoned? I only ask because I actually really liked it. Was there a driving