Re: Search Refiner - Can anyone skype and help me?

Hi, This group is for development of django itself/internals. for your problem please post to django-users mailing list. Regards, Asif On Tuesday, January 26, 2016 at 8:43:27 AM UTC+6, eZ_Harry wrote: > > Hello, > > I have stuck making a search refiner for my website and have been stuck >

Search Refiner - Can anyone skype and help me?

Hello, I have stuck making a search refiner for my website and have been stuck for so long now, I am really just in need of some direction and to get someone to tell me roughly how I should be going about it. If anyone could help me that would be greatly appreciated. Just message me and ill

Re: Improving MSSQL and Azure SQL support on Django

is there any update about the progress of this? -- Fábio C. Barrionuevo da Luz Palmas - Tocantins - Brasil - América do Sul Em terça-feira, 13 de outubro de 2015 18:12:55 UTC-3, Tim Graham escreveu: > > If anyone is interested in listening in on the meetings with Microsoft > engineers

Re: deadlock risk from using cache a load time

I got a patch from the django-cms folks that moves template loading into their AppConfig.ready() routine, but the problem persists. The last few lines of apps.populate are: self.models_ready = True for app_config in self.get_app_configs():

Re: two levels of m2m relationship & update values

Please write to django-users as this mailing list is for the development of Django itself. On Monday, January 25, 2016 at 6:07:41 PM UTC-5, Slomski wrote: > > Hi, > > I am trying to create a django app as follow: > > a Block with unique name can have few Flats. Flat name in each Block is >

two levels of m2m relationship & update values

Hi, I am trying to create a django app as follow: a Block with unique name can have few Flats. Flat name in each Block is unique but flat names can be the same in different Blocks and Flat name needs to be chosen from the range {Paprika, Water, Banana}. each Flat can have three rooms and room

model formsets and recently stale data

We saw an unexpected result working with model formsets and recently stale data. Consider a simple Book model with soft deletion. ``` class Book(models.Model): name = models.CharField(max_length=100) deleted = models.BooleanField(default=False) ``` We have one book ``` book =

Re: test --keepdb and explicitly migrating the test database

Hi again, On Monday 25 January 2016 18:33:15 charettes wrote: > FWIW I've been working around this limitation by adding a suffix > to my `DATABASES['alias']['TEST']['NAME']` setting if the project > VCS branch is not the default one. > What Marc said. That's nice, but doesn't solve my problem.

Re: test --keepdb and explicitly migrating the test database

Simon - that's great but still means ending up having to create a new test DB every time you switch to a new branch, something you do a lot if you're part of the QA process! +100 to this feature, it would be super useful for me, especially when working with long running feature branches with

Re: 'noescape' filter for django template

And even then, |safe is exactly the same as |noescape On Monday, January 25, 2016 at 4:33:01 PM UTC+1, Tim Graham wrote: > > Is there some reason you cannot mark the string safe in Python code using > one of the following methods? I think that's where escaping logic belongs. > > >

Re: test --keepdb and explicitly migrating the test database

FWIW I've been working around this limitation by adding a suffix to my `DATABASES['alias']['TEST']['NAME']` setting if the project VCS branch is not the default one. e.g. for Git import subprocess branch = subprocess.check_output(['git', 'rev-parse', '--abbrev-ref', 'HEAD']).strip() if branch

Re: add prefered/default protocol in the sites framework #26079

In using Marten Kenbeek's URL dispatch rewrite branch, I've found that using the pattern of defining some site configuration in your settings is the way to go: it more easily allows you to have URL patterns on multiple domain/scheme combinations. I use a dict similar to what Tim has shown, and

Re: add prefered/default protocol in the sites framework #26079

On 01/25/2016 09:01 AM, Tim Graham wrote: > Oh, looks like django-hosts also has this problem. It looks like in some > cases the URLs will be correct (due to the PARENT_HOST setting, I think, > which is 'djangoproject.dev:8000' in the djangoproject.com dev > settings), but if you are browsing a

Re: add prefered/default protocol in the sites framework #26079

Oh, looks like django-hosts also has this problem. It looks like in some cases the URLs will be correct (due to the PARENT_HOST setting, I think, which is 'djangoproject.dev:8000' in the djangoproject.com dev settings), but if you are browsing a different host (e.g. the docs site), then those

Re: 'noescape' filter for django template

Is there some reason you cannot mark the string safe in Python code using one of the following methods? I think that's where escaping logic belongs. https://docs.djangoproject.com/en/stable/ref/utils/#django.utils.html.format_html

'noescape' filter for django template

Hi All, I want to add a new filter names 'noescape' to django template. After that, {{ |noescape }} will output the context variable without auto escape. It will be more convenient than {% autoescape off %}{{ }} {% endautoescape %} Thanks and regards, Hans -- You received this message

Re: add prefered/default protocol in the sites framework #26079

> On 25 janv. 2016, at 14:19, Tim Graham wrote: > > I believe it's a common use case to import a copy of a production database > and examine it locally -- that's what I meant about portability. I’m not convinced by this argument because the data for the Site model will be

Re: add prefered/default protocol in the sites framework #26079

I believe it's a common use case to import a copy of a production database and examine it locally -- that's what I meant about portability. I'm not aware of any Django usage that involves serving protocols other than http(s). Is this a case you've come across? On Monday, January 25, 2016 at

Re: test --keepdb and explicitly migrating the test database

I've made similar mistakes (corrupting the test database) while working on djangoproject.com. For that project, test database creation is quick enough that I just drop "--keepdb" and start fresh. I think this will usually be the simplest option for most users, but I don't see a reason not to

test --keepdb and explicitly migrating the test database

Hi, While developing against a large project with many migrations, I found 1.8's --keepdb option to the test command a life-saver, changing the time to run the projects test from 7-8 minutes to under one (not even counting the tests themselves). But it is still missing something. If I develop

Re: add prefered/default protocol in the sites framework #26079

1. it's not necessarily about SSL, it can be for any protocol but SITE dependent. 2. and for the dev/prod , your data will be different anyway so you put the preferred protocol accordingly to your setup. 3. it's only for generating full URLs, not for internal links (ex:

Re: add prefered/default protocol in the sites framework #26079

Hi, I think the same in the case of: > >1. It would make data less portable between development (where SSL is >often not in use) and production. > > So maybe a settings option could work. El miércoles, 13 de enero de 2016, 14:21:14 (UTC+1), Eric Rouleau escribió: > > Hi > > I've

Re: add prefered/default protocol in the sites framework #26079

since no feedback has been given yet, I will add that the change is just an addition (new feature) meaning there is no breaking of code , it just provides a way to define a default protocol for a given SITE, and will ultimately default to http when none is specified -- You received this