On Friday, March 31, 2017 at 10:50:54 AM UTC+3, Todor Velichkov wrote:
>
> @Anssi, thank you for your response.
> I really haven't think about threat safety, but maybe its because in our
> specific usage it's close to impossible to happen.
>
> What do you think about this:
> 1) Put everything into
I'd suggest to use git bisect to find the Django commit where the behavior
changed:
https://docs.djangoproject.com/en/dev/internals/contributing/triaging-tickets/#bisecting-a-regression
On Wednesday, April 5, 2017 at 5:57:03 PM UTC-4, Maximiliano Robaina wrote:
>
> Hi,
>
>
> I'm the maintener of
Hi,
I'm the maintener of django-firebird database backend.
I've an strange behavior (a different result) when reading a value from a
DecimalField between Django 1.7 and Django 1.8 and I'm trying to figured
out where is my mistake.
I've a django project which I update from 1.7 to 1.8.
In this
Hi, this was already wontfixed here:
https://code.djangoproject.com/ticket/3362
with the rationale, "We've decided in the past not to add a new class for
every single response code. You can already pass the status code in when
creating the HttpResponse class, so that can be used in this case."
Sergey, I like the idea. It at least serves as a demonstration of what can
be done with custom fields. The PoC shows it's not too much code either.
Would you be looking to replace the existing FK's to ContentType too, e.g.
in Admin and Auth?
On 5 April 2017 at 06:24, Asif Saifuddin wrote:
> Hi S
Every Django view function MUST return an HttpResponse object, sometimes we
just want to send data to the server and don't want to send data back to the
client , this probably lead Python users want to return None instead, however ,
this is not allowed in Django view function, I found HttpRe
I think people are always going to run into such kind of issues until they
decide to add django-master to their test matrix, so that each dependency
and project should always have the chance to be ready for the next version
of Django "0day". But perhaps I'm missing something.
Best
James
--
You
Not on purpose no -- if it doesn't work with 4.1 that is a bug
On Wednesday, April 5, 2017 at 11:07:13 AM UTC+2, jorr...@gmail.com wrote:
>
> Is the required version of Pillow pinned at 4.0.0? I upgraded to Django
> 1.11 and from Pillow 4.0.0 to 4.1.0 but now Django doesn't start because it
> sa
Is the required version of Pillow pinned at 4.0.0? I upgraded to Django
1.11 and from Pillow 4.0.0 to 4.1.0 but now Django doesn't start because it
says I can't use ImageField without installing Pillow. Downgrading to
Pillow 4.0.0 fixes this.
On Tuesday, April 4, 2017 at 6:09:40 PM UTC+2, Tim
Hello, I would like to use a custom Site model, in a similar way as
implemented for django.contrib.auth.users.
As discussed here https://code.djangoproject.com/ticket/27784 there is also
another ticket and patch for that, but with a different approach.
My pull request: https://github.com/django
Hi Cử Nhữ Văn,
This mailing list is for development of Django itself, rather than support
queries. You may get a better answer on the main mailing list or on #django
on IRC.
You may also find some help about different languages in the docs:
https://docs.djangoproject.com/en/1.10/ref/contrib/postg
Given that you can always do import Value as V, I'm not sure providing an
alias is necessary.
On 3 April 2017 at 12:15, Josh Smeaton wrote:
> I think I proposed V as an alias back when I was writing the patch, but
> the rough consensus at the time was that one letter class names are a bit
> of a
12 matches
Mail list logo
