date:20140131

Re: [Django] #21913: Error 400 without any information if user uploads file to STATIC_ROOT

2014-01-31 Thread Django

#21913: Error 400 without any information if user uploads file to STATIC_ROOT
-+-
 Reporter:  cyborg4006@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  File |  Version:  1.6
  uploads/storage|   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:  upload, 400  | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by cyborg4006@…):

 Oh, I didn't know that there is a detailed documentation on "settings.py"
 file. Thank you.

-- 
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/078.876ba2f6a532f86a733f9171a82b5623%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #8989: Syndication Framework could implement atom:link@rel=self to better follow the recommendations of the RSS Advisory Board

2014-01-31 Thread Django

#8989: Syndication Framework could implement atom:link@rel=self to better follow
the recommendations of the RSS Advisory Board
-+
 Reporter:  xavier.morel@…   |Owner:  arthurk
 Type:  Uncategorized|   Status:  closed
Component:  contrib.syndication  |  Version:  1.1
 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 LaIrZOFDvHvYtJjfI):

 * version:  master => 1.1
 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 http://reglenna.com/doc/#i3b>active ativan pictures of pills -
 ativan generic price

-- 
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/083.8e7e4d528dbf9f9e0736017aaf327926%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21791: RelatedFieldWidgetWrapper object has no attribute decompress

2014-01-31 Thread Django

#21791: RelatedFieldWidgetWrapper object has no attribute decompress
---+--
 Reporter:  DylannCordel   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.6
 Severity:  Normal |   Resolution:  worksforme
 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 timo):

 Here's a [https://github.com/stefanfoulis/cmsplugin-filer/pull/106 pull
 request] for the issue in cmsplugin-filer.

-- 
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.2d18bec3e8ce290c6ea47e768c5e9562%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21921: host_validation_re does not match IPv6 addresses

2014-01-31 Thread Django

#21921: host_validation_re does not match IPv6 addresses
-+--
 Reporter:  sej854+django@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by claudep):

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


Comment:

 The issue about exception differentiation has been addressed in #19866
 (the fix is in Django 1.6).

-- 
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/081.58fe80958fdac3174ad76b06ced0578f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21791: RelatedFieldWidgetWrapper object has no attribute decompress

2014-01-31 Thread Django

#21791: RelatedFieldWidgetWrapper object has no attribute decompress
---+--
 Reporter:  DylannCordel   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.6
 Severity:  Normal |   Resolution:  worksforme
 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 anonymous):

 Just wanted to say this problem rears its head on my project too. Django
 1.6.1, Python 2.7, django-cms beta3, djangocms-filer.

-- 
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.d330ac63fe63324755eed2dd5c44bf77%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21917: Breakage in SQLite migrations

2014-01-31 Thread Django

#21917: Breakage in SQLite migrations
-+
 Reporter:  apollo13 |Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by bmispelon):

 For the record, here's a simplified `models.py` that reproduce the error:
 {{{#!python
 from django.db import models

 class Foo(models.Model):
 bar_fk = models.ForeignKey('Bar', null=True)

 class Bar(models.Model):
 foo_fk = models.ForeignKey('Foo')
 }}}

 I'll also note that the same models work fine on 1.6 with `syncdb`.

-- 
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.1684255d820966efc1581f1a0ed2a9ed%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21903: Query with select_related and defer on MySQL causes id field to be returned as bool

2014-01-31 Thread Django

#21903: Query with select_related and defer on MySQL causes id field to be 
returned
as bool
-+-
 Reporter:  matklad  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by eswenson):

 Didn't mean to be anonymous.

-- 
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.47b9d85a45c19b02af8b4386dc7368ae%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21903: Query with select_related and defer on MySQL causes id field to be returned as bool

2014-01-31 Thread Django

#21903: Query with select_related and defer on MySQL causes id field to be 
returned
as bool
-+-
 Reporter:  matklad  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by anonymous):

 +1 for getting this ticket into a 1.6 point release soon.  We just ran
 into this problem in production. We applied the above-mentioned patch to
 the 1.6.1 sources and have deployed this patched version. We are no longer
 running into the mismatched result row/field tuples.

-- 
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.3d003c7a00d342dfb738847d8f156f52%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21920: Please document mod_python support drop in release notes

2014-01-31 Thread Django

#21920: Please document mod_python support drop in release notes
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.5
 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
---+

Comment (by anonymous):

 mod_python was deprecated in 1.3 and removed in 1.5.

 https://docs.djangoproject.com/en/dev/releases/1.3-alpha-1/#mod-python-
 support

-- 
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.fafebf3bdacff871aba5720027832eb4%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21920: Please document mod_python support drop in release notes

2014-01-31 Thread Django

#21920: Please document mod_python support drop in release notes
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.5
 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
---+

Comment (by anonymous):

 Ok, I'm getting confused maybe. Is mod_python supposed to work with 1.5 ?
 Maybe this is not a documentation issue.

 I'm getting a 500 with that message:

 mod_python (pid=4479, interpreter='xx.com', phase='PythonHandler',
 handler='django.core.handlers.modpython'): Application error
 ServerName: 'xx.com'
 DocumentRoot: '/usr/lib/ngw/static'
 URI: '/'
 Location: None
 Directory: None
 Filename: '/usr/lib/ngw/static/'
 PathInfo: ''
 Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/mod_python/importer.py", line
 1537, in HandlerDispatch\ndefault=default_handler, arg=req,
 silent=hlist.silent)
   File "/usr/lib/python2.7/dist-packages/mod_python/importer.py", line
 1202, in _process_target\nmodule = import_module(module_name,
 path=path)
   File "/usr/lib/python2.7/dist-packages/mod_python/importer.py", line
 304, in import_module\nreturn __import__(module_name, {}, {}, ['*'])
 **ImportError: No module named modpython**

-- 
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.4ea7eb185c203f3ce2a22a5a5bb5fac2%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21920: Please document mod_python support drop in release notes

2014-01-31 Thread Django

Comment (by anonymous):

I'm reading the 1.5 release notes here:
https://docs.djangoproject.com/en/1.5/releases/1.5/

1.5 was the first version to drop mod_python support.

Maybe my English is not good enough, but "deprecation plan" sounds like a
list of features that becomes deprecated, and whose removal is scheduled
sometime in the future.

I maintain 1.5 release notes should says it is broking what used to be one
of the best may to deploy django apps, that is dropping mod_python
support. First line of that page has a link to "backwards incompatible
changes". There is nothing about mod_python there.

(I haven't finish migration to 0.96 version in that big project, yet...)

--
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.b23d59cce47a9703d398785a766e63db%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21892: Remove "string based" RunPython operations.

2014-01-31 Thread Django

#21892: Remove "string based" RunPython operations.
-+-
 Reporter:  loic84   |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Migrations   |  1.7-alpha-1
 Severity:  Release blocker  |   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 timo):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * 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.293204e0fbf0e04146deeb62f768379c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21893: Migrations RunPython operations seem to trip on MTI models.

2014-01-31 Thread Django

#21893: Migrations RunPython operations seem to trip on MTI models.
+---
 Reporter:  loic84  |Owner:
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-alpha-1
 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 timo):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * 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/064.186e0ec75d524073ad3ebd3f18fe8070%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21917: Breakage in SQLite migrations

2014-01-31 Thread Django

#21917: Breakage in SQLite migrations
-+
 Reporter:  apollo13 |Owner:
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   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 timo):

 * 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/066.8da223140112340435dc8b785e99703f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21913: Error 400 without any information if user uploads file to STATIC_ROOT

2014-01-31 Thread Django

#21913: Error 400 without any information if user uploads file to STATIC_ROOT
-+-
 Reporter:  cyborg4006@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  File |  Version:  1.6
  uploads/storage|   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:  upload, 400  | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 I'm sorry you ran into the issue. This is addressed in settings
 documentation for [https://docs.djangoproject.com/en/dev/ref/settings
 /#media-root MEDIA_ROOT]. We're trying not to put a lot of documentation
 in `settings.py`.

-- 
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/078.ecf3d0bb82ea53c1f72242d5e7fdeb83%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21799: loaddata ignorenonexistent should ignore missing models too

2014-01-31 Thread Django

#21799: loaddata ignorenonexistent should ignore missing models too
-+-
 Reporter:  michael.clagett@…|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core |   Resolution:
  (Serialization)| Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  loaddata |  Patch needs improvement:  0
  ignorenonexistent  |UI/UX:  0
Has patch:  0|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * version:  1.6 => master
 * easy:  1 => 0
 * 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/083.4447a0e28d7cb6c35a9a4ac3ab89e03f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] a938ff: Updated some tests to use the check framework and ...

2014-01-31 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a938fff0309d83a64ea588a56bf07984f1436a0e
  
https://github.com/django/django/commit/a938fff0309d83a64ea588a56bf07984f1436a0e
  Author: Tim Graham 
  Date:   2014-01-31 (Fri, 31 Jan 2014)

  Changed paths:
M tests/modeladmin/tests.py

  Log Message:
  ---
  Updated some tests to use the check framework and silenced a 
PendingDeprecationWarning.


-- 
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/52ebe30fc0124_23feacdd48860c2%40hookshot-fe1-pe1-prd.aws.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21908: Misleading documentation in ModelAdmin.get_inline_instances

2014-01-31 Thread Django

#21908: Misleading documentation in ModelAdmin.get_inline_instances
--+
 Reporter:  matt@…|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.6
 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 timo):

 * needs_better_patch:   => 0
 * component:  contrib.admin => Documentation
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 Sure, I'll be happy to review your patch.

-- 
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.47b0479457b8939dd791fd8e484b0a2f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #9025: Nested Inline Support in Admin

2014-01-31 Thread Django

#9025: Nested Inline Support in Admin
---+
 Reporter:  pixelcort  |Owner:
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  Bug?   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+

Comment (by bnafta@…):

 What is current status of this feature?
 Recent changes in django 1.7 will make it somehow easier to do?

-- 
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.c7a955398b85c163f183c5d1c76a23f4%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21848: Some strange problem in Model inheritance and selected_related

2014-01-31 Thread Django

#21848: Some strange problem in Model inheritance and selected_related
-+-
 Reporter:  davydov.ilya@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
  model,inheritance,selected_related |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 Hmmh... maybe this too will be fixed by
 9918c4ac3ec9622631558ef26ebf3919cb69 (see tickets #21903, #21413). I
 can't verify that right now. Trying that
 
https://github.com/akaariai/django/commit/e9a48efe366f1fab7e888cd9648ba69a06bece4a
 fixes the issue would be very helpful.

-- 
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/080.4d5146517a96c87ad0609cf7079b3db9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21848: Some strange problem in Model inheritance and selected_related

2014-01-31 Thread Django

#21848: Some strange problem in Model inheritance and selected_related
-+-
 Reporter:  davydov.ilya@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
  model,inheritance,selected_related |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 I've used
 MySQL-python==1.2.5
 Django 1.6.1

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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/080.1037457fe86869f00abb6bb8bc351548%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21848: Some strange problem in Model inheritance and selected_related

2014-01-31 Thread Django

#21848: Some strange problem in Model inheritance and selected_related
-+-
 Reporter:  davydov.ilya@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
  model,inheritance,selected_related |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 Why did you close this bug?

-- 
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/080.eff03bafae5abcd94f9fee0722d97691%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #3183: manage.py doesn't like international keyboard input

2014-01-31 Thread Django

#3183: manage.py doesn't like international keyboard input
-+-
 Reporter:  mark@…   |Owner:  adrian
 Type:  defect   |   Status:  closed
Component:  Validators   |  Version:  0.96
 Severity:  normal   |   Resolution:
 Keywords:  manage.py,   |  worksforme
  validation | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by oKxejGimcYIbWUsWj):

 * version:  master => 0.96
 * easy:   => 0
 * ui_ux:   => 0


Comment:

 http://reglenna.com/doc/#tepu9r>continue ativan usage -
 lorazepam 1 mg anxiety

-- 
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/075.cfea2f4cc2cf794a6e5720d3301aab59%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21921: host_validation_re does not match IPv6 addresses

2014-01-31 Thread Django

#21921: host_validation_re does not match IPv6 addresses
-+--
 Reporter:  sej854+django@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
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 anonymous):

 Possibly! I came across this when trying to figure out why our provider's
 was flooded by e-mails -- some automatic script searching for
 vulnerabilities tried out all sorts of addresses, and because of the mis-
 matching host_validation_re Django sent one e-mail to me for each request
 -- I wouldn't say it was totally wrong to raise SuspiciousOperation
 exceptions in this case (it ''was'' a suspicious operation), but there
 should be some way to prevent just this kind of exception to be e-mailed
 to the admin, without having to disable all Exception mails (according to
 the django logging documentation it should be possible to deal with sub-
 categories of SuspiciousOperation, but the code in http/request.py only
 raises SuspiciousOperation(), so I can't see how you'd filter out just the
 mismatches to the Host: validation). Otherwise this can result in a (not
 even intentional) denial of service...

-- 
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/081.5ea39320e0d9d4fbfecf84983c855398%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21921: host_validation_re does not match IPv6 addresses

2014-01-31 Thread Django

#21921: host_validation_re does not match IPv6 addresses
-+--
 Reporter:  sej854+django@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
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 claudep):

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


Comment:

 I find a bit strange that your Host value doesn't contain the brackets
 (the RFC requires them, http://tools.ietf.org/html/rfc3986#section-3.2.2).
 Is it the client who didn't set the brackets?

-- 
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/081.2125ed41036cc6f499a4c2c04ad0bb57%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21911: Admin login can cause data loss

2014-01-31 Thread Django

#21911: Admin login can cause data loss
-+
 Reporter:  pennersr |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by claudep):

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


Comment:

 See https://github.com/django/django/pull/2226

-- 
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.188a06aa0c66078f6a416cd80085abdf%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21920: Please document mod_python support drop in release notes

2014-01-31 Thread Django

Comment (by timo):

We don't typically repeat the list of deprecated features in the release
notes, rather just say "We’ve also dropped some features, which are
detailed in our deprecation plan" (with deprecation plan linked to the
appropriate page). However, I noticed that in the development version of
the docs, the deprecation timeline has been truncated so the list of
features removed in 1.5 has been removed so if you're reading the 1.5
release notes in a newer version of the docs, you may not be able to find
what you're looking for. Thus, we may want to rethink how we structure
this.

--
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.f376f91ee068b84a03784b0303edee40%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21918: Ordering changing order_by behavior

2014-01-31 Thread Django

#21918: Ordering changing order_by behavior
-+-
 Reporter:  hugotacito@… |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  ordering |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by hugotacito@…):

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


Comment:

 Sorry, had some problems in my application that did this. Closing...

-- 
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/078.3354d3cddbc135fc7043029ba97b9755%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21920: Please document mod_python support drop in release notes

2014-01-31 Thread Django

#21920: Please document mod_python support drop in release notes
---+
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.5
 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 mjtamlyn):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 It had been documented as deprecated in 1.2, 1.3 and 1.4, but nonetheless
 it should be in the release notes.

-- 
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.9a935570f006288650e484c621ab7d99%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21921: host_validation_re does not match IPv6 addresses

2014-01-31 Thread Django

#21921: host_validation_re does not match IPv6 addresses
-+
 Reporter:  sej854+django@…  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  HTTP handling|Version:  master
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Validation of the host part fails, falsely raising SuspiciousOperation

 validate_host() or split_domain_port() in django.http.request try to match
 the Host: value against the following RegExp:

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

 The issue are the \[ \] (literal square brackets) around the IPv6 part --
 the Host: value actually does not contain them. Hence it fails to match
 any IPv6 address.
 In my local installation I removed the source of the problem by adding
 question marks after the \[ and \], but of course it'd be better if it
 could be fixed properly in the code base.

 I encountered this problem in a django 1.3.7 install, but checked the
 github
 
(https://github.com/django/django/blob/c250f9c99b59bb011dae9bc97783458621462b65/django/http/request.py)
 to confirm that this problem hasn't changed.

 Let me know if you need any additional information.

-- 
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.3cfb52b9e015bf968f25b92b8cab1fa8%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21920: Please document mod_python support drop in release notes

2014-01-31 Thread Django

#21920: Please document mod_python support drop in release notes
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.5
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 After upgrading to 1.5, I gave that error:
 ImportError: No module named modpython

 I would have switch to wsgi before upgrading to 1.5, had I known.

 Please do add this important change in release notes.

-- 
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.719743de961359134ff744ed3aeccf62%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21918: Ordering changing order_by behavior

2014-01-31 Thread Django

#21918: Ordering changing order_by behavior
-+-
 Reporter:  hugotacito@… |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  ordering |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by akaariai):

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


Comment:

 Do you get different ordering for the
 `Year.objects.all().order_by('-year')` query if you remove the Meta
 ordering attribute? If I recall correctly this shouldn't happen.

-- 
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/078.dfaa461ea07bb930a69ab573b409077b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21919: As you can see, simply understanding your insurance business can be a helpful device in getting the best care achievable. Doing your explore genuinely pays off of within the long run,

2014-01-31 Thread Django

#21919: As you can see, simply understanding your insurance business can be a
helpful device in getting the best care achievable. Doing your explore
genuinely pays off of within the long run, and inquiring queries can help
you evade any surprise bills. That you are responsible for your health, and
realizing methods to handle your insurance organization is a part of this!
---+---
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.6
 Severity:  Normal |   Keywords:  GARCINIA CAMBOGIA MIRACLE
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+---
 In occurrence you do not acquire unsurpassable wellbeing, head certain to
 outlet close to with antithetical insurance companies. Agencies all human
 diverse standards they use for their uncomparable probability levels. Both
 enable higher sterol premiums or higher BMI's in their policies. When you
 change around the boundary, it's notable of your case and healthiness to
 work who present offer you the top discounts at your contempor GARCINIA
 CAMBOGIA MIRACLE

 {Prioritize your issues. Do you would suchlike to thrust having a unique
 theologizer or boilersuit health repair artifact? Can you necessity the
 most inexpensive premiums? Can you hump meticulous coverall eudaimonia
 requirements that impoverishment to be addressed? Whenever you generate a
 itemize of your priorities, you are fit to intolerant set the sort of
 overall welfare protection companies that pass to be perfect to your
 needs.
 When selecting the conservative coverall upbeat contract policy for you
 and your home, it truly is unbelievably crucial to work around and explore
 the variant ones. Choosing the top valued eudaemonia and wellness shelter
 can provide reserve you hundreds or flatbottomed thousands of dollars per
 year. The toll cost fund from put to neaten can be real striking.
 In case you are self-employed, you should at all times figure your
 coverall welfare insurance payments for tax purposes. This is the
 individual way to save your self a brobdingnagian total of payment at tax
 case. Eudaimonia insurance payments are expropriated as above-the-line
 deductions, and they inform the turn of your familiarized gross income no
 concern if or not you decide to itemize.
 Numerous colleges and universities request unit coverall eudaimonia
 contract policies, so in the circumstance you aren't smothered below your
 parents' insurance, this may be the primo way to get relatively cheap
 contract. Quite a few alumni organizations acquaint grouping insurance to
 graduates, thus you can use this to raft with you after your high from
 school and good before you get employer shelter.
 It's potential the mercantilism you utilize for welfare and eudaemonia
 shelter to has looked at your examination history, if forthcoming, ripe
 before they order you to definitely put to-up on your own app.
 Consequently they instrument screw you are prevarication as presently time
 you do it, invalidating your exercise directly. Closing honesty faculty
 get reliable that your app is approved and you also invite reporting.
 Seem strongly at your boilersuit upbeat idea's prescription aegis. It may
 change from twelvemonth to twelvemonth, and a medicament medicament which
 was once beaded could perhaps be dropped at any assumption dimension. In
 the circumstance you get particular drugs regularly, you necessary to piss
 sure that they are ease arillate by your pose so you do not get cragfast
 with a prodigious eyeshade.
 Change your eudaemonia protection contract to agree your requirements and
 eff your premiums as very low as thinkable. For occurrence, few policies
 direct many for relationship mind. If you are a solitary male, you do not
 duty that indorsement. Deleting it may reduction your premiums. Only
 select the health and eudaemonia contract selections that you
 pauperization so that the disbursal of insurance is minimized.
 If an coverall health protection organisation representative asks you an
 take to which you do not interpret the response, swan them so. There is no
 shame in recital them which you are unsure of what they are asking, and
 they staleness ring your physician to tally the suitable respond. They may
 seem frustrated, but that's okay. Don't let it pain you. GARCINIA CAMBOGIA
 MIRACLE

 As you can see, just apprehension your shelter mercantilism can be a
 reformative pattern in effort the mortal charge realizable. Doing your
 explore really pays off of within the monthlong run, and investigatory
 queries can aid you bilk any surprise bills. That you are judicious for
 your welfare, and realizing methods to manipulate your insurance activity
 is a relation of this!
 [http://garciniacambogiamiraclereview.com/
 ]

-

[Django] #21918: Ordering changing order_by behavior

2014-01-31 Thread Django

#21918: Ordering changing order_by behavior
--+--
 Reporter:  hugotacito@…  |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.5
 Severity:  Normal|   Keywords:  ordering
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 Not sure if its a bug, but i am having this problem:

 models.py
 {{{
 class Year(models.Model):
year = models.IntegerField(unique=True)
class Meta:
 ordering = ['-year']
 }}}


 views.py
 {{{
 def list_years(request):
year = Year.objects.all().order_by('-year')
...
 }}}


 The problem is that the order_by is returning ascending probably because
 of the ordering from the meta class. In my opinion the order_by should not
 be affected by the ordering attribute from the meta class for clarity.

-- 
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/063.1d2f99b05ea54fe2746b1e8795ef9557%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #21917: Breakage in SQLite migrations

2014-01-31 Thread Django

#21917: Breakage in SQLite migrations
---+
   Reporter:  apollo13 |  Owner:
   Type:  Bug  | Status:  new
  Component:  Migrations   |Version:  master
   Severity:  Release blocker  |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 Error:
 {{{
 Applying oversight.0001_logentry_sensor...Traceback (most recent call
 last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File
 "/home/florian/sources/django.git/django/core/management/__init__.py",
 line 427, in execute_from_command_line
 utility.execute()
   File
 "/home/florian/sources/django.git/django/core/management/__init__.py",
 line 419, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/home/florian/sources/django.git/django/core/management/base.py",
 line 287, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/home/florian/sources/django.git/django/core/management/base.py",
 line 336, in execute
 output = self.handle(*args, **options)
   File
 "/home/florian/sources/django.git/django/core/management/commands/migrate.py",
 line 145, in handle
 executor.migrate(targets, plan, fake=options.get("fake", False))
   File
 "/home/florian/sources/django.git/django/db/migrations/executor.py", line
 60, in migrate
 self.apply_migration(migration, fake=fake)
   File
 "/home/florian/sources/django.git/django/db/migrations/executor.py", line
 94, in apply_migration
 migration.apply(project_state, schema_editor)
   File
 "/home/florian/sources/django.git/django/db/migrations/migration.py", line
 97, in apply
 operation.database_forwards(self.app_label, schema_editor,
 project_state, new_state)
   File
 "/home/florian/sources/django.git/django/db/migrations/operations/fields.py",
 line 35, in database_forwards
 field,
   File
 "/home/florian/sources/django.git/django/db/backends/sqlite3/schema.py",
 line 95, in add_field
 raise ValueError("You cannot add a null=False column without a default
 value on SQLite.")
 ValueError: You cannot add a null=False column without a default value on
 SQLite.
 }}}

 Models:
 {{{
 from django.db import models
 from django.utils.timezone import now


 class Sensor(models.Model):
 name = models.CharField(max_length=255)
 api_endpoint = models.SlugField()
 unit = models.CharField(max_length=255)
 sensor_class = models.CharField(max_length=255)
 params = models.TextField()
 current_log = models.ForeignKey('LogEntry', null=True,
 related_name='+')

 def __unicode__(self):
 return self.name


 class LogEntry(models.Model):
 datetime = models.DateTimeField(default=now)
 sensor = models.ForeignKey(Sensor)
 value = models.CharField(max_length=255)
 }}}

 Migrations generated by makemigrations:
 {{{
 # encoding: utf8
 from django.db import models, migrations
 import django.utils.timezone


 class Migration(migrations.Migration):

 dependencies = [
 ]

 operations = [
 migrations.CreateModel(
 name='LogEntry',
 fields=[
 (u'id', models.AutoField(verbose_name=u'ID',
 serialize=False, auto_created=True, primary_key=True)),
 ('datetime',
 models.DateTimeField(default=django.utils.timezone.now)),
 ('value', models.CharField(max_length=255)),
 ],
 options={
 },
 bases=(models.Model,),
 ),
 migrations.CreateModel(
 name='Sensor',
 fields=[
 (u'id', models.AutoField(verbose_name=u'ID',
 serialize=False, auto_created=True, primary_key=True)),
 ('name', models.CharField(max_length=255)),
 ('api_endpoint', models.SlugField()),
 ('unit', models.CharField(max_length=255)),
 ('sensor_class', models.CharField(max_length=255)),
 ('params', models.TextField()),
 ('current_log', models.ForeignKey(to='oversight.LogEntry',
 to_field=u'id', null=True)),
 ],
 options={
 },
 bases=(models.Model,),
 ),
 ]
 }}}
 and:
 {{{
 # encoding: utf8
 from django.db import models, migrations


 class Migration(migrations.Migration):

 dependencies = [
 ('oversight', '0001_initial'),
 ]

 operations = [
 migrations.AddField(
 model_name='logentry',
 name='sensor',
 field=models.ForeignKey(to='oversight.Sensor',
 to_field=u'id'),
 preserve_default=True,
 ),

Re: [Django] #17943: Too many open file descriptors while using memcache

2014-01-31 Thread Django

#17943: Too many open file descriptors while using memcache
-+-
 Reporter:  m.gajda@…|Owner:  haxoza
 Type:  Bug  |   Status:  assigned
Component:  Core (Cache system)  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  cache memcache open  | Triage Stage:  Accepted
  file descriptors   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by m.gajda@…):

 I have recently updated my Django environment to 1.5.5, and then to 1.6.1.
 In both cases the above mentioned issues still persists. The patch
 attached helps.

-- 
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/077.4050e0189a5ba92e834c81c1c54bab0c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #15619: Logout link should be protected

2014-01-31 Thread Django

#15619: Logout link should be protected
--+--
 Reporter:  void  |Owner:  ashchristopher
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  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 Gwildor):

 * cc: Gwildor (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/062.64202e070736454c6f4ccc821d7afa66%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #15667: Implement template-based widget rendering

2014-01-31 Thread Django

#15667: Implement template-based widget rendering
+
 Reporter:  brutasse|Owner:  brutasse
 Type:  New feature |   Status:  new
Component:  Forms   |  Version:
 Severity:  Normal  |   Resolution:
 Keywords:  form-rendering  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+
Changes (by Gwildor):

 * cc: Gwildor (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.078b3ed52d3ffc1ee6d6dd3091576d6c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #9025: Nested Inline Support in Admin

2014-01-31 Thread Django

#9025: Nested Inline Support in Admin
---+
 Reporter:  pixelcort  |Owner:
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  Bug?   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+
Changes (by Gwildor):

 * cc: Gwildor (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.e6946870392d0b045d507d8e0cc2014f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21911: Admin login can cause data loss

2014-01-31 Thread Django

#21911: Admin login can cause data loss
-+
 Reporter:  pennersr |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.4
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by claudep):

 Currently, the `staff_member_required` decorator allows to post login data
 to any admin view to log in a user. I am not a fan of this functionality,
 but changing this would have to be documented as a backwards
 incompatibility.
 This is mainly tested in
 
[[https://github.com/django/django/blob/stable/1.6.x/tests/admin_views/tests.py#L1593|SecureViewTests]].

-- 
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.cc14172b2689f5d2191539ecd73353d1%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21911: Admin login can cause data loss

2014-01-31 Thread Django

#21911: Admin login can cause data loss
-+
 Reporter:  pennersr |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.4
 Severity:  Release blocker  |   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 pennersr):

 * cc: raymond.penners@… (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.97db04bbf34afb4d23152cb5b78f6dcc%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

41 matches

Mail list logo