Re: Initial value is not displayed on forms.DateField with widget input type="date" when localized

You can read https://code.djangoproject.com/ticket/33113 for some details on this issue. On Wednesday, October 27, 2021 at 5:07:00 AM UTC-4 binoy...@gmail.com wrote: > Hi > I have a form field forms.DateField and widget as follows > > class CustomDateInput(forms.DateInput): > input_type =

Re: Oracle 12.0.1 admin not working with django 3+

I'm not sure if this is the cause of your issue but Django 3.0 officially supports Oracle 12.2 and higher: https://docs.djangoproject.com/en/3.0/ref/databases/#oracle-notes On Tuesday, June 23, 2020 at 10:35:24 PM UTC-4, ashish goyal wrote: > > Ho All, > > Have created lot of stuff in app,

Re: cx_Oracle.DatabaseError: ORA-00910: specified length too long for its datatype

The relevant migration is: https://github.com/divio/django-cms/blob/d6cabc49f016dd9a16f91440da9fb6790d27c2ae/cms/migrations/0008_auto_20150208_2149.py It increases the length of a CharField to 2048 characters which seems to be longer than Oracle supports. As far as I know, Django CMS isn't

Re: Best way to get a PR Review?

Hi Matt, Your patch is in the "Patches needing review" queue (along with 33 others issues) at https://dashboard.djangoproject.com/. Reviewing patches isn't a task limited to members of the Django team. Anyone from the community is welcome to review patches and mark the ticket as "patch needs

Re: Possible Django bug I am considering raising

You can try to find the commit that introduced the issue: https://docs.djangoproject.com/en/dev/internals/contributing/triaging-tickets/#bisecting-a-regression On Thursday, June 4, 2020 at 11:25:09 AM UTC-4, OwlHoot wrote: > > Hi all > > I believe the issue I have enquired about on the following

Re: GeoDjango with MySQL8

Hi, you might have better luck getting an answer on the GeoDjango mailing list: https://groups.google.com/forum/#!forum/geodjango On Monday, May 25, 2020 at 11:06:26 AM UTC-4, Utkarsh Bansal wrote: > > I am facing problems while trying to use GeoDjango (v2.2) with MySQL 8.0.19 > > I created a

Re: Mobile friendly admin

What version of Django are you using? https://github.com/elky/django-flat-responsive is an extension for the Django admin that makes the interface mobile-friendly. It's part of Django 2.0 and later. On Wednesday, April 1, 2020 at 4:02:57 AM UTC-4, guettli wrote: > > I know there a several

Re: Is this mistake in utils.functional?

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

Re: CockroachDB & Django

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

Re: Fixtures for django auth groups

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

Re: no such table: main.auth_user__old

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

Re: Upgrading Django from 1.11 to 2.2

The advice is to go from one the major version to the next. Don't try to skip versions. -- 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

Re: Upgrading Django from 1.11 to 2.2

Consider the "Upgrading Django to a newer version" guide. https://docs.djangoproject.com/en/stable/howto/upgrade-version/ On Friday, March 29, 2019 at 4:52:10 AM UTC-4, Uri Even-Chen wrote: > > Hi, > > I want to upgrade Django from 1.11 to 2.2. Do I have to upgrade first to > 2.0 and then to

Re: Django ForeignKey field name “check” raises SystemCheckError

I believe the warning is incorrect. See https://code.djangoproject.com/ticket/23615 for the disucssion. On Wednesday, February 20, 2019 at 12:25:46 PM UTC-5, Eric Palmitesta wrote: > > The Django docs ( > https://docs.djangoproject.com/en/1.11/topics/db/models/#field-name-restrictions) > >

Re: Messages rejected?

possible somehow, do you know? > > Thanks. > > On Thu, 14 Feb 2019 at 02:38, Tim Graham > > wrote: > >> Messages from first time posters go through a moderation queue. >> >> On Tuesday, February 12, 2019 at 9:56:26 PM UTC-5, Anton Melser wrote: >>>

Re: AuthenticationForm 'data' keyword argument?

>From the docs for AuthenticationForm: "Takes request as its first positional argument, which is stored on the form instance for use by sub-classes." https://docs.djangoproject.com/en/dev/topics/auth/default/#django.contrib.auth.forms.AuthenticationForm On Thursday, February 14, 2019 at

Re: Messages rejected?

Messages from first time posters go through a moderation queue. On Tuesday, February 12, 2019 at 9:56:26 PM UTC-5, Anton Melser wrote: > > Hi, > I asked a question last night with a Google for business account and had > the message bounce - is that normal? > > Google also hasn't kept the

Re: 2.2a1: django-admin migrate throws UnicodeEncodeError

This was reported as crashing on Windows in https://code.djangoproject.com/ticket/30184 so we might revert the change. On Friday, February 1, 2019 at 3:45:39 PM UTC-5, Tim Graham wrote: > > I think your shell/terminal isn't configured for Unicode. Take a look here > for some ideas

Re: get_expiry_age does not use expire_date column.

Hi Shen, I haven't looked into this much but https://code.djangoproject.com/ticket/19201 could be related. Feel free to offer a patch to improve the situation. On Monday, February 4, 2019 at 12:59:16 PM UTC-5, Shen Li wrote: > > Hi community, > > I find it strange that in the DB session

Re: Model's verbose_name not getting used as field label when specifying a field type in ModelForm

When you add a form field like that, it removes inheritance of field attributes like verbose_name from the model. Instead, you could override Form.__init__() and set the widget similar to what's described at https://docs.djangoproject.com/en/stable/ref/forms/widgets/ "Or if the field isn’t

Re: inspectdb traceback

" delivered to me, it > was not indentionally installed. how to get a "new" version via pip? > > On Friday, February 1, 2019 at 3:45:15 PM UTC+1, Tim Graham wrote: >> >> You must use an older version of mysqlclient for such an old (and >> unsupported) vers

Re: 2.2a1: django-admin migrate throws UnicodeEncodeError

I think your shell/terminal isn't configured for Unicode. Take a look here for some ideas about how to solve it: https://stackoverflow.com/questions/9942594/unicodeencodeerror-ascii-codec-cant-encode-character-u-xa0-in-position-20/39293287 On Friday, February 1, 2019 at 1:49:07 PM UTC-5,

Re: Migration question: why causes this change a non-empty migration?

AutoField has AUTO_INCREMENT while IntegerField does not so if the migration is working correctly, I think its purpose is to drop the AUTO_INCREMENT. I'm reluctant to continue investigation as you're using an old version of Django and many bugs have been fixed since then. If you can reproduce

Re: inspectdb traceback

You must use an older version of mysqlclient for such an old (and unsupported) version of Django. On Friday, February 1, 2019 at 7:50:11 AM UTC-5, christia...@itsv.at wrote: > > > while trying to build an app around an existing database, inspectdb bails > out on me. the server is running fine

Re: Questions about MySQL notes in Django docs

Yes, Django supports MySQL 8. If you google "django mysql 8" the second result is https://code.djangoproject.com/ticket/29451. Based on the commits there, it looks like Django 2.0.7 and above received the fixes. On Wednesday, January 23, 2019 at 5:10:18 AM UTC-5, Carsten Fuchs wrote: > > Dear

Django security releases issued: 2.1.5, 2.0.10, and 1.11.18

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

Re: Form no longer validates after upgrading django from 2.0.5 to 2.1. Should I report a bug?

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

Re: Update of issue (Trac) rejected (SPAM ...)

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

Re: Strange intermittent UUID bug

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

Re: makemigrations makes migration even if no changes in model

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

Re: Prepopulate blog in b.entry_set.all()[i].blog ?

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: > >

Re: Can't Upload Image Field With Django 2.1

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

Re: Can't Upload Image Field With Django 2.1

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. >

Re: Can't Upload Image Field With Django 2.1

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

Re: Can't Upload Image Field With Django 2.1

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

Re: GEOSContextHandle leak probably due to thread local storage destructing order

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

Re: Allow a limit_choices_to callable to accept the current model instances object

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

Release 1.11.16 on hold?

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

Re: Using Subdomains in Version 2.1.7

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

Re: Help.... Django : Change Backend as mysql and create sample example using django ORM

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: >>&g

Re: Help.... Django : Change Backend as mysql and create sample example using django ORM

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: > >

Re: Check file input extension

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 >

Re: Upgrading app with settings-dependent migrations

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

Re: Concerning CVE-2018-14574: is there a open redirect possibility in CommonMiddleware of version 1.9.5

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

Re: 3719: 'utf8' is currently an alias for the character set UTF8MB3, which will be replaced by UTF8MB4 - When using MySQL sakila and world DB examples

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

Re: GEOSGeometry function dies with error pure virtual method called message

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 code >

Re: GEOSGeometry function dies with error pure virtual method called message

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:- > >

Re: Oracle with Django

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

Django 2.1 released

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

Django security releases issued: 1.11.15 and 2.0.8

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

Re: Django2.0.7 generate SQL query function is wrong(REGEXP_LIKE).

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

Re: python manage.py inspectdb makes all fields with a default value blank=True, null=True

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

Re: authenticate issues with custom backends in 2.1rc1

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

Django 2.1 release candidate 1 released

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

Django 2.1 beta 1 released

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:

Django 2.1 alpha 1 released

We've made the first release on the way to Django's next major release, Django 2.1! With about two and a half months until the final release (scheduled for August 1), we'll need timely testing from the community to ensure an on time, stable release. Check out the blog post:

Re: @mark_safe decorator and filters & tags

Seems to be a regression: https://code.djangoproject.com/ticket/29400 On Tuesday, May 8, 2018 at 4:45:14 PM UTC-4, Torsten Bronger wrote: > > Hallöchen! > > Up to Django 1.11, I had the following pattern frequently in my > code: > > @register.filter > @mark_safe > def

Django bugfix releases: 2.0.5 and 1.11.13

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2018/may/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

Re: perhap buys in autodetector.py

When you say, "remove all previous migration codes" -- you mean you removed all the migration files such as 0001_initial.py? In that case, make sure you don't remove the __init__.py file, otherwise you must use "makemigrations app_name". On Thursday, April 19, 2018 at 7:18:02 AM UTC-4,

Re: Proxy User and AUTH_USER_MODEL: TypeError: MyUser cannot proxy the swapped model 'myapp.MyUser'.

The behavior seems expected. https://docs.djangoproject.com/en/dev/topics/auth/customizing/#custom-users-and-proxy-models It looks like if you use a proxy model, then you should import it where needed rather than use AUTH_USER_MODEL. On Saturday, April 14, 2018 at 6:34:59 PM UTC-4, Nicolas

Re: First Django Patch: django.contrib.auth 'Specifying a namespace in include() without providing an app_name '

It can't be changed due to backwards compatibility. See https://github.com/django/django/pull/9527. On Saturday, April 14, 2018 at 12:29:01 PM UTC-4, jazu...@gmail.com wrote: > > Hi, I've recently sprung a bug that seems to be easily fixable. I would > like to create my first patch on django

Django bugfix releases: 2.0.4 and 1.11.12

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2018/apr/02/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

Re: Updating TimeField in forms/formsets returns value without microseconds

You need to set support_microseconds=True on the widget. https://docs.djangoproject.com/en/stable/ref/forms/widgets/#django.forms.Widget.supports_microseconds On Sunday, March 25, 2018 at 9:03:18 AM UTC-4, Rafał Szymczuk wrote: > > I have problem with updating TimeField in my models - when I want

Re: GROUP BY behavior change in Django 2.0 with annotate/extra

I'd use git bisect to find the commit where the behavior changed in Django. That will likely yield some insight. https://docs.djangoproject.com/en/dev/internals/contributing/triaging-tickets/#bisecting-a-regression On Friday, March 9, 2018 at 5:39:43 PM UTC-5, Michael Soderstrom wrote: > > In a

Django security releases issued: 2.0.3, 1.11.11, and 1.8.19

Today the Django team issued Django 2.0.3, 1.11.11, and 1.8.19 as part of our security process. These releases address two security issues, and we encourage all users to upgrade as soon as possible: https://www.djangoproject.com/weblog/2018/mar/06/security-releases/ As a reminder, we ask that

Re: Disable single instance of a system check warning

There is not, but there's an open ticket for that enhancement. https://code.djangoproject.com/ticket/26472 On Friday, February 9, 2018 at 6:58:08 AM UTC-5, Mattias Linnap wrote: > > Hi djangonauts, > > > System check identified some issues: > > > HINT: ForeignKey(unique=True) is usually better

Re: Django 2.0.2 not work with Jinja 2 (admin side)

The admin doesn't support Jinja2. If you're using Jinja2, you must also have a DjangoTemplates backend defined in your TEMPLATES to use the admin. On Saturday, February 3, 2018 at 7:26:33 PM UTC-5, Николай Инкогнито wrote: > > /admin/ > - raise error > -- You received this message because you

Re: Deprecations not listed within release notes

Correct, that falls under "private API removal". If you clone the Django source code you can use "git log -S custom_sql_for_model" to find the commits that touched something with that name. In this case, you'll find

Re: Impossible to reproduce example in the documentation of Queryset.values()

Confirmed. I opened a bug report: https://code.djangoproject.com/ticket/29032. On Wednesday, January 17, 2018 at 11:37:23 AM UTC-5, Joseph Lucas wrote: > > Hi, > > We were not able to reproduce an example described in Django's > documentation, concerning the value() method of Queryset >

Django bugfix releases: 2.0.1 and 1.11.9

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2018/jan/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

Re: AutocompleteSelect and AutocompleteSelectMultiple admin widgets.

They're used when you use ModelAdmin.autocomplete_fields. https://docs.djangoproject.com/en/dev/ref/contrib/admin/#django.contrib.admin.ModelAdmin.autocomplete_fields On Monday, November 27, 2017 at 3:27:30 AM UTC-5, Daniel Gola wrote: > > Hello, > > Where I can find more detailed information

Re: AttributeError: 'TemplateResponse' object has no attribute '_reason_phrase'

I tried a Google search for the last line of the error message and came to https://code.djangoproject.com/ticket/25964. Conclusion: try clearing your cache. On Wednesday, November 22, 2017 at 3:29:42 AM UTC-5, Web Architect wrote: > > Hi, > > We recently migrated from Django 1.8 to Django

Django 2.0 release candidate 1 released

We've made the final (hopefully) release on the way to Django's next major release, Django 2.0! Check out the blog post: https://www.djangoproject.com/weblog/2017/nov/15/django-20-release-candidate-1-released/ -- You received this message because you are subscribed to the Google Groups "Django

Re: Find a typo in the documentation.

I pushed a fix for that, thanks! On Tuesday, November 7, 2017 at 3:42:14 AM UTC-5, 王祥 wrote: > > In this site > , > the code > Book.objects.all().aggregate(price_diff=Max('price', output_field= > FloatField()) -

Django bugfix release: 1.11.7

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2017/nov/01/bugfix-release/ -- 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

Re: QuerySet.extra and ticket #28756

t.identifier for q in quali_results] > fields = '"'+'","'.join(str(field) for field in field_list)+'"' > field_sql = "FIELD(`identifier`,"+fields+")" > quali_results = quali_results.extra(select={'field_sql' : field_sql}, > order_by=['fi

Re: TypeError: unorderable types: CharField() < CharField()

2to3 can do some simple changes for Python 3 compatibility but it can't do everything. I think you'll spend less time updating your application to a supported version of Django which supports Python 3 than you would adding Python 3 support to Django 1.4. On Wednesday, October 25, 2017 at

Django 2.0 beta 1 released

We've made the second release on the way to Django's next major release, Django 2.0! 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:

Re: How do I request a new feature in 1.11.x?

11 October 2017 at 10:03, Tim Graham <timog...@gmail.com > > wrote: > >> No, Django 1.11.x won't receive new features. The supported versions >> policy is the same for that release series as for other releases. >> >> >> https://docs.django

Re: How do I request a new feature in 1.11.x?

No, Django 1.11.x won't receive new features. The supported versions policy is the same for that release series as for other releases. https://docs.djangoproject.com/en/dev/internals/release-process/#supported-versions On Wednesday, October 11, 2017 at 12:01:06 AM UTC-4, Chris Beck wrote: > >

Django bugfix release: 1.11.6

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2017/oct/05/bugfix-release/ -- 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

Re: Auth Password Change template not working

I'd temporarily remove the built-in template that's being loaded so that TemplateDoesNotExist is raised. The debug page will show the locations that Django searched for the template. On Wednesday, September 27, 2017 at 7:10:54 AM UTC-4, naitik gala wrote: > > Hi all, > > I am trying to add my

Re: How safe is it to use sys.exit() in custom commands

I don't know of any reason why that would be unsafe. You'll find several uses of sys.exit() in Django's built in commands located in django/core/management/commands. On Friday, September 29, 2017 at 5:13:50 PM UTC-4, phep wrote: > > Hi, > > Executive summary : everything's in the subject line.

Re: Bug to set session in Django Test?

There's a test in Django's test suite for this: https://github.com/django/django/blob/fd866c25d1665b73aff0d8312c414ae6f69812a3/tests/test_client_regress/tests.py#L1009-L1015 I guess you'll need to figure out how your project differs from that. On Saturday, September 30, 2017 at 6:30:25 AM

Re: How to clean a form which receives multiple files

There's a pull request to allow FileField(multiple=True): https://github.com/django/django/pull/9011 On Monday, September 25, 2017 at 4:19:24 AM UTC-4, guettli wrote: > > thank you very much for your Feedback! > > Am Freitag, 22. September 2017 18:24:23 UTC+2 schrieb mike: >> >> I do it this way

Django 2.0 alpha 1 released

We've made the first release on the way to Django's next major release, Django 2.0! With just a little over two months until the final release (scheduled for December 1), we'll need timely testing from the community to ensure an on time, stable release. Check out the blog post:

Django security releases issued: 1.11.5 and 1.10.8

Today the Django team issued 1.11.5 and 1.10.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/2017/sep/05/security-releases/ As a reminder, we ask that potential security

Re: JavaScriptCatalog: it's big or not?

Quoting Claude from https://code.djangoproject.com/ticket/28434#comment:2, "There is a ​specific test for that in the Django test suite. It may be the test is missing something, but you should explore that

Re: Template Rendering Django 1.11

ifferent is really unacceptable right now. > > > > *From:* Tim Graham [mailto:timogra...@gmail.com] > *Sent:* Saturday, August 5, 2017 8:25 PM > *To:* Django users > *Cc:* Matthew Pava > *Subject:* Re: Template Rendering Django 1.11 > > > > Are you using t

Re: AttributeError: 'module' object has no attribute 'SubfieldBase'

>From https://bitbucket.org/schinckel/django-timedelta-field: "If you are using Django 1.8 or greater (and you really _should_ be), then you should use the included DurationField() instead of this. This field does not work with Django 1.10, and will probably not be updated to fix the issue(s).

Re: Migration of auth.user to custom user

Some steps are outlined in https://code.djangoproject.com/ticket/25313. On Friday, August 4, 2017 at 3:37:08 AM UTC-4, Mike Dewhirst wrote: > > I have read widely (including the docs) and been daunted by the notion > of coverting auth.user into a custom user. I have data and wonder if > there

Re: Template Rendering Django 1.11

Are you using the cached template loader? It may mitigate the problem to some extent. https://docs.djangoproject.com/en/1.11/ref/templates/api/#django.template.loaders.cached.Loader As of Django 1.11, it's enabled if DEBUG is False and OPTIONS['loaders']

Re: Turn off migrations completely in Django 1.7

Perhaps giving some actionable, constructive feedback would be more useful. On Tuesday, August 1, 2017 at 6:50:47 PM UTC-4, Robert F. wrote: > > I know this is an old topic but I completely agree with Frank. Nothing > gives me more headaches and makes me want to move off Django more than >

Django bugfix release: 1.11.4

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2017/aug/01/bugfix-release/ -- 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

Re: ModelForm with field subset saving all fields

It might be worth considering. Here's a quick patch: diff --git a/django/forms/models.py b/django/forms/models.py index ffa8982..bd5d108 100644 --- a/django/forms/models.py +++ b/django/forms/models.py @@ -454,7 +454,8 @@ class BaseModelForm(BaseForm): ) if commit:

Re: TypeError: __init__() takes 2 positional arguments but 3 were given (django-material)

Please give the exception traceback. On Tuesday, July 25, 2017 at 3:35:41 PM UTC-4, Elias Coutinho wrote: > > Hello guys! > > I'm trying to recreate a form with Inline using django and django-stuff. I > already got it once, but this is not being easy! > > I want to create a form that can

Re: Django Forms HorizontalRadioSelect Renderer not working.

Replace renderer=HorizontalRadioRenderer with attrs={'class': 'inline'} and then style radio elements using CSS. contrib.admin uses this approach. Here's the CSS:

Re: upgrading django 1.11 warning list

Yes, it's safe to add that to migrations. https://docs.djangoproject.com/en/dev/releases/1.9/#foreignkey-and-onetoonefield-on-delete-argument On Tuesday, July 25, 2017 at 8:55:24 AM UTC-4, pablochud wrote: > > Hi! > It showed me warning related to 'on_delete' as required arg for ForeignKey > in

Re: How to discover which postgres vesion is in use (on 1.11)?

You can use: >>> from django.db import connection >>> connection.pg_version 90507 On Wednesday, July 19, 2017 at 6:15:29 AM UTC-4, HM wrote: > > When https://code.djangoproject.com/ticket/18332 lands (No generic way > to get database backend version) this will be trivial but I need a >

Re: Redirect_field_name in LoginView

Hi, did you find the documentation for LoginView? https://docs.djangoproject.com/en/dev/topics/auth/default/#django.contrib.auth.views.LoginView On Friday, July 14, 2017 at 7:13:29 AM UTC-4, Polina Ia wrote: > > Hello, > can someone explain me the setting of 'redirect_field_name' in LoginView?

  1   2   3   4   5   6   >