date:20191126

Re: [Django] #31035: Promote BaseCommand.run_from_argv to a documented method

2019-11-26 Thread Django

#31035: Promote BaseCommand.run_from_argv to a documented method
---+--
 Reporter:  Roman Odaisky  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Carlton Gibson):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 Hi Roman, thanks for the report.

 I don't think this is the way forward here. `run_from_argv()` has more to
 do than just invoke the subcommand here. It's mean to catch any
 `CommandError`s, handle the output forwarding, etc. Override it here, you
 loose all that.

 I'd still point folks to overriding `handle()` as per the docs. In this
 case just accessing `sys.argv` if that's what you need. That way we don't
 need multiple entry points and you can catch errors, raising the expected
 `CommandError` appropriately.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.058f34e33ff0ca6fb136320efa1366ef%40djangoproject.com.

Re: [Django] #30803: Dateparse function should support comma separators for milliseconds according to ISO-8601

2019-11-26 Thread Django

#30803: Dateparse function should support comma separators for milliseconds
according to ISO-8601
-+-
 Reporter:  Ben Wilber   |Owner:  Farhaan Bukhsh
 Type:  New feature  |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_docs:  1 => 0
 * stage:  Accepted => Ready for checkin


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.fd872e00768ca39295f04d22cb88460b%40djangoproject.com.

Re: [Django] #31034: Add a navigation sidebar to the admin

2019-11-26 Thread Django

#31034: Add a navigation sidebar to the admin
---+---
 Reporter:  Tom Carrick|Owner:  Tom Carrick
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+---
Changes (by Carlton Gibson):

 * stage:  Unreviewed => Accepted


Comment:

 OK, thanks. Accepting on the basis of the discussion. 👍

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.aee88750c1022e6702d1247a0ceab849%40djangoproject.com.

Re: [Django] #31027: Prefer DOM object properties over Element.getAttribute() and Element.setAttribute().

2019-11-26 Thread Django

#31027: Prefer DOM object properties over Element.getAttribute() and
Element.setAttribute().
--+
 Reporter:  Jon Dufresne  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.admin |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Mariusz Felisiak ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"cab36618326524b336517c2c5fd62633916818e0" cab36618]:
 {{{
 #!CommitTicketReference repository=""
 revision="cab36618326524b336517c2c5fd62633916818e0"
 Fixed #31027 -- Replaced .getAttribute()/.setAttribute() usage with DOM
 properties.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.75c78bec9d4e8cbcd44cec2b34d1f40a%40djangoproject.com.

Re: [Django] #25012: Migration doesn't seem to detect foreignKey type changes

2019-11-26 Thread Django

#25012: Migration doesn't seem to detect foreignKey type changes
-+
 Reporter:  Hedde van der Heide  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  migrations   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Samuel Bishop):

 * keywords:   => migrations
 * cc: Samuel Bishop (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.64010fdea48a4e732d8ec83f19980992%40djangoproject.com.

Re: [Django] #31018: Update FAQ about NoSQL databases.

2019-11-26 Thread Django

#31018: Update FAQ about NoSQL databases.
--+
 Reporter:  Thomas Güttler|Owner:  felixxm
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  2.2
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Mariusz Felisiak ):

 In [changeset:"3cf70df468d4453fb315cb74db0232ac9a1e89be" 3cf70df]:
 {{{
 #!CommitTicketReference repository=""
 revision="3cf70df468d4453fb315cb74db0232ac9a1e89be"
 [2.2.x] Fixed #31018 -- Removed django-nonrel in NoSQL databases FAQ.

 Backport of a36f7ed6ac5b2529db7e13fd3754290484928b18 from master
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.2069fca853fa4186a324f2b10a7409a6%40djangoproject.com.

Re: [Django] #31018: Update FAQ about NoSQL databases.

2019-11-26 Thread Django

#31018: Update FAQ about NoSQL databases.
--+
 Reporter:  Thomas Güttler|Owner:  felixxm
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  2.2
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Mariusz Felisiak ):

 In [changeset:"1decf29a3e1e1f8455fc09cce6804ae465bd33bb" 1decf29a]:
 {{{
 #!CommitTicketReference repository=""
 revision="1decf29a3e1e1f8455fc09cce6804ae465bd33bb"
 [3.0.x] Fixed #31018 -- Removed django-nonrel in NoSQL databases FAQ.

 Backport of a36f7ed6ac5b2529db7e13fd3754290484928b18 from master
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.3c005ffd960a87ac85bc336f3ab61937%40djangoproject.com.

Re: [Django] #31018: Update FAQ about NoSQL databases.

2019-11-26 Thread Django

#31018: Update FAQ about NoSQL databases.
--+
 Reporter:  Thomas Güttler|Owner:  felixxm
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  2.2
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by GitHub ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"a36f7ed6ac5b2529db7e13fd3754290484928b18" a36f7ed6]:
 {{{
 #!CommitTicketReference repository=""
 revision="a36f7ed6ac5b2529db7e13fd3754290484928b18"
 Fixed #31018 -- Removed django-nonrel in NoSQL databases FAQ.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.80ecdef9fb1537540a98878709dd4a54%40djangoproject.com.

Re: [Django] #31024: firstof template tag documentation incorrectly specifies value testing. (was: firstof template tag documentation incorrectly specifies value testing)

2019-11-26 Thread Django

#31024: firstof template tag documentation incorrectly specifies value testing.
--+
 Reporter:  Keryn Knight  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by felixxm):

 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.940323c36057a63ebf1cdd89d611bd94%40djangoproject.com.

Re: [Django] #31037: Template truncatechars dots missing. (was: Template truncatechars dots missing)

2019-11-26 Thread Django

#31037: Template truncatechars dots missing.
-+--
 Reporter:  老广 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  2.2
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  truncatechars| Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by felixxm):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 `truncatechars` now uses the real ellipsis character (…) instead of 3
 dots, this is a
 [https://docs.djangoproject.com/en/2.2/releases/2.2/#miscellaneous
 documented] and expected change.

 `{{ "Hello Django" | truncatechars:10 }}` returns `Hello Dja…` for me.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.e4d4e097bc587242c42174c021f410f4%40djangoproject.com.

Re: [Django] #31021: migration doesn't work on multi database environment.

2019-11-26 Thread Django

* status: new => closed
* resolution: => needsinfo

Comment:

> I want to say after configure multi database setting without default,
the migration script won't work. It throw the following exception while
migrate...

Just like I said, it works for me with
[https://docs.djangoproject.com/en/2.2/topics/db/multi-db/#an-example an
example] from docs, that doesn't require a `default` DB. Please don't
reopen this ticket without providing a small, sample project which we can
use to reproduce this issue. You can also try to one of
[https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels
support channels].

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.1f11db854b3238473f6f24881566a3e1%40djangoproject.com.

Re: [Django] #31021: migration doesn't work on multi database environment.

2019-11-26 Thread Django

#31021: migration doesn't work on multi database environment.
--+--
 Reporter:  haudoing  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  2.2
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Description changed by haudoing:

Old description:

> The tutorial said that we can omit to set the default database if default
> doesn't makes sense
> https://docs.djangoproject.com/en/2.2/topics/db/multi-db/#defining-your-
> databases
>

> But the following migration script doesn't work after configuration with
> empty default database
> https://github.com/django/django/blob/stable/2.2.x/django/contrib/auth/migrations/0011_update_proxy_permissions.py
>
> on line 42, it use
>
> {{{
> with transaction.atomic():
> Permission.objects.filter(
> permissions_query,
> content_type=old_content_type,
> ).update(content_type=new_content_type)
> }}}
>
> Tracebacks
> {{{
> raise ImproperlyConfigured("settings.DATABASES is improperly
> configured. "
> django.core.exceptions.ImproperlyConfigured: settings.DATABASES is
> improperly configured. Please supply the ENGINE value. Check settings
> documentation for more details.
> }}}
>

>
> This will brake the migration if default database doesn't set

New description:

 The tutorial said that we can omit to set the default database if default
 doesn't makes sense
 https://docs.djangoproject.com/en/2.2/topics/db/multi-db/#defining-your-
 databases


 But the following migration script doesn't work after configuration with
 empty default database
 
https://github.com/django/django/blob/stable/2.2.x/django/contrib/auth/migrations/0011_update_proxy_permissions.py

 on line 42, it use

 {{{
 with transaction.atomic():
 Permission.objects.filter(
 permissions_query,
 content_type=old_content_type,
 ).update(content_type=new_content_type)
 }}}
 This will brake the migration if default database doesn't set


 Tracebacks
 {{{
 raise ImproperlyConfigured("settings.DATABASES is improperly
 configured. "
 django.core.exceptions.ImproperlyConfigured: settings.DATABASES is
 improperly configured. Please supply the ENGINE value. Check settings
 documentation for more details.
 }}}

--

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.ab777e0577031ffacfc45d6de79a93a5%40djangoproject.com.

Re: [Django] #31021: migration doesn't work on multi database environment.

2019-11-26 Thread Django

#31021: migration doesn't work on multi database environment.
--+--
 Reporter:  haudoing  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  2.2
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Description changed by haudoing:

Old description:

> The tutorial said that we can omit to set the default database if default
> doesn't makes sense
> https://docs.djangoproject.com/en/2.2/topics/db/multi-db/#defining-your-
> databases
>
> But the following script brake it
> https://github.com/django/django/blob/stable/2.2.x/django/contrib/auth/migrations/0011_update_proxy_permissions.py
>
> on line 42, it use
>
> {{{
> with transaction.atomic():
> Permission.objects.filter(
> permissions_query,
> content_type=old_content_type,
> ).update(content_type=new_content_type)
> }}}
>
> This will brake the migration if default database doesn't set

New description:

 The tutorial said that we can omit to set the default database if default
 doesn't makes sense
 https://docs.djangoproject.com/en/2.2/topics/db/multi-db/#defining-your-
 databases


 But the following migration script doesn't work after configuration with
 empty default database
 
https://github.com/django/django/blob/stable/2.2.x/django/contrib/auth/migrations/0011_update_proxy_permissions.py

 on line 42, it use

 {{{
 with transaction.atomic():
 Permission.objects.filter(
 permissions_query,
 content_type=old_content_type,
 ).update(content_type=new_content_type)
 }}}

 Tracebacks
 {{{
 raise ImproperlyConfigured("settings.DATABASES is improperly
 configured. "
 django.core.exceptions.ImproperlyConfigured: settings.DATABASES is
 improperly configured. Please supply the ENGINE value. Check settings
 documentation for more details.
 }}}



 This will brake the migration if default database doesn't set

--

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.fda5b575a44ddfe490f7234eff9b8edb%40djangoproject.com.

Re: [Django] #31021: migration doesn't work on multi database environment.

2019-11-26 Thread Django

#31021: migration doesn't work on multi database environment.
--+--
 Reporter:  haudoing  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  2.2
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by haudoing):

 * status:  closed => new
 * resolution:  worksforme =>


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.7f0f5d7f1409a42e985a77eec1476aeb%40djangoproject.com.

[Django] #31037: Template truncatechars dots missing

2019-11-26 Thread Django

#31037: Template truncatechars dots missing
---+---
   Reporter:  老广 |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Template system  |Version:  2.2
   Severity:  Normal   |   Keywords:  truncatechars
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+---
 Django 2.1.14 work fine,  version 2.2.x has bug


 {{ "Hello Django" | truncatechars:10 }}

 Django 2.1.x output:  Hello D...
 Django 2.2.x output:  Hello Djan

 But the doc match the first case

 https://docs.djangoproject.com/en/2.2/ref/templates/builtins/#truncatechars

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.93fbdb172f2d1a8aff131cf2f045fe3f%40djangoproject.com.

Re: [Django] #31021: migration doesn't work on multi database environment.

2019-11-26 Thread Django

#31021: migration doesn't work on multi database environment.
--+--
 Reporter:  haudoing  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  2.2
 Severity:  Normal|   Resolution:  worksforme
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+--

Comment (by haudoing):

 Sorry for my poor English. I doesn't express it well. What I mean to say
 is not migration script brake the multi db setting. I want to say after
 configure multi database setting without default, the migration script
 won't work. It throw the following exception while migrate

 {{{
 raise ImproperlyConfigured("settings.DATABASES is improperly
 configured. "
 django.core.exceptions.ImproperlyConfigured: settings.DATABASES is
 improperly configured. Please supply the ENGINE value. Check settings
 documentation for more details.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.1597848c3aa6eef027ec2234058a81ed%40djangoproject.com.

Re: [Django] #31026: Switch form rendering to template engine

2019-11-26 Thread Django

#31026: Switch form rendering to template engine
--+
 Reporter:  Johannes Hoppe|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Johannes Hoppe):

 * needs_better_patch:  0 => 1


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.f7a45738948a14dfd2f7fe1d205cb59c%40djangoproject.com.

Re: [Django] #29892: Multiple Selenium test failures in Firefox

2019-11-26 Thread Django

#29892: Multiple Selenium test failures in Firefox
---+
 Reporter:  Tom Forbes |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Jon Dufresne):

 * status:  closed => new
 * resolution:  needsinfo =>
 * stage:  Unreviewed => Accepted


Comment:

 PR to fix all tests with Firefox.

 https://github.com/django/django/pull/12149

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.5df4ac522b37c3bee1263ebd422b04eb%40djangoproject.com.

Re: [Django] #22261: reverse() and get_absolute_url() may return different values for same FlatPage

2019-11-26 Thread Django

#22261: reverse() and get_absolute_url() may return different values for same
FlatPage
-+-
 Reporter:  allo@…   |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  assigned
Component:  contrib.flatpages|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Hasan Ramezani):

 * owner:  edanm => Hasan Ramezani
 * needs_better_patch:  1 => 0


Comment:

 I created another [https://github.com/django/django/pull/12148 PR] based
 on the [https://github.com/django/django/pull/2554 first PR].

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.036edfe3f363c39280e82e13bf248cc7%40djangoproject.com.

Re: [Django] #31036: Primary key has incorrect default on MySQL. (was: MySQL driver has incorrect primary key default, causing failure to insert auto increment rows with no additional values.)

2019-11-26 Thread Django

#31036: Primary key has incorrect default on MySQL.
-+-
 Reporter:  PeterVenable |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:  mysql| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => closed
 * resolution:   => worksforme


Comment:

 `DEFAULT` works completely fine for `AUTO_INCREMENT` columns on MySQL. I'm
 not able to reproduce your issue.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.d1d4bad95b5e6483020401b660f28a78%40djangoproject.com.

Re: [Django] #31036: MySQL driver has incorrect primary key default, causing failure to insert auto increment rows with no additional values.

2019-11-26 Thread Django

#31036: MySQL driver has incorrect primary key default, causing failure to 
insert
auto increment rows with no additional values.
-+-
 Reporter:  PeterVenable |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql| Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Description changed by PeterVenable:

Old description:

> The problem:
>
> Given a MySQL table with only one column, an auto-increment primary key
> integer, inserting a row should be as simple as calling
> MyTable.objects.create()
> However, the generated SQL is:
> {{{
> INSERT INTO `myapp_mytable` (`id`) VALUES (DEFAULT);
> -- Error Code: 1062. Duplicate entry '0' for key 'PRIMARY'
> }}}
> Instead it should generate:
> {{{
> INSERT INTO `myapp_mytable` (`id`) VALUES (NULL);
> }}}
>
> The fix could be a one-line edit to
> https://github.com/django/django/blob/master/django/db/backends/base/operations.py#L294
> changing 'DEFAULT' to 'NULL'.

New description:

 The problem:

 Given a MySQL 5.6 table with only one column, an auto-increment primary
 key integer, inserting a row should be as simple as calling
 MyTable.objects.create()
 However, the generated SQL is:
 {{{
 INSERT INTO `myapp_mytable` (`id`) VALUES (DEFAULT);
 -- Error Code: 1062. Duplicate entry '0' for key 'PRIMARY'
 }}}
 Instead it should generate:
 {{{
 INSERT INTO `myapp_mytable` (`id`) VALUES (NULL);
 }}}

 The fix could be a one-line edit to
 
https://github.com/django/django/blob/master/django/db/backends/base/operations.py#L294
 changing 'DEFAULT' to 'NULL'.

--

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.14a017ad7dea1771219371f260d253cf%40djangoproject.com.

[Django] #31036: MySQL driver has incorrect primary key default, causing failure to insert auto increment rows with no additional values.

2019-11-26 Thread Django

#31036: MySQL driver has incorrect primary key default, causing failure to 
insert
auto increment rows with no additional values.
-+-
   Reporter: |  Owner:  nobody
  PeterVenable   |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.2
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  mysql
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 The problem:

 Given a MySQL table with only one column, an auto-increment primary key
 integer, inserting a row should be as simple as calling
 MyTable.objects.create()
 However, the generated SQL is:
 {{{
 INSERT INTO `myapp_mytable` (`id`) VALUES (DEFAULT);
 -- Error Code: 1062. Duplicate entry '0' for key 'PRIMARY'
 }}}
 Instead it should generate:
 {{{
 INSERT INTO `myapp_mytable` (`id`) VALUES (NULL);
 }}}

 The fix could be a one-line edit to
 
https://github.com/django/django/blob/master/django/db/backends/base/operations.py#L294
 changing 'DEFAULT' to 'NULL'.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/055.75dab0440c7b0d502e09906e7a877132%40djangoproject.com.

Re: [Django] #31032: Document the minimal supported version of browsers for the admin

2019-11-26 Thread Django

Comment (by Tom Carrick):

Personally I'd be in favour of keeping this quite modern, as Curtis
mentions in the discussion, perhaps the most recent couple of versions as
of the release date for that particular Django version.

I'd also be in favour of using this as an impetus to clean up some of the
old js, and perhaps we can even remove the old date/time picker code and
rely on the browsers' native implementations.

This might frustrate users that have to target old browsers, but I think
in general it should be reasonable to constrain people who use the admin
to modern browsers. On the other hand, I also don't want this to be a
reason for people to not update Django.

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.870511ab6da973ea78aa92c7868d40d7%40djangoproject.com.

Re: [Django] #29760: Cursors are being closed explicitly in autocommit mode

2019-11-26 Thread Django

#29760: Cursors are being closed explicitly in autocommit mode
-+-
 Reporter:  Ali Teoman Unay  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  cursor, sql, | Triage Stage:  Accepted
  database, autocommit,  |
  transactions, postrgresql, |
  psycopg|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 For the record the above comment was related to the use of `pg_bouncer`
 which is documented to be causing issue with `iterator()`.

 > I believe it appears when the cursor is destroyed before the transaction
 ended and it points to a synchronization error which might be related to
 this issue.

 Ali, I'm not sure I'm following along here. The ticket mentions autocommit
 but you're a mentioning transactions here. Do you happen to use connection
 polling as well?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.1a89fc887316d9cade9c0dbbfc305b2a%40djangoproject.com.

[Django] #31035: Promote BaseCommand.run_from_argv to a documented method

2019-11-26 Thread Django

#31035: Promote BaseCommand.run_from_argv to a documented method
-+
   Reporter:  Roman Odaisky  |  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  Documentation  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 It is sometimes useful to use django-admin commands without argparse. The
 most obvious reason for that would be to forward the arguments to another
 CLI app that parses its own arguments. For example:
 {{{
 class Command(BaseCommand):
 def run_from_argv(self, argv):
 celery.bin.celery.main([argv[0], *argv[2:]])  # can now access
 django.conf.settings
 }}}
 Please update the documentation to make overriding run_from_argv a
 supported way of implementing a management command.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.6f66c0d0287ba0c684d11356aa55b0e1%40djangoproject.com.

Re: [Django] #29760: Cursors are being closed explicitly in autocommit mode

2019-11-26 Thread Django

#29760: Cursors are being closed explicitly in autocommit mode
-+-
 Reporter:  Ali Teoman Unay  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  cursor, sql, | Triage Stage:  Accepted
  database, autocommit,  |
  transactions, postrgresql, |
  psycopg|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Kurt Wheeler):

 I'm getting the same error, while using the `iterator()` method of a
 queryset:
 {{{
 Traceback (most recent call last):
   File "/usr/local/lib/python3.5/dist-packages/django/db/utils.py", line
 96, in inner
 return func(*args, **kwargs)
 psycopg2.OperationalError: cursor "_django_curs_140027036677888_1" does
 not exist
 The above exception was the direct cause of the following exception:
 Traceback (most recent call last):
   File "/usr/local/lib/python3.5/dist-
 packages/django/db/models/sql/compiler.py", line 1512, in cursor_iter
 for rows in iter((lambda: cursor.fetchmany(itersize)), sentinel):
   File "/usr/local/lib/python3.5/dist-
 packages/django/db/models/sql/compiler.py", line 1512, in 
 for rows in iter((lambda: cursor.fetchmany(itersize)), sentinel):
   File "/usr/local/lib/python3.5/dist-packages/django/db/utils.py", line
 96, in inner
 return func(*args, **kwargs)
   File "/usr/local/lib/python3.5/dist-packages/django/db/utils.py", line
 89, in __exit__
 raise dj_exc_value.with_traceback(traceback) from exc_value
   File "/usr/local/lib/python3.5/dist-packages/django/db/utils.py", line
 96, in inner
 return func(*args, **kwargs)
 django.db.utils.OperationalError: cursor "_django_curs_140027036677888_1"
 does not exist
 During handling of the above exception, another exception occurred:
 Traceback (most recent call last):
   File "/home/user/data_refinery_workers/processors/utils.py", line 369,
 in run_pipeline
 last_result = processor(last_result)
   File "/home/user/data_refinery_workers/processors/qn_reference.py", line
 241, in _update_caches
 for experiment in unique_experiments.iterator():
   File "/usr/local/lib/python3.5/dist-packages/django/db/models/query.py",
 line 341, in _iterator
 yield from self._iterable_class(self, chunked_fetch=use_chunked_fetch,
 chunk_size=chunk_size)
   File "/usr/local/lib/python3.5/dist-packages/django/db/models/query.py",
 line 72, in __iter__
 for row in compiler.results_iter(results):
   File "/usr/local/lib/python3.5/dist-
 packages/django/db/models/sql/compiler.py", line 1515, in cursor_iter
 cursor.close()
 psycopg2.OperationalError: cursor "_django_curs_140027036677888_1" does
 not exist
 }}}

 This is the line of code that is causing that error
 
https://github.com/AlexsLemonade/refinebio/blob/dev/workers/data_refinery_workers/processors/qn_reference.py#L241

 Any idea why my cursor is disappearing? I don't think I'm doing anything
 unusual in my code there. The queryset it's iterating over seems to be
 ~20k records.

 The only other thing I can think of that might be non-standard about my
 configuration is that I have a pg_bouncer instance set up to batch
 database connections. It seems to do a good job of pretending to be the
 postgres server itself, but maybe this is a place that it doesn't?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.429772ffa23e3a6e0070df8e21bb65fc%40djangoproject.com.

[Django] #31034: Add a navigation sidebar to the admin

2019-11-26 Thread Django

#31034: Add a navigation sidebar to the admin
-+
   Reporter:  Tom Carrick|  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  contrib.admin  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 Title says it all, really. The idea is to add an optional (probably
 enabled by default?) sidebar for navigation, doing roughly what the
 current homepage does. For now, it'll be a simple implementation only for
 large screens, and hopefully it can be iterated on in the future.

 I opened a discussion here, only got one response but it was positive and
 I think it's not too controversial if it's behind a flag:
 https://groups.google.com/forum/#!topic/django-developers/PAZw8chsp2g

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.03e9e5e69050d2bd76decd8f4d087308%40djangoproject.com.

Re: [Django] #31034: Add a navigation sidebar to the admin

2019-11-26 Thread Django

#31034: Add a navigation sidebar to the admin
---+---
 Reporter:  Tom Carrick|Owner:  Tom Carrick
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+---
Changes (by Tom Carrick):

 * status:  new => assigned
 * owner:  nobody => Tom Carrick


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.3a9c70dfc75258655a550e4560b0d29d%40djangoproject.com.

Re: [Django] #31033: djangoproject documentation search not returning results try searching for forms yields no results

2019-11-26 Thread Django

#31033: djangoproject documentation search not returning results try searching 
for
forms yields no results
-+-
 Reporter:  stherrien|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  2.2
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => closed
 * resolution:   => duplicate
 * component:  Uncategorized => Documentation
 * type:  Uncategorized => Cleanup/optimization


Comment:

 Duplicate of #31017. It works fine for me.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.5c519f028e177becaf69e2d2f5dcf311%40djangoproject.com.

Re: [Django] #31033: djangoproject documentation search not returning results try searching for forms yields no results

2019-11-26 Thread Django

#31033: djangoproject documentation search not returning results try searching 
for
forms yields no results
---+--
 Reporter:  stherrien  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  2.2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by stherrien):

 * Attachment "Screen Shot 2019-11-26 at 10.22.07 AM.png" added.

 screenshot

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.23d282fd4d7419641ed886bc7a17adbf%40djangoproject.com.

[Django] #31033: djangoproject documentation search not returning results try searching for forms yields no results

2019-11-26 Thread Django

#31033: djangoproject documentation search not returning results try searching 
for
forms yields no results
-+
   Reporter:  stherrien  |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  2.2
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 djangoproject.com documentation search not returning results try searching
 for "forms" yields no results

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.c78fa39408460e39600a881629113d85%40djangoproject.com.

Re: [Django] #29892: Multiple Selenium test failures in Firefox

2019-11-26 Thread Django

#29892: Multiple Selenium test failures in Firefox
---+--
 Reporter:  Tom Forbes |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Jon Dufresne):

 * has_patch:  0 => 1


Comment:

 PR https://github.com/django/django/pull/12147 for tests:

 {{{
 test_date_time_picker_shortcuts
 (admin_widgets.tests.DateTimePickerAltTimezoneSeleniumTests)
 test_date_time_picker_shortcuts
 (admin_widgets.tests.DateTimePickerShortcutsSeleniumTests)
 }}}

 (I think this ticket should be reopened.)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.a979e8f53ee51f46d9fa9cef5509591b%40djangoproject.com.

Re: [Django] #29892: Multiple Selenium test failures in Firefox

2019-11-26 Thread Django

#29892: Multiple Selenium test failures in Firefox
---+--
 Reporter:  Tom Forbes |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Jon Dufresne):

 * cc: jon.dufresne@… (added)


Comment:

 I think some of the failures are due to the behavior described in
 https://github.com/mozilla/geckodriver/issues/878 That is, the current
 page isn't invalidated after a `.submit()` call so selenium driver doesn't
 wait for a page reload.

 If I understand the Firefox people correctly, `Element.submit()` should
 not be used as it isn't a WebDriver primitive.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.0432d9c593e1705d5949ca6a98d45a6a%40djangoproject.com.

Re: [Django] #31031: Possible data loss in admin changeform view when using regex special characters in formset prefix

2019-11-26 Thread Django

#31031: Possible data loss in admin changeform view when using regex special
characters in formset prefix
---+
 Reporter:  Baptiste Mispelon  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  2.2
 Severity:  Release blocker|   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Mariusz Felisiak ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"52936efacec4df05df2d9872c09c3332335bf21b" 52936efa]:
 {{{
 #!CommitTicketReference repository=""
 revision="52936efacec4df05df2d9872c09c3332335bf21b"
 Fixed #31031 -- Fixed data loss in admin changelist view when formset's
 prefix contains regex special chars.

 Regression in b18650a2634890aa758abae2f33875daa13a9ba3.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.3dd5bda103246e70aa997e523120541b%40djangoproject.com.

Re: [Django] #31031: Possible data loss in admin changeform view when using regex special characters in formset prefix

2019-11-26 Thread Django

#31031: Possible data loss in admin changeform view when using regex special
characters in formset prefix
---+
 Reporter:  Baptiste Mispelon  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  2.2
 Severity:  Release blocker|   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Mariusz Felisiak ):

 In [changeset:"7873d3757d3075d36cf68771bf4f584ba3386e37" 7873d375]:
 {{{
 #!CommitTicketReference repository=""
 revision="7873d3757d3075d36cf68771bf4f584ba3386e37"
 [2.2.x] Fixed #31031 -- Fixed data loss in admin changelist view when
 formset's prefix contains regex special chars.

 Regression in b18650a2634890aa758abae2f33875daa13a9ba3.

 Backport of 52936efacec4df05df2d9872c09c3332335bf21b from master
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.c3547df85cb9cfc26ad6731a3df66c9e%40djangoproject.com.

Re: [Django] #31031: Possible data loss in admin changeform view when using regex special characters in formset prefix

2019-11-26 Thread Django

#31031: Possible data loss in admin changeform view when using regex special
characters in formset prefix
---+
 Reporter:  Baptiste Mispelon  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  2.2
 Severity:  Release blocker|   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Mariusz Felisiak ):

 In [changeset:"3ed55606c4351913584a79e8b967f99b40316f1d" 3ed55606]:
 {{{
 #!CommitTicketReference repository=""
 revision="3ed55606c4351913584a79e8b967f99b40316f1d"
 [3.0.x] Fixed #31031 -- Fixed data loss in admin changelist view when
 formset's prefix contains regex special chars.

 Regression in b18650a2634890aa758abae2f33875daa13a9ba3.

 Backport of 52936efacec4df05df2d9872c09c3332335bf21b from master
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.ac5635a485e0e34daa0738ba67cf003d%40djangoproject.com.

Re: [Django] #30190: json lines (jsonl) serializer

2019-11-26 Thread Django

#30190: json lines (jsonl) serializer
-+-
 Reporter:  aliva|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core |  Version:  master
  (Serialization)|
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => closed
 * resolution:   => needsinfo
 * type:  Bug => New feature


Comment:

 Please don't reopen closed ticket. This ticket should be discussed in the
 DevelopersMailingList before reopening. We can reconsider it when we reach
 a strong consensus on the mailing list.

 Also please try to be more polite, your comment sounds like a demand. This
 is not a good way to be heard.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.30ec00188f47f42b1dcd3b8488d3f9c8%40djangoproject.com.

Re: [Django] #31030: register SQLite functions as deterministic on Python 3.8

2019-11-26 Thread Django

#31030: register SQLite functions as deterministic on Python 3.8
-+-
 Reporter:  Sergey Fedoseev  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sqlite   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sergey Fedoseev):

 * has_patch:  0 => 1


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.c4a4259d203944843b6ca650825c7cd0%40djangoproject.com.

Re: [Django] #31030: register SQLite functions as deterministic on Python 3.8

2019-11-26 Thread Django

#31030: register SQLite functions as deterministic on Python 3.8
-+-
 Reporter:  Sergey Fedoseev  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sqlite   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Sergey Fedoseev):

 [https://github.com/django/django/pull/12145 PR]

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.9b598eecaffeb9885af27a831a576e64%40djangoproject.com.

Re: [Django] #30190: json lines (jsonl) serializer

2019-11-26 Thread Django

#30190: json lines (jsonl) serializer
-+-
 Reporter:  aliva|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core |  Version:  master
  (Serialization)|
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Francisco Javier):

 * cc: Francisco Javier (added)
 * type:  New feature => Bug
 * status:  closed => new
 * resolution:  needsinfo =>
 * needs_tests:  0 => 1


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.0587c62e60c6dde49ec4c7c7f3571307%40djangoproject.com.

Re: [Django] #30190: json lines (jsonl) serializer

2019-11-26 Thread Django

Comment (by Francisco Javier):

The Django Core MUST solve his own things by himself, and not relaying to
a third party solution.

If dumpdata/loaddata is broken for very big datasets, the issue must be
addresed and solved as soon as posible.

In my particular case, I have a Sqlite3 DataBase of 800MB, and want to
migrate to PostgreSQL. The Dumpdata/Loaddata combo is the only straight
way to do it.

If the django-mljson (or the patch submited in the ticket) solves the
MemoryError of Loaddata in big datasets, Django-Core must integrate the
mljson (or the patch submited) as the default serializer/deserializer for
dumpdata/loaddata process.

Actually, my issue is solved by using django-mljson, but lost 2 days
figuring 'what the heck' was going wrong.

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.1e4ff14c119c3d2bb91337ea78c88541%40djangoproject.com.

41 matches

Mail list logo