Yes, there's a mention of that on the password_reset() view docs:
https://docs.djangoproject.com/en/stable/topics/auth/default/#django.contrib.auth.views.password_reset
Feel free to submit some docs clarifications as a pull request if you'd
like.
On Tuesday, March 15, 2016 at 7:32:41 PM UTC-4,
Are you using the same settings file in both cases? I think this might
happen if you don't have django.contrib.postgres in INSTALLED_APPS which
would mean register_hstore_handler() isn't called.
On Tuesday, March 22, 2016 at 1:15:28 PM UTC-4, Andrew Grossman wrote:
>
> I'm working with a model t
We recommend going one major version at a time:
https://docs.djangoproject.com/en/stable/howto/upgrade-version/
On Tuesday, March 29, 2016 at 5:19:59 PM UTC-4, Roger Dunn wrote:
>
> I've inherited a moderately large project written 2 years ago using Django
> 1.4, and wondering if it is worth cre
Looks reasonable, although I am not entirely clear what role charset has in
a JsonResponse. See https://code.djangoproject.com/ticket/23949.
On Thursday, March 31, 2016 at 6:15:53 AM UTC-4, Daniel Blasco wrote:
>
> Hi,
>
> I'm testing the REST API of my application and I found an error that I
>
Some attributes such as IntegerField.min_value need to be customized on the
field rather than the widget. This will ensure that validation is also done
server-side. (see
https://github.com/django/django/blob/f3595b25496691966d4ff858a3b395735ad85a6e/django/forms/fields.py#L278-L285
for example)
See https://github.com/django/djangoproject.com/issues/621 for some recent
improvements we tried to fix this. Perhaps more needs to be done but things
look better for me since that change.
On Thursday, March 31, 2016 at 1:40:26 PM UTC-4, Piotr Gnus wrote:
>
> Hello,
>
> when translations were im
Details are available on the Django project weblog:
https://www.djangoproject.com/weblog/2016/apr/01/bugfix-releases/
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an emai
Nothing outside of the way that Django normally determines the order in
which to run migrations:
https://docs.djangoproject.com/en/stable/howto/writing-migrations/#controlling-the-order-of-migrations
On Friday, April 1, 2016 at 11:45:42 AM UTC-4, kasmi sidi wrote:
>
> is there a way to tell djan
Difficult for me to say for sure without having a sample project to debug.
Do you know if you have any module level queries in your project? Those are
generally to be avoided and may cause problems like this. See
https://groups.google.com/d/topic/django-developers/7JwWatLfP44/discussion
for som
Also, your models might reference a setting whose value differs between
development and production. This probably won't cause any problems but will
trip up the migrations autodetector into thinking that a migration needs to
be made.
https://code.djangoproject.com/ticket/24648
On Saturday, Apri
It looks like your migration history is corrupted somehow (migrations 10-22
are applied but not their dependency 0001). You might need to manually add
a row to the django_migrations table to reflect the fact that 0001 is
applied. If you can provide steps that reproduce how you got to such a bad
You want `from __future__ import unicode_literals`:
https://docs.djangoproject.com/en/dev/ref/unicode/#general-string-handling
On Thursday, April 14, 2016 at 6:27:07 PM UTC-4, Fred Stluka wrote:
>
> Django users,
>
> In my Django app, I want to allow users to enter Unicode
> strings. But if the
t; Fred Stluka -- mailt...@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 4/14/16 10:05 PM, Tim Graham wrote:
We've made the second release on the way to Django's next major
release, Django 2.1! With a month and a half until the final release,
we'll need timely testing from the community to ensure a stable
release. Check out the blog post:
https://www.djangoproject.com/weblog/2018/jun/18/django-21-beta-1-
We've made the final (hopefully) release on the way to Django's next
major release, Django 2.1! Check out the blog post:
https://www.djangoproject.com/weblog/2018/jul/18/django-21-rc1/
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscri
Do you have deprecation warnings with Django 2.0.x?
https://docs.djangoproject.com/en/dev/howto/upgrade-version/#resolving-deprecation-warnings
>From the 2.1 release notes: "The authenticate() method of authentication
backends requires request as the first positional argument."
>From the 1.11 r
For future reference, creating a bug report is sufficient. No need to post
to django-developers.
I'll post my analysis from the ticket below.
https://code.djangoproject.com/ticket/29583#comment:1
I think you made a mistake in your analysis. In the FieldInfo
initialization, line[6] (not inf
This is a regression that will be fixed in Django 2.0.8:
https://code.djangoproject.com/ticket/29544
On Thursday, July 26, 2018 at 6:40:37 AM UTC-4, Jason wrote:
>
> what's the django orm code that generates that query?
>
> On Thursday, July 26, 2018 at 12:12:06 AM UTC-4, Hiroyuki Yamashita wrote
Today the Django team issued 1.11.15 and 2.0.8 as part of our security
process. These releases address a security issue, and we encourage all
users to upgrade as soon as possible:
https://www.djangoproject.com/weblog/2018/aug/01/security-releases/
As a reminder, we ask that potential security iss
Django 2.1 is now available:
https://www.djangoproject.com/weblog/2018/aug/01/django-21-released/
With the release of Django 2.1, Django 2.0 has reached the end of
mainstream support. The final minor bug fix release (which is also a
security release), 2.0.8, was issued today. Django 2.0 will recei
What's the error? Did you read the Oracle notes?
https://docs.djangoproject.com/en/stable/ref/databases/#oracle-notes
On Wednesday, August 1, 2018 at 4:04:53 PM UTC-4, Md. Razibul Hasan Mithu
wrote:
>
> I didn't find any way to connect oracle 11g with django. It still gives me
> error
>
> On
I'm not sure what you mean by "On debugging". Is that the complete code
snippet to reproduce the issue? I don't see a crash on my system. Which
Django version?
On Thursday, August 2, 2018 at 8:29:51 AM UTC-4, Saurabh Khanduja wrote:
>
> Hi,
> This is the piece of code I am working with:-
>
> po
g in transform
> function in file
> ~/anaconda3/envs/py35/lib/python3.5/site-packages/django/contrib/gis/geos/geometry.py
>
> On Thursday, 2 August 2018 16:28:43 UTC+2, Tim Graham wrote:
>>
>> I'm not sure what you mean by "On debugging". Is that the complete c
It looks like some code is promoting MySQL's warnings to exceptions.
django.db.backends.mysql had that behavior before Django 1.8:
https://code.djangoproject.com/changeset/5bcd292098b4de7bb03ef778e24d9e2f433d0dae/
For anyone reporting this, are you using django.db.backends.mysql or some
other da
I didn't confirm it but according to the comments at the bottom of
https://github.com/django/django/commit/a656a681272f8f3734b6eb38e9a88aa0d91806f1,
Django 1.9 and later are affected.
On Thursday, August 23, 2018 at 7:30:51 AM UTC-4, Christophe Dupouy wrote:
>
> I understand that per your suppo
I think that https://code.djangoproject.com/ticket/24648 describes your
issue.
On Thursday, August 23, 2018 at 7:30:33 AM UTC-4, Jan Musílek wrote:
>
> Hi!
>
> I have a problem with migrations workflow for which I couldn't find an
> answer anywhere else.
>
> Suppose, that I have an application
You can use FileExtensionValidator:
https://docs.djangoproject.com/en/stable/ref/validators/#django.core.validators.FileExtensionValidator
On Tuesday, August 28, 2018 at 7:35:39 AM UTC-4, René L. Hechavarría wrote:
>
> Hi everyone, i need check file input format in forms.py, someone have any
> ex
What version of Django, MySQL, and mysqlclient are you using?
On Tuesday, August 28, 2018 at 2:00:52 AM UTC-4, Sonali Vighne wrote:
>
> I will paste full error and stack trace here.
>
> This is occurred when I am giving “python manage.py migrate” command
>
>
>
> Operations to perform:
>
> Appl
qlclient - mysqlclient 1.3.12
>
> On Wednesday, August 29, 2018 at 6:24:05 PM UTC+5:30, Tim Graham wrote:
>>
>> What version of Django, MySQL, and mysqlclient are you using?
>>
>> On Tuesday, August 28, 2018 at 2:00:52 AM UTC-4, Sonali Vighne wrote:
>>>
>
Starting in Django 2.0, "The django.core.urlresolvers module is removed in
favor of its new location, django.urls."
Use from django.urls import reverse as simple_reverse
On Wednesday, August 29, 2018 at 9:56:09 AM UTC-4, Abednego Ng'ang'a wrote:
>
> I've followed the procedure of installing subd
We'll release it October 1.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to djang
There's a ticket with that feature request:
https://code.djangoproject.com/ticket/25306
On Tuesday, September 25, 2018 at 6:25:38 PM UTC-4, Ochui Princewill wrote:
>
> Hello,
>
> Am current working on a project and i want to filter the content of a
> ForeignkeyField base on the current model ob
Yes, if you can demonstrate that Django is at fault, you may create a
ticket.
If you're unsure, you might have better luck on the
https://groups.google.com/forum/#!forum/geodjango mailing list.
On Thursday, October 18, 2018 at 9:08:10 PM UTC-4, Yong Li wrote:
>
> I have seen consistent GEOSCont
It would be helpful to see the complete traceback. What you provided
doesn't show where the exception originates.
On Tuesday, October 30, 2018 at 10:38:38 PM UTC-4, Pacôme Avahouin wrote:
>
> Hello guys,
>
> I'm trying to upload user avatar (ImageField type) with my own custom user
> model foll
It looks like the width_field option on the model field isn't a string.
On Wednesday, October 31, 2018 at 10:28:42 AM UTC-4, Pacôme Avahouin wrote:
>
> Hello Tim,
>
> Thanks for answering.
>
> Here is the complete traceback.
> By the way when i commented out the 'upload_file' function still i'm
>
height_field and width_field should be strings. What's the error and what
does your model fields look like?
On Wednesday, October 31, 2018 at 10:53:53 AM UTC-4, Pacôme Avahouin wrote:
>
> Tim you just saved me right now:) I have spent the all night trying to
> figure it out.
> Thanks a lot.
> No
You've misunderstood the purpose of height_field and width_field. Please
read the documentation:
https://docs.djangoproject.com/en/dev/ref/models/fields/#django.db.models.ImageField.height_field
You need to use a third-party app to do image resizing. Check out
https://djangopackages.org/grids/g
It seems to be a bug as reported in
https://code.djangoproject.com/ticket/29908. The ForeignKey must use
to_field to reproduce the problem.
On Saturday, October 20, 2018 at 4:38:51 AM UTC-4, Carsten Fuchs wrote:
>
> Can anyone help please?
>
> Am 2018-10-11 um 16:58 schrieb Carsten Fuchs:
> >
I think you'll need to provide a sample project that reproduces the
problem. I tried with the models you gave (and removed references to the
models that you didn't provide) but can't reproduce.
On Friday, November 9, 2018 at 6:51:49 AM UTC-5, Michał Redmerski wrote:
>
> Hello!
>
> All issues wi
See if
https://groups.google.com/d/msg/django-users/ZGb8ofw1Ux8/TnMdqsj4AgAJ helps.
On Friday, November 23, 2018 at 1:11:21 PM UTC-5, Zach wrote:
>
> You could try modifying to_python with something like this:
>
> import logging
>
>
> def to_python(self, value):
> if value is not None
I marked your comment as "ham" so maybe it'll pass the Bayes filter now.
"Easy pickings" is subjective but I wouldn't consider that issue "easy"
since there's not a clear consensus about how to proceed.
On Wednesday, November 28, 2018 at 5:10:06 AM UTC-5, guettli wrote:
>
> I wanted to update th
I think the behavior changed in
https://github.com/django/django/commit/5fa4f40f45fcdbb7e48489ed3039a314b5c961d0.
The old behavior looks like a bug to me (can you explain why it would be
expected?) and we don't generally document bug fixes in the release notes.
On Monday, December 31, 2018 at 8
Today the Django team issued 2.1.5, 2.0.10, and 1.11.18 as part of our
security process. These releases address a security issue, and we encourage
all users to upgrade as soon as possible:
https://www.djangoproject.com/weblog/2019/jan/04/security-releases/
The issue was publicly reported through
If you're using Django 2.1, try upgrading to the latest Django 2.1.x
(2.1.14 as of this writing). You should always use the latest point release
to get the most recent security and bug fixes.
See
https://stackoverflow.com/questions/53637182/django-no-such-table-main-auth-user-old
On Saturday,
Take a look at https://docs.djangoproject.com/en/stable/howto/initial-data/.
On Tuesday, December 3, 2019 at 10:31:01 AM UTC-5, Arulselvam K wrote:
>
> I want to create fixtures for auth groups to get some preloaded auth
> groups. Kindly educate me on how to create fixtures fixtures for built in
Cockroach Labs engaged me to work on the CockroachDB backend for Django.
django-cockroachdb 2.2 alpha 2 (for Django 2.2.x) and 3.0 alpha 1 (for
Django 3.0.x) are now available. These versions pass much of the Django
test suite and are ready for real world testing.
Be aware that the latest relea
The code is equivalent to:
res = self.func(instance)
instance.__dict__['self.name'] = self.func(instance)
(except that self.func(instance) isn't called twice like it would be in
this version)
On Thursday, February 6, 2020 at 7:39:47 AM UTC-5, Akira Furude wrote:
>
> Currently I'm working on my
501 - 547 of 547 matches
Mail list logo
