date:20160219

Re: [Django] #26165: Add an FAQ that explains why Django's CSRF isn't vulnerable

2016-02-19 Thread Django

#26165: Add an FAQ that explains why Django's CSRF isn't vulnerable
-+-
 Reporter:  timgraham|Owner:  acemaster
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  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 zachborboa):

 * cc: zachborboa@… (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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.fc093ca2aea2f8522ce3f3f7c49095f1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26239: Document auto_now behavior with QuerySet.update()

2016-02-19 Thread Django

#26239: Document auto_now behavior with QuerySet.update()
--+
 Reporter:  boussouira|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 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
--+

Comment (by AMaini503):

 Replying to [ticket:26239 boussouira]:
 > I don't know if this is a bug or not, but when using `update()`, the
 DateTime fields with `auto_now` are not updated to the current time. The
 documentation of `auto_now` doesn't say anything about that situation.
 > For example:
 >
 > {{{
 > #  This won't update `updated_at`:
 > Order.objects.filter(user_id=7).update(check_count=3)
 >
 > # You have to explicitly include it in update()
 > Order.objects.filter(user_id=7).update(check_count=3,
 updated_at=timezone.now())
 > }}}

 --> I will try to work on this. But should update be modified to include
 timestamp by itself or documentation should be altered to state that
 timestamp needs to be passed explicitly ?

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.2d95e7a7fee0f03398034f362e6e3f2e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25292: "'str' object has no attribute '_meta'" crash in ManyToManyField.through_fields check

2016-02-19 Thread Django

#25292: "'str' object has no attribute '_meta'" crash in
ManyToManyField.through_fields check
-+-
 Reporter:  thbarrons|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (System |  Version:  1.8
  checks)|
 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
-+-

Comment (by timgraham):

 Adding those models to a project, I still cannot reproduce a crash. Maybe
 you could provide a sample project?

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.a4c7df81b7f7f773d7b44509f83d2cf3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25292: "'str' object has no attribute '_meta'" crash in ManyToManyField.through_fields check

2016-02-19 Thread Django

#25292: "'str' object has no attribute '_meta'" crash in
ManyToManyField.through_fields check
-+-
 Reporter:  thbarrons|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (System |  Version:  1.8
  checks)|
 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
-+-

Comment (by raratiru):

 {{{
 class Stage(models.Model):
 stage_id = models.AutoField(primary_key=True)

 class Category(models.Model):
 category_id = models.AutoField(primary_key=True)
 stage = models.ManyToManyField('Stage', through='StageCategory',
 related_name="stage_category")
 }}}

 If we do not define the StageCategory table, the error is not understood
 at all:
 {{{
 $ ./manage.py runserver
 Performing system checks...



 Unhandled exception in thread started by .wrapper at 0x7f3f16c930d0>
 Traceback (most recent call last):
   File "/home/flyer/.virtualenvs/lived/lib/python3.4/site-
 packages/django/utils/autoreload.py", line 229, in wrapper
 fn(*args, **kwargs)
   File "/home/flyer/.virtualenvs/lived/lib/python3.4/site-
 packages/django/core/management/commands/runserver.py", line 114, in
 inner_run
 self.validate(display_num_errors=True)
   File "/home/flyer/.virtualenvs/lived/lib/python3.4/site-
 packages/django/core/management/base.py", line 469, in validate
 return self.check(app_configs=app_configs,
 display_num_errors=display_num_errors)
   File "/home/flyer/.virtualenvs/lived/lib/python3.4/site-
 packages/django/core/management/base.py", line 482, in check
 include_deployment_checks=include_deployment_checks,
   File "/home/flyer/.virtualenvs/lived/lib/python3.4/site-
 packages/django/core/checks/registry.py", line 72, in run_checks
 new_errors = check(app_configs=app_configs)
   File "/home/flyer/.virtualenvs/lived/lib/python3.4/site-
 packages/django/core/checks/model_checks.py", line 28, in check_all_models
 errors.extend(model.check(**kwargs))
   File "/home/flyer/.virtualenvs/lived/lib/python3.4/site-
 packages/django/db/models/base.py", line 1207, in check
 errors.extend(cls._check_long_column_names())
   File "/home/flyer/.virtualenvs/lived/lib/python3.4/site-
 packages/django/db/models/base.py", line 1648, in _check_long_column_names
 for m2m in f.rel.through._meta.local_fields:
 AttributeError: 'str' object has no attribute '_meta'

 }}}

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.696b876ab6efdd59c320d047365bbe85%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26234: Add `css_classes` parameter to Form.as_*() methods

2016-02-19 Thread Django

#26234: Add `css_classes` parameter to Form.as_*() methods
--+--
 Reporter:  willstott101  |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Forms |  Version:  1.9
 Severity:  Normal|   Resolution:  wontfix
 Keywords:  css forms | Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by timgraham):

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


Comment:

 Let's reopen this if you can get consensus on the DevelopersMailingList to
 do it. I'm still not certain promoting more use of these methods is a good
 idea.

 Maybe template-based widget rendering (#15667) will help for your use
 case.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.350abb1df839419557c76db4956b8943%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26240: docs about cached.Loader thread safety unclear

2016-02-19 Thread Django

#26240: docs about cached.Loader thread safety unclear
---+--
 Reporter:  TZanke |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.9
 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
---+--
Changes (by timgraham):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => worksforme
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 If you click through to the "for more information" link, it does say,
 "Since Django is sometimes run in multi-threaded..." This seems fine to
 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.7e71b77f032378a9ac63e4e2ab10434c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17419: Add a JSON template filter

2016-02-19 Thread Django

#17419: Add a JSON template filter
---+-
 Reporter:  lau|Owner:  aaugustin
 Type:  New feature|   Status:  new
Component:  Template system|  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  json template tag  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by gavinwahl):

 I want to point out that django-argonauts can be used both to generate
 javascript code and to populate a `

Re: [Django] #21734: admin's delete_selected action doesn't catch ProtectedError

2016-02-19 Thread Django

#21734: admin's delete_selected action doesn't catch ProtectedError
---+-
 Reporter:  sander@…   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  needsinfo
 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 timgraham):

 * Attachment "21734-test.diff" 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/076.c9bdb193f2aba9c664b1ff51a75cb0f8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21734: admin's delete_selected action doesn't catch ProtectedError (was: Admin doesn't catch ProtectedError)

2016-02-19 Thread Django

#21734: admin's delete_selected action doesn't catch ProtectedError
---+-
 Reporter:  sander@…   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  needsinfo
 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 timgraham):

 * needs_better_patch:  0 => 1
 * needs_tests:  1 => 0


Comment:

 You can create a crash by posting data and bypassing the confirmation
 page. Seems low priority given the admin is for "trusted users" but
 wouldn't hurt to fix. See #26235 for the same issue for the regular delete
 view.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/076.9c5924561d1c33863fd49f670b7ee79b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21734: admin's delete_selected action doesn't catch ProtectedError

2016-02-19 Thread Django

#21734: admin's delete_selected action doesn't catch ProtectedError
---+
 Reporter:  sander@…   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  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 timgraham):

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


--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/076.0cca082ba9ed35954da5be372b6cd88e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26235: POST to delete protected fk relationship raises ProtectedError

2016-02-19 Thread Django

#26235: POST to delete protected fk relationship raises ProtectedError
---+
 Reporter:  Zelvuska   |Owner:  nobody
 Type:  Bug|   Status:  new
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:  1  |UI/UX:  0
---+
Changes (by timgraham):

 * Attachment "26235.diff" 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.237059e618d9cdcb68b7cb452807ebe8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26235: POST to delete protected fk relationship raises ProtectedError

2016-02-19 Thread Django

#26235: POST to delete protected fk relationship raises ProtectedError
---+
 Reporter:  Zelvuska   |Owner:  nobody
 Type:  Bug|   Status:  new
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:  1  |UI/UX:  0
---+
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


Comment:

 I guess we could try to prevent the issue in case the intermediate page is
 bypassed. Test attached.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.e008d82990692be666f2d1dadece998a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26246: Migrations fail when `'django.contrib.sites'` is included in INSTALLED_APPS

2016-02-19 Thread Django

#26246: Migrations fail when `'django.contrib.sites'` is included in 
INSTALLED_APPS
-+-
 Reporter:  agconti  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.sites|  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  sites, migrations,   | Triage Stage:
  django_site, migrate   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by agconti):

 Thank you. This solved my issue.

 Replying to [comment:3 timgraham]:
 > You have a custom entry in `MIGRATION_MODULES` for that app that points
 to a nonexistent module: `'sites': 'contrib.sites.migrations'`.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.c7a2645e6736c20ce0ac5c5d1cf67c46%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26244: URLValidator and http/request.py use different validators

2016-02-19 Thread Django

#26244: URLValidator and http/request.py use different validators
-+-
 Reporter:  zachborboa   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  HTTP handling|  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 timgraham):

 * cc: apollo13 (added)


Comment:

 Florian, what do you think? The regular expression in `request.py` is a
 security fix from 27560924ec1e567be4727ef8d7dfc4d3879c048c.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.c40895e251e0633d6a8dce17c0bb2811%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26246: Migrations fail when `'django.contrib.sites'` is included in INSTALLED_APPS

2016-02-19 Thread Django

#26246: Migrations fail when `'django.contrib.sites'` is included in 
INSTALLED_APPS
-+-
 Reporter:  agconti  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.sites|  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  sites, migrations,   | Triage Stage:
  django_site, migrate   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 You have a custom entry in `MIGRATION_MODULES` for that app that points to
 a nonexistent module: `'sites': 'contrib.sites.migrations'`.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.1bb6f228f2c96688d34980e9aaef9fd6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26247: External link in need of redirect to proper documentation location

2016-02-19 Thread Django

#26247: External link in need of redirect to proper documentation location
-+-
 Reporter:  adaminfinitum|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Uncategorized|  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  404, error,  | Triage Stage:
  redirect, 301, documentation   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => invalid
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Not sure if this is a good idea or not. You could bring it up on the
 DevelopersMailingList (here's [https://groups.google.com/d/topic/django-
 developers/5TsL3MED5W8/discussion an existing thread]. Anyway, the correct
 ticket tracker for the website is
 https://github.com/django/djangoproject.com/.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.c7b017e93abe2e420e33bd82f9e49511%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26247: External link in need of redirect to proper documentation location

2016-02-19 Thread Django

The link is under the 4th code block in that tab (the `#` URL fragment is
to the tab, not the section itself).

The anchor text reads __Django feature syntax__ and it points to
https://docs.djangoproject.com/en/1.3/howto/initial-data/

Which is a 404 (and the link on that page requested I report it).

Apparently it just needs updated to the current versions documentation:
https://docs.djangoproject.com/en/1.9/howto/initial-data/

It wouldn't surprise me if other versions (and other documents of each of
those versions) all need updated too.

I tried to work out a RegEx for a redirect but was struggling with it when
I realized that this site runs on Nginx not Apache and the code wouldn't
work anyway.

Since the link's destination URL looks proper, I'm guessing URL structures
changed and that all links to that URL would now be broken so rather than
contacting the author, I am submitting it here as it should be redirected
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/056.7b262f8a0b200ee974854db18ffb42dc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25653: Provide a way to run only the selenium tests

2016-02-19 Thread Django

#25653: Provide a way to run only the selenium tests
---+
 Reporter:  timgraham  |Owner:  mrbox
 Type:  New feature|   Status:  closed
Component:  Testing framework  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"6670da75ff8a59b2ec0b465846e3f76aab9155b2" 6670da75]:
 {{{
 #!CommitTicketReference repository=""
 revision="6670da75ff8a59b2ec0b465846e3f76aab9155b2"
 Fixed #25653 -- Made --selenium run only the selenium tests.
 }}}

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.a42f80d90c40ade9f71a4bc67c6d6ce3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25735: Add test tagging to Django test runner

2016-02-19 Thread Django

#25735: Add test tagging to Django test runner
---+
 Reporter:  carljm |Owner:  mrbox
 Type:  New feature|   Status:  closed
Component:  Testing framework  |  Version:  1.8
 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
---+

Comment (by Tim Graham ):

 In [changeset:"032f5a789692d69ab206f902867ff2c3e05c5320" 032f5a78]:
 {{{
 #!CommitTicketReference repository=""
 revision="032f5a789692d69ab206f902867ff2c3e05c5320"
 Refs #25735 -- Made @tag decorator importable from django.test.
 }}}

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.6d71039e0fb25e6a62cece372598006b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25349: ModelForm regression when setting None into a ForeignKey

2016-02-19 Thread Django

#25349: ModelForm regression when setting None into a ForeignKey
-+-
 Reporter:  jpaulett |Owner:  Tim
 |  Graham 
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

 * owner:   => Tim Graham 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"375e1cfe2b2e1c3c57f882147c34902c6e8189ac" 375e1cfe]:
 {{{
 #!CommitTicketReference repository=""
 revision="375e1cfe2b2e1c3c57f882147c34902c6e8189ac"
 Fixed #25349 -- Allowed a ModelForm to unset a fields with blank=True,
 required=False.
 }}}

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.37b0b2b3a3379430ad7ea8ed22a338e5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26246: Migrations fail when `'django.contrib.sites'` is included in INSTALLED_APPS

2016-02-19 Thread Django

#26246: Migrations fail when `'django.contrib.sites'` is included in 
INSTALLED_APPS
-+-
 Reporter:  agconti  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.sites|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  sites, migrations,   | Triage Stage:
  django_site, migrate   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by agconti:

Old description:

> When `'django.contrib.sites'` is included in INSTALLED_APPS,
>
> Running:
>
> {{{
>   python manage.py migrate
> }}}
>
> fails with:
>

> {{{
> django.db.utils.ProgrammingError: relation "django_site" does not
> exist
> LINE 1: SELECT (1) AS "a" FROM "django_sit
> e" LIMIT 1
> }}}
>
> I have followed the docs and included `SITE_ID = 1` in my settings.
>
> Even more puzzling is that when I try to migrate the `sites` app
> separately with `python manage.py migrate sites` it that fails with:
>

> {{{
> CommandError: App 'sites' does not have migrations
> }}}
>
> This issue can be reporduced my cloning: https://github.com/agconti
> /django-contrib-sites-failed-migration-example and running the
> migrations.
>
> Do you have any idea on way resolve this?
>

> Installed Apps:
>

> {{{
> INSTALLED_APPS = (
>  'django.contrib.admin',
>   'django.contrib.sites',
>   'django.contrib.auth',
>   'django.contrib.contenttypes',
>   'django.contrib.sessions',
>   'django.contrib.messages',
>   'django.contrib.staticfiles',
> )
> }}}
>
> Migration error:
>
> {{{
>
> (env) ustwo-nyc-conti-mbpr :: ~/dev/test-web » ./test/manage.py migrate
> 128 ↵
> Operations to perform:
>   Apply all migrations: admin, contenttypes, auth, sessions
> Running migrations:
>   No migrations to apply.
> Traceback (most recent call last):
>   File "./test/manage.py", line 11, in 
> execute_from_command_line(sys.argv)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 353, in
> execute_from_command_line
> utility.execute()
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 345, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/core/management/base.py", line 348, in run_from_argv
> self.execute(*args, **cmd_options)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/core/management/base.py", line 399, in execute
> docs(README): updated with issue details
> output = self.handle(*args, **options)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/core/management/commands/migrate.py", line 204, in handle
> emit_post_migrate_signal(self.verbosity, self.interactive,
> connection.alias)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/core/management/sql.py", line 50, in
> emit_post_migrate_signal
> using=db)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/dispatch/dispatcher.py", line 192, in send
> response = receiver(signal=self, sender=sender, **named)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/contrib/sites/management.py", line 20, in
> create_default_site
> if not Site.objects.using(using).exists():
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/db/models/query.py", line 651, in exists
> return self.query.has_results(using=self.db)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/db/models/sql/query.py", line 501, in has_results
> return compiler.has_results()
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/db/models/sql/compiler.py", line 819, in has_results
> return bool(self.execute_sql(SINGLE))
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/db/models/sql/compiler.py", line 848, in execute_sql
> cursor.execute(sql, params)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/db/backends/utils.py", line 79, in execute
> return super(CursorDebugWrapper, self).execute(sql, params)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/db/backends/utils.py", line 64, in execute
> return self.cursor.execute(sql, params)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/db/utils.py", line 95, in __exit__
> six.reraise(dj_exc_type, dj_exc_value, traceback)

Re: [Django] #26246: Migrations fail when `'django.contrib.sites'` is included in INSTALLED_APPS

2016-02-19 Thread Django

#26246: Migrations fail when `'django.contrib.sites'` is included in 
INSTALLED_APPS
-+-
 Reporter:  agconti  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.sites|  Version:  1.9
 Severity:  Normal   |   Resolution:
 Keywords:  sites, migrations,   | Triage Stage:
  django_site, migrate   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by agconti):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Old description:

> When `'django.contrib.sites'` is included in INSTALLED_APPS,
>
> ### Running:
>
> {{{
>   python manage.py migrate
> }}}
>
> ### fails with:
>

> {{{
> django.db.utils.ProgrammingError: relation "django_site" does not
> exist
> LINE 1: SELECT (1) AS "a" FROM "django_sit
> e" LIMIT 1
> }}}
>
> I have followed the docs and included `SITE_ID = 1` in my settings.
>
> Even more puzzling is that when I try to migrate the `sites` app
> separately with `python manage.py migrate sites` it that fails with:
>

> {{{
> CommandError: App 'sites' does not have migrations
> }}}
>
> This issue can be reporduced my cloning: https://github.com/agconti
> /django-contrib-sites-failed-migration-example and running the
> migrations.
>
> Do you have any idea on way resolve this?
>

> Installed Apps:
>

> {{{
> INSTALLED_APPS = (
>  'django.contrib.admin',
>   'django.contrib.sites',
>   'django.contrib.auth',
>   'django.contrib.contenttypes',
>   'django.contrib.sessions',
>   'django.contrib.messages',
>   'django.contrib.staticfiles',
> )
> }}}
>
> Migration error:
>
> {{{
>
> (env) ustwo-nyc-conti-mbpr :: ~/dev/test-web » ./test/manage.py migrate
> 128 ↵
> Operations to perform:
>   Apply all migrations: admin, contenttypes, auth, sessions
> Running migrations:
>   No migrations to apply.
> Traceback (most recent call last):
>   File "./test/manage.py", line 11, in 
> execute_from_command_line(sys.argv)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 353, in
> execute_from_command_line
> utility.execute()
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/core/management/__init__.py", line 345, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/core/management/base.py", line 348, in run_from_argv
> self.execute(*args, **cmd_options)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/core/management/base.py", line 399, in execute
> docs(README): updated with issue details
> output = self.handle(*args, **options)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/core/management/commands/migrate.py", line 204, in handle
> emit_post_migrate_signal(self.verbosity, self.interactive,
> connection.alias)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/core/management/sql.py", line 50, in
> emit_post_migrate_signal
> using=db)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/dispatch/dispatcher.py", line 192, in send
> response = receiver(signal=self, sender=sender, **named)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/contrib/sites/management.py", line 20, in
> create_default_site
> if not Site.objects.using(using).exists():
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/db/models/query.py", line 651, in exists
> return self.query.has_results(using=self.db)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/db/models/sql/query.py", line 501, in has_results
> return compiler.has_results()
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/db/models/sql/compiler.py", line 819, in has_results
> return bool(self.execute_sql(SINGLE))
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/db/models/sql/compiler.py", line 848, in execute_sql
> cursor.execute(sql, params)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/db/backends/utils.py", line 79, in execute
> return super(CursorDebugWrapper, self).execute(sql, params)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/db/backends/utils.py", line 64, in execute
> return self.cursor.execute(sql, params)
>   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
> packages/django/db/utils.py", l

[Django] #26246: Migrations fail when `'django.contrib.sites'` is included in INSTALLED_APPS

2016-02-19 Thread Django

#26246: Migrations fail when `'django.contrib.sites'` is included in 
INSTALLED_APPS
-+-
 Reporter:  agconti  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:   |Version:  1.9
  contrib.sites  |   Keywords:  sites, migrations, django_site,
 Severity:  Normal   |  migrate
 Triage Stage:   |  Has patch:  0
  Unreviewed |
Easy pickings:  0|  UI/UX:  0
-+-
 When `'django.contrib.sites'` is included in INSTALLED_APPS,

 ### Running:

 {{{
   python manage.py migrate
 }}}

 ### fails with:


 {{{
 django.db.utils.ProgrammingError: relation "django_site" does not
 exist
 LINE 1: SELECT (1) AS "a" FROM "django_sit
 e" LIMIT 1
 }}}

 I have followed the docs and included `SITE_ID = 1` in my settings.

 Even more puzzling is that when I try to migrate the `sites` app
 separately with `python manage.py migrate sites` it that fails with:


 {{{
 CommandError: App 'sites' does not have migrations
 }}}

 This issue can be reporduced my cloning: https://github.com/agconti
 /django-contrib-sites-failed-migration-example and running the migrations.

 Do you have any idea on way resolve this?


 Installed Apps:


 {{{
 INSTALLED_APPS = (
  'django.contrib.admin',
   'django.contrib.sites',
   'django.contrib.auth',
   'django.contrib.contenttypes',
   'django.contrib.sessions',
   'django.contrib.messages',
   'django.contrib.staticfiles',
 )
 }}}

 Migration error:

 {{{

 (env) ustwo-nyc-conti-mbpr :: ~/dev/test-web » ./test/manage.py migrate
 128 ↵
 Operations to perform:
   Apply all migrations: admin, contenttypes, auth, sessions
 Running migrations:
   No migrations to apply.
 Traceback (most recent call last):
   File "./test/manage.py", line 11, in 
 execute_from_command_line(sys.argv)
   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 353, in
 execute_from_command_line
 utility.execute()
   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 345, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
 packages/django/core/management/base.py", line 348, in run_from_argv
 self.execute(*args, **cmd_options)
   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
 packages/django/core/management/base.py", line 399, in execute
 docs(README): updated with issue details
 output = self.handle(*args, **options)
   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
 packages/django/core/management/commands/migrate.py", line 204, in handle
 emit_post_migrate_signal(self.verbosity, self.interactive,
 connection.alias)
   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
 packages/django/core/management/sql.py", line 50, in
 emit_post_migrate_signal
 using=db)
   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
 packages/django/dispatch/dispatcher.py", line 192, in send
 response = receiver(signal=self, sender=sender, **named)
   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
 packages/django/contrib/sites/management.py", line 20, in
 create_default_site
 if not Site.objects.using(using).exists():
   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
 packages/django/db/models/query.py", line 651, in exists
 return self.query.has_results(using=self.db)
   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
 packages/django/db/models/sql/query.py", line 501, in has_results
 return compiler.has_results()
   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
 packages/django/db/models/sql/compiler.py", line 819, in has_results
 return bool(self.execute_sql(SINGLE))
   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
 packages/django/db/models/sql/compiler.py", line 848, in execute_sql
 cursor.execute(sql, params)
   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 79, in execute
 return super(CursorDebugWrapper, self).execute(sql, params)
   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 64, in execute
 return self.cursor.execute(sql, params)
   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
 packages/django/db/utils.py", line 95, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/Users/conti/dev/test-web/env/lib/python2.7/site-
 packages/django/db/backends/utils.py", line 64, in execute
 return self.cursor.execute(sql, params)
 django.db.utils.ProgrammingError: relation "django_site" does not exist
 LINE 1: SELECT (1) AS "a" FROM "django_site" LIMIT 1
 }}}

--
Ticket URL: 
Django

Re: [Django] #26235: POST to delete protected fk relationship raises ProtectedError

2016-02-19 Thread Django

#26235: POST to delete protected fk relationship raises ProtectedError
---+--
 Reporter:  Zelvuska   |Owner:  nobody
 Type:  Bug|   Status:  new
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:  1  |UI/UX:  0
---+--

Comment (by timgraham):

 The "delete" button shouldn't appear on the intermediate page, no?

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.dfdf92e904d5943109e4e715b96b0af6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26244: URLValidator and http/request.py use different validators

2016-02-19 Thread Django

#26244: URLValidator and http/request.py use different validators
-+-
 Reporter:  zachborboa   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  HTTP handling|  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
-+-

Comment (by zachborboa):

 `host_validation_re` could be changed from

 {{{#!python
 host_validation_re =
 re.compile(r"^([a-z0-9.-]+|\[[a-f0-9]*:[a-f0-9:]+\])(:\d+)?$")
 }}}

 to something like
 {{{#!python
 host_validation_re = re.compile(
 r'(?:' + ipv4_re + '|' + ipv6_re + '|' + host_re + ')'
 r'(?::\d{2,5})?'  # port
 )
 }}}

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.73bf20518b33c11dadde2811a331af1e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #13312: Add a way to customize the order_by() of null fields (was: order_by on null-field gives different results on different db engines)

2016-02-19 Thread Django

#13312: Add a way to customize the order_by() of null fields
-+-
 Reporter:  binary   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ordering, order_by,  | Triage Stage:  Accepted
  null   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * version:  1.1 => master
 * type:  Uncategorized => New feature
 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.653dc2906787f1eaa418791a39279328%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26245: [1.9] Change of primary_key Field on Child Table with One-to-one Relationship Create Duplicated Record

2016-02-19 Thread Django

#26245: [1.9] Change of primary_key Field on Child Table with One-to-one
Relationship Create Duplicated Record
-+-
 Reporter:  lystor   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  One-to-one,  | Triage Stage:
  duplicate  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * status:  new => closed
 * severity:  Release blocker => Normal
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0
 * resolution:   => duplicate


Comment:

 Unless the behavior changed in 1.9, this looks like a duplicate of #2259
 to 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.25e84e87b35c7e158a41262812d5bf04%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26241: collectstatic's output of `skipping x (not modified)` isn't very clear

2016-02-19 Thread Django

#26241: collectstatic's output of `skipping x (not modified)` isn't very clear
-+-
 Reporter:  kezabelle|Owner:  AMaini503
 Type:  Uncategorized|   Status:  closed
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:
 |  worksforme
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 I agree with Claude.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.75a32167a7b6aa08a5e38b02941acbca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26244: URLValidator and http/request.py use different validators

2016-02-19 Thread Django

#26244: URLValidator and http/request.py use different validators
-+-
 Reporter:  zachborboa   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  HTTP handling|  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 timgraham):

 * component:  Uncategorized => HTTP handling
 * needs_better_patch:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Unless there is some problem that fixing this will solve, I vote not to
 try to combine the two. `URLValidator` changes too often. If we cause some
 regression there, at least it's some limited compared to if we also break
 `django.http.request`.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.9822ee3847b8e7ff9afbd05fe7136c4e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26245: [1.9] Change of primary_key Field on Child Table with One-to-one Relationship Create Duplicated Record

2016-02-19 Thread Django

#26245: [1.9] Change of primary_key Field on Child Table with One-to-one
Relationship Create Duplicated Record
--+
 Reporter:  lystor|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.9
 Severity:  Release blocker   |   Keywords:  One-to-one,
  |  duplicate
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Hi

 After changing the value of primary_key field on child table (using drop-
 down list) with One-to-one relationship in '''Django Admin Site''' we got
 duplicated record in table because the record with new primary_key value
 is added but existing record with old primary_key is not deleted.

 - django 1.9.2
 - python 3.5.1
 - mysqlclient 1.3.7
 - mysql 5.7.11

 
 '''models.py'''
 {{{
 from django.db import models

 class Metric(models.Model):
 name= models.CharField(unique=True, max_length=255)
 params  = models.CharField(max_length=255)
 value   = models.CharField(max_length=255, blank=True)

 class Meta:
 managed = False
 db_table= 'metrics'

 def __str__(self):
 return str(self.id)


 class PollerEvent(models.Model):
 metric  = models.OneToOneField(Metric,
 on_delete=models.CASCADE, primary_key=True)
 duration= models.IntegerField()
 error   = models.TextField()

 class Meta:
 managed = False
 db_table= 'poller_events'

 def __str__(self):
 return '%s (%s)' % (self.metric_id, self.error)
 }}}

 
 '''admin.py'''
 {{{
 from django.contrib import admin

 from .models import Metric, PollerEvent

 admin.site.register(Metric)
 admin.site.register(PollerEvent)
 }}}

 
 '''test.py'''
 {{{
 import django, os
 os.environ.setdefault("DJANGO_SETTINGS_MODULE", "project.settings")
 django.setup()
 from dashboard.models import Metric, PollerEvent

 print('=== BEFORE ===')
 print(Metric.objects.all())
 print(PollerEvent.objects.all())

 print('=== CHANGE ===')
 event = PollerEvent.objects.get(metric_id = 3)
 event.metric_id = 4
 event.save()

 print('=== AFTER ===')
 print(PollerEvent.objects.all())

 print('=== SQL ===')
 for query in django.db.connection.queries:
 print(query)
 }}}

 
 '''result'''
 {{{
 === BEFORE ===
 [, , ]

 []

 === CHANGE ===

 === AFTER ===
 [, ]

 === SQL ===
 {'sql': 'SET SQL_AUTO_IS_NULL = 0', 'time': '0.036'}

 {'sql': 'SELECT `metrics`.`id`, `metrics`.`name`, `metrics`.`params`,
 `metrics`.`value` FROM `metrics` LIMIT 21', 'time': '0.036'}

 {'sql': 'SELECT `poller_events`.`metric_id`, `poller_events`.`duration`,
 `poller_events`.`error` FROM `poller_events` LIMIT 21', 'time': '0.036'}

 {'sql': 'SELECT `poller_events`.`metric_id`, `poller_events`.`duration`,
 `poller_events`.`error` FROM `poller_events` WHERE
 `poller_events`.`metric_id` = 3', 'time': '0.036'}

 {'sql': "UPDATE `poller_events` SET `duration` = 555, `error` = 'timeout'
 WHERE `poller_events`.`metric_id` = 4", 'time': '0.036'}

 {'sql': "INSERT INTO `poller_events` (`metric_id`, `duration`, `error`)
 VALUES (4, 555, 'timeout')", 'time': '0.036'}

 {'sql': 'SELECT `poller_events`.`metric_id`, `poller_events`.`duration`,
 `poller_events`.`error` FROM `poller_events` LIMIT 21', 'time': '0.036'}
 }}}

 

 Please fix this bug.
 Thank you!

 --
 With best regards,
 Mykola

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.6243913ee62ee585f8777f90d9bcd1af%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26244: URLValidator and http/request.py use different validators

2016-02-19 Thread Django

#26244: URLValidator and http/request.py use different validators
---+
 Reporter:  zachborboa |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  master
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 The host validation patterns should probably be the same and written in a
 way that allows their reuse.

 ~
 https://github.com/django/django/blob/master/django/core/validators.py#L99
 ~ https://github.com/django/django/blob/master/django/http/request.py#L25

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/053.0f0a5bfbe942e7baeb1d27f2747033ff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26237: uuid.UUID() generates 'invalid syntax' and 'badly formed' uuids

2016-02-19 Thread Django

#26237: uuid.UUID() generates 'invalid syntax' and 'badly formed' uuids
---+--
 Reporter:  MalikRumi  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Uncategorized  |  Version:  1.9
 Severity:  Normal |   Resolution:  invalid
 Keywords:  uuid   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by charettes):

 > What does 'confirmation' of a bug look like?

 An exception with a traceback involving Django's source code should be a
 good hint it might be Django bug.

 In the case of your report Django isn't involved at all and both traceback
 point to the cause of your errors (a syntax and name a error).

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.3bccba62472620da5701efd321e70d26%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26241: collectstatic's output of `skipping x (not modified)` isn't very clear

2016-02-19 Thread Django

#26241: collectstatic's output of `skipping x (not modified)` isn't very clear
-+-
 Reporter:  kezabelle|Owner:  AMaini503
 Type:  Uncategorized|   Status:  assigned
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by claudep):

 As far as I'm concerned, `(not modified)` seems rather clear (the file has
 not been modified since last run). I don't find the proposal better.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.df98d3f4e3cf7cfe455855df89f56634%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26242: Allow to create models with static app_label at import stage.

2016-02-19 Thread Django

#26242: Allow to create models with static app_label at import stage.
---+--
 Reporter:  kramarz|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.9
 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
---+--

Comment (by aaugustin):

 The ability to import models (directly or indirectly) in an application's
 `__init__.py` was deprecated in 1.7 and removed in 1.9. I knew it would
 make your use case impossible. Importing too many things in `__init__.py`
 can cause hard-to-break import loops. That's why I didn't mind
 discouraging this pattern.

 The current situation results from trade-off between fixing very complex
 bugs that could occur when a Django application starts and preserving
 backwards-compatibility. It was done for reasons discussed at length on
 the mailing list.

 I don't oppose further changes in the area, however, I kindly ask that you
 review past discussions (search for "app-loading" on the django-developers
 archives) before undoing decisions into which a lot of work was put.
 Thanks.


 PS -- regarding the fact that apps are explicitly declared while models
 aren't, Django has always had an INSTALLED_APPS setting but never had
 INSTALLED_MODELS or equivalent, so I don't think you can draw useful
 conclusions from this observation.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.ea63e5d604d16bf07fc317e390cf47db%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23155: Add request attr to user_login_failed signal

2016-02-19 Thread Django

#23155: Add request attr to user_login_failed signal
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.auth |  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 timgraham):

 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.29d645c91f8cb58ceafa49a6a1e84a99%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26243: Note in deployment checklist that PYTHONHASHSEED is randomized by default as of Python 3.3

2016-02-19 Thread Django

#26243: Note in deployment checklist that PYTHONHASHSEED is randomized by 
default
as of Python 3.3
-+-
 Reporter:  raphaelm |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"c7448c39a313abb33afd23207348d6f3afae9ce8" c7448c39]:
 {{{
 #!CommitTicketReference repository=""
 revision="c7448c39a313abb33afd23207348d6f3afae9ce8"
 [1.9.x] Fixed #26243 -- Noted that 'python -R' is enabled by default in
 Python 3.3.

 Backport of 5c31d8d189ec24d83e25e2c560860f70307b431e 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.638c02d1d97d7de00803dcff97d102c6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26243: Note in deployment checklist that PYTHONHASHSEED is randomized by default as of Python 3.3

2016-02-19 Thread Django

#26243: Note in deployment checklist that PYTHONHASHSEED is randomized by 
default
as of Python 3.3
-+-
 Reporter:  raphaelm |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:  fixed
 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
-+-

Comment (by Tim Graham ):

 In [changeset:"5c31d8d189ec24d83e25e2c560860f70307b431e" 5c31d8d1]:
 {{{
 #!CommitTicketReference repository=""
 revision="5c31d8d189ec24d83e25e2c560860f70307b431e"
 Fixed #26243 -- Noted that 'python -R' is enabled by default in Python
 3.3.
 }}}

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.59a225cce76969ae6a1ef7a744ebf826%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26243: Note in deployment checklist that PYTHONHASHSEED is randomized by default as of Python 3.3 (was: Documentation)

2016-02-19 Thread Django

#26243: Note in deployment checklist that PYTHONHASHSEED is randomized by 
default
as of Python 3.3
-+-
 Reporter:  raphaelm |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 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 timgraham):

 * stage:  Unreviewed => 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.5c07d4ce9652a83810c42b7a13d33f77%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26237: uuid.UUID() generates 'invalid syntax' and 'badly formed' uuids

2016-02-19 Thread Django

Comment (by MalikRumi):

1. Thank you for the explanation. I did as you suggested and got the
result you predicted:

In [1]: import uuid

In [2]: uuid.UUID('61877565-5fe5-4175-9f2b-d24704df0b74')
Out[2]: UUID('61877565-5fe5-4175-9f2b-d24704df0b74')

2. As I said in my original report, I had posted to the forums before
coming to you. One answer strongly suggested an issue, which is why I
decided to come to you. However, this morning I see a retraction/further
explanation from him that is more in line with what you said here. So I am
sorry for taking your time, but I thought I had run out of options.

3. What does 'confirmation' of a bug look like?

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.6066127e23a1bcf886bac4c4364e6f3a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26235: POST to delete protected fk relationship raises ProtectedError

2016-02-19 Thread Django

#26235: POST to delete protected fk relationship raises ProtectedError
---+--
 Reporter:  Zelvuska   |Owner:  nobody
 Type:  Bug|   Status:  new
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:  1  |UI/UX:  0
---+--

Comment (by Zelvuska):

 Yes, it seems that #21734 might be related. We have stumbled upon this
 while writing tests for our application.

 But you can trigger this when you just submit the intermediate page that
 states that you cannot delete protected item.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.71adccacf6dec5ceff38cb4359387b98%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26243: Documentation

2016-02-19 Thread Django

#26243: Documentation
-+-
 Reporter:  raphaelm |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:
 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 raphaelm):

 * needs_better_patch:   => 0
 * has_patch:  0 => 1
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 PR is here: https://github.com/django/django/pull/6164

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.35f8a07ee1d55ebb0841556d0db643c1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #2259: Primary keys should be readonly by default in admin

2016-02-19 Thread Django

#2259: Primary keys should be readonly by default in admin
---+
 Reporter:  ed@…   |Owner:
 Type:  Bug|   Status:  new
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 AMaini503):

 * owner:  AMaini503 =>
 * status:  assigned => new


--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.52cff917a255caca9824f3c6898bf638%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26235: POST to delete protected fk relationship raises ProtectedError

2016-02-19 Thread Django

#26235: POST to delete protected fk relationship raises ProtectedError
---+--
 Reporter:  Zelvuska   |Owner:  nobody
 Type:  Bug|   Status:  new
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:  1  |UI/UX:  0
---+--

Comment (by timgraham):

 Is this the actions "delete selected" page as described in #21734? Did you
 skip the intermediate page that checks for protected items?

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.32be958cd16babb079fdb95eb9b6a44b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26243: Documentation

2016-02-19 Thread Django

#26243: Documentation
--+
 Reporter:  raphaelm  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.9
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The deployment checklist mentions the PYTHONHASHSEED variable which is no
 longer relevant as of Python 3.3. We should mention that to avoid
 confusion.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.511e5db2acfbeea1c440f35601f2d773%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26242: Allow to create models with static app_label at import stage.

2016-02-19 Thread Django

#26242: Allow to create models with static app_label at import stage.
---+--
 Reporter:  kramarz|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.9
 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
---+--

Comment (by kramarz):

 My use case is probably silly and not worth of braking your constraints,
 but I believe this PR does not break one about consistency of app registry
 - it just lets you do what could do anyway but earlier. The other
 constraint about importing models after apps is not documented properly
 and I didn't knew about it. ref:
 https://docs.djangoproject.com/en/1.9/ref/applications/#how-applications-
 are-loaded ("Strictly speaking, Django allows importing models once their
 application configuration is loaded")
 
 In my opinion it is not consistient, that models have to magicaly install
 themselves in metaclass while applications are installed manualy using
 INSTALLED_APPS. If it was the app who installs models using in example
 self.installed_models you
 wohttps://code.djangoproject.com/ticket/26242#no4uldn't need any
 additional constraints about import order.
 
 My use case: In my projects i like to have "external api" of application
 in __init__.py Sadly lots of this api uses models. It is just a way to
 have "import models" statement in my __init__.py, apps.py and every module
 they importing from on module level and not copied to every function there
 which obscures readability. I would rather explicit assign app_labels to
 my models.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.1c029b572b493c8766d7ff20ed6cf1ad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25974: switch GIS docs from 3 to 4 spaces indentation

2016-02-19 Thread Django

#25974: switch GIS docs from 3 to 4 spaces indentation
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  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 Tim Graham ):

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


Comment:

 In [changeset:"23e1ad537a5ce4b765f88ab5d2bfee06f773f8c9" 23e1ad53]:
 {{{
 #!CommitTicketReference repository=""
 revision="23e1ad537a5ce4b765f88ab5d2bfee06f773f8c9"
 Fixed #25974 -- Switched GIS docs to 4 spaces indentation.
 }}}

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.a92d8f02cbe2e52b4edf0bd0654d622f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #2259: Primary keys should be readonly by default in admin

2016-02-19 Thread Django

#2259: Primary keys should be readonly by default in admin
---+-
 Reporter:  ed@…   |Owner:  AMaini503
 Type:  Bug|   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 AMaini503):

 * owner:   => AMaini503
 * status:  new => assigned


--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.abaa3bd814c405d07412805cc2df7c86%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26241: collectstatic's output of `skipping x (not modified)` isn't very clear

2016-02-19 Thread Django

#26241: collectstatic's output of `skipping x (not modified)` isn't very clear
-+-
 Reporter:  kezabelle|Owner:  AMaini503
 Type:  Uncategorized|   Status:  assigned
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by AMaini503):

 --> Modified the message as required for more clarity

 Line 267 : collectstatic.py (old)
 {{{
  self.log("Skipping '%s' (not modified)" % path)
 }}}

 Line 267-269 : collecstatic.py (new)
 {{{
 # Message changed to convey the reason clearly as to why the file was
 skipped beca
 # Compares timestamps using --> http_date
 self.log("Skipping '%s' (Dates of last modification are same)" % path)
 }}}

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.ad6df65fc8afa9ce22628bbaab06f3be%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26241: collectstatic's output of `skipping x (not modified)` isn't very clear

2016-02-19 Thread Django

#26241: collectstatic's output of `skipping x (not modified)` isn't very clear
-+-
 Reporter:  kezabelle|Owner:  AMaini503
 Type:  Uncategorized|   Status:  assigned
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by AMaini503):

 * Attachment "26241.diff" 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.6fe8d99d4c41ea3d17846d462b621158%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26242: Allow to create models with static app_label at import stage.

2016-02-19 Thread Django

#26242: Allow to create models with static app_label at import stage.
---+--
 Reporter:  kramarz|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.9
 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 aaugustin):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 > As I understand it django discourage importing models before all apps
 are initialized only because model need to know its 'app_label'.

 This is quite far from being the whole story. Have a look at the mailing
 list discussions about app-loading and at my talk at DjangoCon Europe 2014
 for an explanation of why Django needs to keep a consistent registry of
 models.

 

 This change seems consistent with my intent here:
 https://code.djangoproject.com/ticket/21680#comment:4.

 However I still want to increase consistency of the app registry:
 https://code.djangoproject.com/ticket/21682.

 This would enforce the requirement that models live in an app and are
 imported after their app.

 

 Can you clarify the use case for this change? I'm not sure it's a good
 thing to relax this check.

 I suspect it could reopen some of the bugs the app-loading refactor fixed.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.8237bb4e16586a26c577cedbd758def3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26241: collectstatic's output of `skipping x (not modified)` isn't very clear

2016-02-19 Thread Django

#26241: collectstatic's output of `skipping x (not modified)` isn't very clear
-+-
 Reporter:  kezabelle|Owner:  AMaini503
 Type:  Uncategorized|   Status:  assigned
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by AMaini503):

 * cc: AMaini503 (added)
 * has_patch:  0 => 1
 * type:  New feature => Uncategorized


--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.e0add8226927980f743cb5dcee855efe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26242: Allow to create models with static app_label at import stage.

2016-02-19 Thread Django

#26242: Allow to create models with static app_label at import stage.
---+
 Reporter:  kramarz|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I have submited PR with this change.
 https://github.com/django/django/pull/6163
 As I understand it django discourage importing models before all apps are
 initialized only because model need to know its 'app_label'.
 If app_label  is provided in class Meta it should be ok, but it still
 raises exception.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.512a620c1a2ba22b2dad149be4575650%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26241: collectstatic's output of `skipping x (not modified)` isn't very clear

2016-02-19 Thread Django

#26241: collectstatic's output of `skipping x (not modified)` isn't very clear
-+-
 Reporter:  kezabelle|Owner:  AMaini503
 Type:  New feature  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by AMaini503):

 * owner:  nobody => AMaini503
 * needs_better_patch:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * needs_docs:   => 0


--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.a76d510d2a4efe27a4a98e9f60496187%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #6148: Add generic support for database schemas

2016-02-19 Thread Django

#6148: Add generic support for database schemas
-+-
 Reporter:  ikelly   |Owner:  akaariai
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle postgresql| Triage Stage:  Accepted
  mysql schemas  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 The pull request for this is still missing a couple of day's worth of
 work, but all the hard parts seem to be solved.

 For initial implementation I am going to skip dynamic schemas and other
 useful features which aren't essential for minimal implementation.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.c2167bb0f6ca8af8902e8c023119b639%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26235: POST to delete protected fk relationship raises ProtectedError

2016-02-19 Thread Django

#26235: POST to delete protected fk relationship raises ProtectedError
---+--
 Reporter:  Zelvuska   |Owner:  nobody
 Type:  Bug|   Status:  new
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:  1  |UI/UX:  0
---+--

Comment (by Zelvuska):

 Replying to [comment:1 tedmx]:
 Yes, I understand that and I agree. But I would expect that this
 `ProtectedError` would be caught and handled in the admin. But doing POST
 instead causes `ServerError` which is probably not expected.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.c56c751e4066ce053710f212c891e2b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26235: POST to delete protected fk relationship raises ProtectedError

2016-02-19 Thread Django

#26235: POST to delete protected fk relationship raises ProtectedError
---+--
 Reporter:  Zelvuska   |Owner:  nobody
 Type:  Bug|   Status:  new
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:  1  |UI/UX:  0
---+--
Changes (by tedmx):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Replying to [ticket:26235 Zelvuska]:
 I understand that it is an expected behaviour. `models.PROTECT` prohibits
 deletion of an object in general, and POST is one of these ways.

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.9f0a01d2204304dab4b10897d3fcaacb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25251: Inconsistent availability of data migrations in TransactionTestCase when using --keepdb

2016-02-19 Thread Django

#25251: Inconsistent availability of data migrations in TransactionTestCase when
using --keepdb
---+
 Reporter:  davidszotten   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.8
 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 MoritzS):

 * needs_better_patch:  0 => 1


Comment:

 Left comments on the 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.d8a76574857c4548b86dbb5be910fbfa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26241: collectstatic's output of `skipping x (not modified)` isn't very clear

2016-02-19 Thread Django

#26241: collectstatic's output of `skipping x (not modified)` isn't very clear
-+
Reporter: kezabelle| Owner: nobody
Type: New feature | Status: new
Component: contrib.staticfiles |Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1| UI/UX: 0
-+
Running `manage.py collectstatic` gives output like:
{{{
Skipping 'img/hello.jpg' (not modified)
}}}
Based on that message, it's unclear '''why''' the file was skipped. Is it
because the contents are the same? A hash collision of the filename,
content? Permissions? etc.

It's actually just because the timestamps match,

[https://github.com/django/django/blob/6ca163d7cc451fafd3015fa2ee735d5377fa3065/django/contrib/staticfiles/management/commands/collectstatic.py#L267
as far as I can tell] based on a quick

[https://github.com/django/django/search?q=%22not+modified%22+path%3Adjango%2Fcontrib&type=Code
search], which is absolutely fine, but I had to go to the implementation
to find out what constituted it being unmodified.

I'd like to suggest that the wording be improved/clarified. Perhaps just
something like `modified dates are the same` (I'm not tied to that wording
specifically!).

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.9d5ad87f24ed27e6de74fc151e299a47%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25974: switch GIS docs from 3 to 4 spaces indentation

2016-02-19 Thread Django

#25974: switch GIS docs from 3 to 4 spaces indentation
-+-
 Reporter:  sir-sigurd   |Owner:  sir-
 Type:   |  sigurd
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  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 sir-sigurd):

 * has_patch:  0 => 1


Comment:

 PR -- https://github.com/django/django/pull/6161

--
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.d9bafd5870997a3f1bd11aa55124fbfe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

59 matches

Mail list logo