Re: [Django] #3591: add support for custom app_label and verbose_name

[Django]

#3591: add support for custom app_label and verbose_name
-+-
 Reporter:  jkocherhans  |Owner:  adrian
 Type:  New feature  |   Status:  reopened
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Fixed on
Has patch:  1|  a branch
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  1
-+-
Changes (by mjtamlyn):

 * cc: marc.tamlyn@… (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18448: Rename all documentation files to have .rst extension

[Django]

#18448: Rename all documentation files to have .rst extension
--+
 Reporter:  mjtamlyn  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 All of the docs files are written in reStructuredText, and should probably
 have the correct extension. Whilst of course one can configure a text
 editor to use rst syntax highlighting etc, for the new contributor they
 may not realise to do this.

 To be honest, when I first downloaded the docs I was unsure whether the
 .txt files were actually the docs given that Sphinx docs are written in
 rst.

 Git understands renaming files pretty well, so it should be ok to do this
 even for people with edits to the file - they should all merge in
 correctly (with a bit of luck).

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18447: LazyObject doesn't unwrap on dict access

[Django]

#18447: LazyObject doesn't unwrap on dict access
---+
 Reporter:  FunkyBob   |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  1
Easy pickings:  1  |  UI/UX:  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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16965: Model Formsets can_delete documentation lacking actual use example

[Django]

#16965: Model Formsets can_delete documentation lacking actual use example
-+-
 Reporter:  gregcorey@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  can_delete,  | Triage Stage:  Accepted
  documentation, model formset   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by amanjeev):

 Formsets can_delete online documentation provides no example of how to
 utilize this parameter to ''actually delete a form''

 When you say "actually delete a form", you mean delete the object that,
 that particular form relates to, correct?

 I just want to make sure that we are not deleting a form from the front-
 end end. Rather, this is a feature that is used to delete the object.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18432: Chained foreign keys with to_field produce incorrect query

[Django]

#18432: Chained foreign keys with to_field produce incorrect query
-+-
 Reporter:  lwarx|Owner:  Spark23
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by lwarx):

 Thanks a lot!

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[django/django] f269f3: Small corrections to committing-code docs

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f269f305444f3c972e74755e9adff5ef575401d5
  
https://github.com/django/django/commit/f269f305444f3c972e74755e9adff5ef575401d5
  Author: Luke Plant 
  Date:   2012-06-07 (Thu, 07 Jun 2012)

  Changed paths:
M docs/internals/contributing/committing-code.txt

  Log Message:
  ---
  Small corrections to committing-code docs



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18125: Using filters in if tag example is misleading

[Django]

#18125: Using filters in if tag example is misleading
---+
 Reporter:  ebrelsford@…   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4
 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 ebrelsford@…):

 * has_patch:  0 => 1


Comment:

 I've attached my attempt at making a caveat. I'm new at contributing and
 documentation, so please let me know if I need to change anything.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18272: ModelChoiceField's queryset attribute persists between two form instances

[Django]

#18272: ModelChoiceField's queryset attribute persists between two form 
instances
-+-
 Reporter:  bmispelon|Owner:  Spark23
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  modelchoicefield | Triage Stage:
  deepcopy   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Spark23):

 * owner:  nobody => Spark23
 * needs_docs:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * needs_better_patch:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18436: Review references to Subversion given github move

[Django]

#18436: Review references to Subversion given github move
-+-
 Reporter:  mjtamlyn |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  svn, subversion, | Triage Stage:  Accepted
  docs   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 I killed two birds with one stone :)

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18436: Review references to Subversion given github move

[Django]

#18436: Review references to Subversion given github move
-+-
 Reporter:  mjtamlyn |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  svn, subversion, | Triage Stage:  Accepted
  docs   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ptone):

 * status:  reopened => closed
 * resolution:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18307: Git workflow guidelines

[Django]

#18307: Git workflow guidelines
--+
 Reporter:  akaariai  |Owner:  akaariai
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.3
 Severity:  Normal|   Resolution:  fixed
 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 ptone):

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


Comment:

 fixed in:

 
https://github.com/django/django/commit/90fb6a46485d4f3c70d3864ab0a0e2f619449d31

 Aymeric Augustin :

 "Updated contributing docs for git.

 Most of the credit for this large patch goes to Anssi Kääriäinen.
 Many thanks to all the people who contributed to the discussion."

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18436: Review references to Subversion given github move

[Django]

#18436: Review references to Subversion given github move
-+-
 Reporter:  mjtamlyn |Owner:  nobody
 Type:  New feature  |   Status:  reopened
Component:  Documentation|  Version:
 Severity:  Release blocker  |   Resolution:
 Keywords:  svn, subversion, | Triage Stage:  Accepted
  docs   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ptone):

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


Comment:

 
https://github.com/django/django/commit/90fb6a46485d4f3c70d3864ab0a0e2f619449d31

 refs the wrong ticket number in the commit message

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18446: Revisions to 'Working with forms' topic docs

[Django]

#18446: Revisions to 'Working with forms' topic docs
--+
 Reporter:  aroy  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I did some text editing/cleanup on the 'Working with forms' topic docs
 (https://docs.djangoproject.com/en/1.4/topics/forms/#using-a-form-
 in-a-view).  No code or meaning is changed.  The text is just more
 readable now.
 https://github.com/django/django/pull/128

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18445: Very minor link added

[Django]

#18445: Very minor link added
--+
 Reporter:  anonymous |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  closed
Component:  Documentation |Version:  master
 Severity:  Normal| Resolution:  fixed
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+
Changes (by Aymeric Augustin ):

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


Comment:

 In [33999d9871f9a0484190494e83d4a7e22e063e54]:
 {{{
 #!CommitTicketReference repository=""
 revision="33999d9871f9a0484190494e83d4a7e22e063e54"
 Fixed #18445 -- Added a links in the docs.

 Thanks Audrey Roy for the 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[django/django] 33999d: Fixed #18445 -- Added a links in the docs.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 33999d9871f9a0484190494e83d4a7e22e063e54
  
https://github.com/django/django/commit/33999d9871f9a0484190494e83d4a7e22e063e54
  Author: Aymeric Augustin 
  Date:   2012-06-07 (Thu, 07 Jun 2012)

  Changed paths:
M AUTHORS
M docs/ref/forms/validation.txt
M docs/topics/forms/modelforms.txt

  Log Message:
  ---
  Fixed #18445 -- Added a links in the docs.

Thanks Audrey Roy for the patch.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18445: Very minor link added

[Django]

#18445: Very minor link added
--+
 Reporter:  anonymous |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Here, I turned text that said "form validation" into a link to the Form
 Validation page:
 
https://github.com/audreyr/django/commit/6ccd876f9020748bb7d4e7ce432d190c7ed425f7

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18444: Replace hard coded "View on Site" URLs

[Django]

#18444: Replace hard coded "View on Site" URLs
-+-
 Reporter:  dhepper  |Owner:  dhepper
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by dhepper):

 * owner:  nobody => dhepper
 * needs_better_patch:   => 0
 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

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

[Django]

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

Comment (by akaariai):

 I agree on simplifying the Oracle hacks in the patch. The current patch
 tries to abstract too much of the differences between the databases away.
 Lets rip the current patch to absolute minimum, and then continue from
 there.

 The "multiple schemas on Oracle -> multiple defined connections" needs
 some more thought on how to map the tables to the connections, and how to
 see that some aliases are just schemas for another alias, so that joins
 are allowed, and one can save model in schema "other" using the default
 connection. I hope this can be made to work...

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18443: Import string/numeric types from py3.py

[Django]

#18443: Import string/numeric types from py3.py
-+
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Python 3 |  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
-+

Comment (by claudep):

 Pull request is https://github.com/django/django/pull/129

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18444: Replace hard coded "View on Site" URLs

[Django]

#18444: Replace hard coded "View on Site" URLs
--+
 Reporter:  dhepper   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  contrib.admin |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The URLs of the "View on Site" button on the change form and inline admins
 is hardcoded. They should be replaced with a reversed URLs.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18443: Import string/numeric types from py3.py

[Django]

#18443: Import string/numeric types from py3.py
---+
   Reporter:  claudep  |  Owner:  nobody
   Type:  New feature  | Status:  new
  Component:  Python 3 |Version:  master
   Severity:  Normal   |   Keywords:
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 Now that we have the django/utils/py3.py layer, the next step is to use it
 to import Python 2/3 compatible string and numeric types.

 See also https://docs.djangoproject.com/en/dev/topics/python3/#renamed-
 types

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

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

[Django]

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

Comment (by ikelly):

 Catching up now on this ticket, I'll try to do some testing on Oracle
 soon.

 I want to suggest that we also consider foreign-schema creation to be out
 of scope for databases like Oracle, where schemas and users are the same
 things.  The current code that attempts to do all this through a single
 configured Oracle connection is a bit naive; it assumes that all users
 have the same password, and it appears to also assume that the configured
 Django user has the CREATE ANY TABLE privilege, which would be an unusual
 production setup.

 Instead, a Django user who wants to manage multiple Oracle schemas with
 Django should set up a separate database connection for each schema.  This
 way we're not trying to create or alter objects belonging to other users.
 For the REFERENCES issue, there are two cases -- either the foreign schema
 is not also managed by Django, in which case the user is responsible for
 ensuring the necessary grants, or both schemas are managed by Django, in
 which case we might better be able to automate the grant with the using()
 construct.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18433: "View on site" does not work in InlineModelAdmin when using custom primary key field

[Django]

#18433: "View on site" does not work in InlineModelAdmin when using custom 
primary
key field
+
 Reporter:  jurgeni |Owner:  dhepper
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  1.4
 Severity:  Normal  |   Resolution:
 Keywords:  admin template  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by dhepper):

 * has_patch:  0 => 1


Comment:

 Patch available on GitHub: https://github.com/django/django/pull/127

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17933: "Writing documentation" needs link to check out documentation

[Django]

#17933: "Writing documentation" needs link to check out documentation
--+
 Reporter:  rmattb|Owner:  westfeld
 Type:  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:  1 |UI/UX:  0
--+
Changes (by Aymeric Augustin ):

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


Comment:

 In [6a66fc08b3a1e3ec56e05cd48647060ac3a4da94]:
 {{{
 #!CommitTicketReference repository=""
 revision="6a66fc08b3a1e3ec56e05cd48647060ac3a4da94"
 Fixed #17933 -- Added a missing label to the docs.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[django/django] 6a66fc: Fixed #17933 -- Added a missing label to the docs.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6a66fc08b3a1e3ec56e05cd48647060ac3a4da94
  
https://github.com/django/django/commit/6a66fc08b3a1e3ec56e05cd48647060ac3a4da94
  Author: Aymeric Augustin 
  Date:   2012-06-07 (Thu, 07 Jun 2012)

  Changed paths:
M docs/intro/whatsnext.txt

  Log Message:
  ---
  Fixed #17933 -- Added a missing label to the docs.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17933: "Writing documentation" needs link to check out documentation

[Django]

#17933: "Writing documentation" needs link to check out documentation
--+
 Reporter:  rmattb|Owner:  westfeld
 Type:  Cleanup/optimization  |   Status:  reopened
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:  1 |UI/UX:  0
--+
Changes (by aaugustin):

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


Comment:

 This commit contains a reference to a "differences-between-doc-versions"
 label, but no such label exists in the the docs.

 I thought that I had inadvertently removed this label during my extensive
 changes to the "contributing" section of the docs (#18436), but that
 doesn't appear to be true. Actually I couldn't find any such label in
 Django's history:

 {{{
 % git log -Sdifferences-between-doc-versions
 commit 87ff89d12d109066ff355ed267787d32a6b5aeb7
 Author: Adrian Holovaty 
 Date:   Thu Jun 7 11:32:28 2012 -0500

 Fixed #17933 -- Added intro note to writing-documentation.txt
 Based on initial patch by Thomas Westfeld
 }}}

 I suppose that some of the intended changes are missing in the final
 commit. I'm going to add the label at the most plausible location. You may
 want to check that there are no other missing pieces.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #7623: Multi-table inheritance does not allow linking new instance of child model to existing parent model instance.

[Django]

#7623: Multi-table inheritance does not allow linking new instance of child 
model
to existing parent model instance.
-+-
 Reporter:  brooks.travis@…  |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  model-inheritance,   |  decision needed
  multi-table-inheritance|  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by carbonXT):

 * cc: mike@… (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17209: Dogfood class-based views in contrib.auth

[Django]

#17209: Dogfood class-based views in contrib.auth
-+-
 Reporter:  melinath |Owner:  andrews
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  contrib.auth |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  class-based views|  Needs documentation:  0
  admin auth |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by bmispelon):

 After two minor modifications, I've got all the tests passing on my fork.

 There are still a few things I'd like to improve, mostly around the
 redirection logic in LoginView and LogoutView (it's still messy).

 I've had a hard time wrapping my head around the flow of the function-
 based logout view. I'd appreciate it if someone could make sure I did
 actually replicate it.

 I also have a few questions:

 * LogoutView: For now, it inherits from TemplateView. Does it make more
 sense to inherit from RedirectView (RedirectView has the nice advantage of
 dispatching POST, OPTIONS, DELETE, and PUT to GET)? Or maybe simply View?

 * PasswordResetConfirmView: as mentionned in the comment on the code,
 there is a potential backwards-compatibility issue. It should not be too
 hard to correct it but is it really a problem?

 * Backwards-compatible stubs: the approach I took to ensure backwards-
 compatibility was to create function based wrappers around the class-based
 views. Is this a good approach?

 * How do I approach writing tests for these new class-based views? I'm
 having a hard time determining what should be tested and how.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18436: Review references to Subversion given github move

[Django]

#18436: Review references to Subversion given github move
-+-
 Reporter:  mjtamlyn |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Documentation|  Version:
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  svn, subversion, | Triage Stage:  Accepted
  docs   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [90fb6a46485d4f3c70d3864ab0a0e2f619449d31]:
 {{{
 #!CommitTicketReference repository=""
 revision="90fb6a46485d4f3c70d3864ab0a0e2f619449d31"
 Fixed #18436 -- Updated contributing docs for git.

 Most of the credit for this large patch goes to Anssi Kääriäinen.
 Many thanks to all the people who contributed to the discussion.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[django/django] 90fb6a: Fixed #18436 -- Updated contributing docs for git.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 90fb6a46485d4f3c70d3864ab0a0e2f619449d31
  
https://github.com/django/django/commit/90fb6a46485d4f3c70d3864ab0a0e2f619449d31
  Author: Aymeric Augustin 
  Date:   2012-06-07 (Thu, 07 Jun 2012)

  Changed paths:
M docs/index.txt
M docs/internals/contributing/bugs-and-features.txt
M docs/internals/contributing/committing-code.txt
R docs/internals/contributing/writing-code/branch-policy.txt
M docs/internals/contributing/writing-code/index.txt
M docs/internals/contributing/writing-code/submitting-patches.txt
M docs/internals/contributing/writing-code/unit-tests.txt
A docs/internals/contributing/writing-code/working-with-git.txt
A docs/internals/git.txt
M docs/internals/index.txt
M docs/internals/release-process.txt
R docs/internals/svn.txt

  Log Message:
  ---
  Fixed #18436 -- Updated contributing docs for git.

Most of the credit for this large patch goes to Anssi Kääriäinen.
Many thanks to all the people who contributed to the discussion.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18432: Chained foreign keys with to_field produce incorrect query

[Django]

#18432: Chained foreign keys with to_field produce incorrect query
-+-
 Reporter:  lwarx|Owner:  Spark23
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jannis Leidel ):

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


Comment:

 In [1a412dda621d8623abb91f8687f52de30a79901a]:
 {{{
 #!CommitTicketReference repository=""
 revision="1a412dda621d8623abb91f8687f52de30a79901a"
 Fixed #18432 -- Prevented the ForeignKey field from creating an invalid
 query when chained. Thanks, Jann Kleen.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[django/django] 1a412d: Fixed #18432 -- Prevented the ForeignKey field fro...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1a412dda621d8623abb91f8687f52de30a79901a
  
https://github.com/django/django/commit/1a412dda621d8623abb91f8687f52de30a79901a
  Author: Jann Kleen 
  Date:   2012-06-07 (Thu, 07 Jun 2012)

  Changed paths:
M django/db/models/fields/related.py
M tests/regressiontests/model_regress/models.py
M tests/regressiontests/model_regress/tests.py

  Log Message:
  ---
  Fixed #18432 -- Prevented the ForeignKey field from creating an invalid query 
when chained. Thanks, Jann Kleen.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18432: Chained foreign keys with to_field produce incorrect query

[Django]

#18432: Chained foreign keys with to_field produce incorrect query
-+-
 Reporter:  lwarx|Owner:  Spark23
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jezdez):

 * status:  closed => reopened
 * resolution:  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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18432: Chained foreign keys with to_field produce incorrect query

[Django]

#18432: Chained foreign keys with to_field produce incorrect query
-+-
 Reporter:  lwarx|Owner:  Spark23
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Spark23):

 * status:  assigned => closed
 * has_patch:  0 => 1
 * resolution:   => fixed
 * stage:  Unreviewed => Ready for checkin


Comment:

 fixed in pull request #126 on github

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18363: Add a compatibility layer for Python 3

[Django]

#18363: Add a compatibility layer for Python 3
-+
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Python 3 |  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 Claude Paroz ):

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


Comment:

 In [5e6ded2e58597fa324c550bad35a30ee630ce223]:
 {{{
 #!CommitTicketReference repository=""
 revision="5e6ded2e58597fa324c550bad35a30ee630ce223"
 Fixed #18363 -- Added Python 3 compatibility layer.

 Thanks Vinay Sajip for the support of his django3 branch
 and Alex Gaynor, kezabelle, YorikSar for the review.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[django/django] 5e6ded: Fixed #18363 -- Added Python 3 compatibility layer...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5e6ded2e58597fa324c550bad35a30ee630ce223
  
https://github.com/django/django/commit/5e6ded2e58597fa324c550bad35a30ee630ce223
  Author: Claude Paroz 
  Date:   2012-06-07 (Thu, 07 Jun 2012)

  Changed paths:
A django/utils/py3.py
M docs/index.txt
M docs/ref/unicode.txt
M docs/topics/index.txt
A docs/topics/python3.txt

  Log Message:
  ---
  Fixed #18363 -- Added Python 3 compatibility layer.

Thanks Vinay Sajip for the support of his django3 branch
and Alex Gaynor, kezabelle, YorikSar for the review.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17933: "Writing documentation" needs link to check out documentation

[Django]

#17933: "Writing documentation" needs link to check out documentation
--+
 Reporter:  rmattb|Owner:  westfeld
 Type:  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:  1 |UI/UX:  0
--+
Changes (by Adrian Holovaty ):

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


Comment:

 In [87ff89d12d109066ff355ed267787d32a6b5aeb7]:
 {{{
 #!CommitTicketReference repository=""
 revision="87ff89d12d109066ff355ed267787d32a6b5aeb7"
 Fixed #17933 -- Added intro note to writing-documentation.txt
 Based on initial patch by Thomas Westfeld
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[django/django] 87ff89: Fixed #17933 -- Added intro note to writing-docume...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 87ff89d12d109066ff355ed267787d32a6b5aeb7
  
https://github.com/django/django/commit/87ff89d12d109066ff355ed267787d32a6b5aeb7
  Author: Adrian Holovaty 
  Date:   2012-06-07 (Thu, 07 Jun 2012)

  Changed paths:
M docs/internals/contributing/writing-documentation.txt

  Log Message:
  ---
  Fixed #17933 -- Added intro note to writing-documentation.txt
Based on initial patch by Thomas Westfeld



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17888: CheckboxInput.render() shouldn't catch exceptions from check_test

[Django]

#17888: CheckboxInput.render() shouldn't catch exceptions from check_test
--+
 Reporter:  brutasse  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by brutasse):

 Pull request with tests and docs is at
 https://github.com/django/django/pull/125

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18430: CachedFilesMixin crashed when CSS files contains non-ascii utf-8 character

[Django]

#18430: CachedFilesMixin crashed when CSS files contains non-ascii utf-8 
character
-+-
 Reporter:  brantyoung   |Owner:  dbrgn
 Type:  Bug  |   Status:  reopened
Component:  contrib.staticfiles  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by brantyoung):

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


Comment:

 I create a minimal project to reproduce this ticket:
 https://bitbucket.org/brantyoung/cached_files_mixin_bug/overview

 It's weird, if I moving all of font files to any directory except
 *PROJECTROOT*/css, every thing works fine.

 But if both iconic-font.css and font files in the same **sub-directory**,
 CachedFilesMixin will crash.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18269: From __future__ import unicode_literals

[Django]

#18269: From __future__ import unicode_literals
--+
 Reporter:  claudep   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Python 3  |  Version:  1.3
 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 Claude Paroz ):

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


Comment:

 In [4a103086d5c67fa4fcc53c106c9fdf644c742dd8]:
 {{{
 #!CommitTicketReference repository=""
 revision="4a103086d5c67fa4fcc53c106c9fdf644c742dd8"
 Fixed #18269 -- Applied unicode_literals for Python 3 compatibility.

 Thanks Vinay Sajip for the support of his django3 branch and
 Jannis Leidel for the review.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[django/django] 4a1030: Fixed #18269 -- Applied unicode_literals for Pytho...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4a103086d5c67fa4fcc53c106c9fdf644c742dd8
  
https://github.com/django/django/commit/4a103086d5c67fa4fcc53c106c9fdf644c742dd8
  Author: Claude Paroz 
  Date:   2012-06-07 (Thu, 07 Jun 2012)

  Changed paths:
M django/conf/locale/__init__.py
M django/conf/locale/bg/formats.py
M django/conf/locale/cs/formats.py
M django/conf/locale/en/formats.py
M django/conf/locale/es_MX/formats.py
M django/conf/locale/et/formats.py
M django/conf/locale/fi/formats.py
M django/conf/locale/fr/formats.py
M django/conf/locale/he/formats.py
M django/conf/locale/hu/formats.py
M django/conf/locale/ja/formats.py
M django/conf/locale/km/formats.py
M django/conf/locale/ko/formats.py
M django/conf/locale/lv/formats.py
M django/conf/locale/nb/formats.py
M django/conf/locale/nn/formats.py
M django/conf/locale/pl/formats.py
M django/conf/locale/pt_BR/formats.py
M django/conf/locale/ru/formats.py
M django/conf/locale/sk/formats.py
M django/conf/locale/sv/formats.py
M django/conf/locale/uk/formats.py
M django/conf/locale/vi/formats.py
M django/contrib/admin/forms.py
M django/contrib/admin/helpers.py
M django/contrib/admin/models.py
M django/contrib/admin/templatetags/admin_list.py
M django/contrib/admin/util.py
M django/contrib/admin/widgets.py
M django/contrib/admindocs/tests/__init__.py
M django/contrib/auth/backends.py
M django/contrib/auth/hashers.py
M django/contrib/auth/management/__init__.py
M django/contrib/auth/models.py
M django/contrib/auth/tests/auth_backends.py
M django/contrib/auth/tests/forms.py
M django/contrib/auth/tests/hashers.py
M django/contrib/auth/tests/management.py
M django/contrib/comments/admin.py
M django/contrib/contenttypes/generic.py
M django/contrib/contenttypes/tests.py
M django/contrib/contenttypes/views.py
M django/contrib/databrowse/datastructures.py
M django/contrib/databrowse/plugins/calendars.py
M django/contrib/databrowse/plugins/fieldchoices.py
M django/contrib/databrowse/sites.py
M django/contrib/flatpages/models.py
M django/contrib/flatpages/tests/forms.py
M django/contrib/formtools/tests/__init__.py
M django/contrib/formtools/tests/wizard/forms.py
M django/contrib/formtools/tests/wizard/namedwizardtests/tests.py
M django/contrib/formtools/tests/wizard/wizardtests/tests.py
M django/contrib/gis/feeds.py
M django/contrib/gis/forms/fields.py
M django/contrib/gis/gdal/tests/test_envelope.py
M django/contrib/gis/geoip/tests.py
M django/contrib/gis/sitemaps/views.py
M django/contrib/gis/tests/geoapp/test_feeds.py
M django/contrib/gis/tests/geoapp/test_sitemaps.py
M django/contrib/gis/views.py
M django/contrib/humanize/templatetags/humanize.py
M django/contrib/humanize/tests.py
M django/contrib/localflavor/ar/ar_provinces.py
M django/contrib/localflavor/ar/forms.py
M django/contrib/localflavor/at/forms.py
M django/contrib/localflavor/au/forms.py
M django/contrib/localflavor/br/br_states.py
M django/contrib/localflavor/br/forms.py
M django/contrib/localflavor/ca/forms.py
M django/contrib/localflavor/ch/forms.py
M django/contrib/localflavor/cl/cl_regions.py
M django/contrib/localflavor/cl/forms.py
M django/contrib/localflavor/cn/cn_provinces.py
M django/contrib/localflavor/cn/forms.py
M django/contrib/localflavor/co/co_departments.py
M django/contrib/localflavor/cz/forms.py
M django/contrib/localflavor/de/forms.py
M django/contrib/localflavor/de_CH/formats.py
M django/contrib/localflavor/ec/ec_provinces.py
M django/contrib/localflavor/es/forms.py
M django/contrib/localflavor/fi/fi_municipalities.py
M django/contrib/localflavor/fi/forms.py
M django/contrib/localflavor/fr/forms.py
M django/contrib/localflavor/fr/fr_department.py
M django/contrib/localflavor/gb/forms.py
M django/contrib/localflavor/hk/forms.py
M django/contrib/localflavor/hr/forms.py
M django/contrib/localflavor/hr/hr_choices.py
M django/contrib/localflavor/id/forms.py
M django/contrib/localflavor/il/forms.py
M django/contrib/localflavor/in_/forms.py
M django/contrib/localflavor/is_/forms.py
M django/contrib/localflavor/is_/is_postalcodes.py
M django/contrib/localflavor/it/forms.py
M django/contrib/localflavor/it/it_province.py
M django/contrib/localflavor/it/it_region.py
M django/contrib/localflavor/it/util.py
M django/contrib/localflavor/kw/forms.py
M django/contrib/localflavor/mk/forms.py
M django/contrib/localflavor/mk/mk_choices.py
M django/contrib/localflavor/mx/forms.py
M django/contrib/localflavor/mx/mx_states.py
M django/contrib/localflavor/nl/forms.py
M django/contrib/localflavor/no/forms.py
M django/contrib/localflavor/no/no_municipaliti

Re: [Django] #16855: select_related doesn't chain as expected

[Django]

#16855: select_related doesn't chain as expected
-+-
 Reporter:  Leo  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by oinopion):

 * has_patch:  0 => 1


Comment:

 I've created pull request https://github.com/django/django/pull/124

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18442: Documentation references non-existent locale

[Django]

#18442: Documentation references non-existent locale
-+-
 Reporter:  jakul|Owner:  jakul
 Type:  Uncategorized|   Status:  closed
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Fixed on
Has patch:  1|  a branch
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [706fd9adc0b6587c7f96a834c757708e64fcf615]:
 {{{
 #!CommitTicketReference repository=""
 revision="706fd9adc0b6587c7f96a834c757708e64fcf615"
 Merge pull request #122 from jakul/issue-18442

 Fixed #18442 -- Invalid locale name in docs.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[django/django] 0e3694: fix bad locale names

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0e36948f627983bbf2b3cc4c4d2ec4a5a64e6e0a
  
https://github.com/django/django/commit/0e36948f627983bbf2b3cc4c4d2ec4a5a64e6e0a
  Author: jakul 
  Date:   2012-06-07 (Thu, 07 Jun 2012)

  Changed paths:
M docs/ref/django-admin.txt

  Log Message:
  ---
  fix bad locale names


  Commit: 706fd9adc0b6587c7f96a834c757708e64fcf615
  
https://github.com/django/django/commit/706fd9adc0b6587c7f96a834c757708e64fcf615
  Author: Aymeric Augustin 
  Date:   2012-06-07 (Thu, 07 Jun 2012)

  Changed paths:
M docs/ref/django-admin.txt

  Log Message:
  ---
  Merge pull request #122 from jakul/issue-18442

Fixed #18442 -- Invalid locale name in docs.


Compare: https://github.com/django/django/compare/c28e700...706fd9a

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18381: Underscore in CharField primary key breaks the admin "view on site" link

[Django]

#18381: Underscore in CharField primary key breaks the admin "view on site" link
---+
 Reporter:  dappawit   |Owner:  apollo13
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 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 apollo13):

 See https://github.com/django/django/pull/123 for the pull 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17181: Allow for specifying multiple locales and domains for makemessages and compilemessages commands

[Django]

#17181: Allow for specifying multiple locales and domains for makemessages and
compilemessages commands
-+-
 Reporter:  aminland |Owner:  jakul
 Type:  New feature  |   Status:  new
Component:   |  Version:  1.3
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:  Fixed on
 Keywords:  i18n makemessages|  a branch
  compilemessages|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by jakul):

 * cc: jakul (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18442: Documentation references non-existent locale

[Django]

#18442: Documentation references non-existent locale
-+-
 Reporter:  jakul|Owner:  jakul
 Type:  Uncategorized|   Status:  new
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Fixed on
Has patch:  1|  a branch
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by jakul):

 * cc: jakul (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18056: query_set.dates('field_name', 'years') does not return distinct elements

[Django]

#18056: query_set.dates('field_name', 'years') does not return distinct elements
-+-
 Reporter:  framazz@…|Owner:  nmfm
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nuno Maltez ):

 * status:  reopened => new
 * owner:  nobody => nmfm


Comment:

 From my local tests, having a custom object manager is creating the issue.
 I'll take a closer look.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18381: Underscore in CharField primary key breaks the admin "view on site" link

[Django]

#18381: Underscore in CharField primary key breaks the admin "view on site" link
---+
 Reporter:  dappawit   |Owner:  apollo13
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 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 apollo13):

 * owner:  nobody => apollo13


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17181: Allow for specifying multiple locales and domains for makemessages and compilemessages commands

[Django]

#17181: Allow for specifying multiple locales and domains for makemessages and
compilemessages commands
-+-
 Reporter:  aminland |Owner:  jakul
 Type:  New feature  |   Status:  new
Component:   |  Version:  1.3
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:  Fixed on
 Keywords:  i18n makemessages|  a branch
  compilemessages|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by jakul):

 * stage:  Accepted => Fixed on a branch


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18442: Documentation references non-existent locale

[Django]

#18442: Documentation references non-existent locale
-+-
 Reporter:  jakul|Owner:  jakul
 Type:  Uncategorized|   Status:  new
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Fixed on
Has patch:  1|  a branch
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by jakul):

 * has_patch:  0 => 1
 * stage:  Unreviewed => Fixed on a branch


Comment:

 I made a pull request https://github.com/django/django/pull/122

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18381: Underscore in CharField primary key breaks the admin "view on site" link

[Django]

#18381: Underscore in CharField primary key breaks the admin "view on site" link
---+
 Reporter:  dappawit   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 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 apollo13):

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


Comment:

 The problem is that we pass the escaped object_id into
 contenttype_views.shortcut -- we either have to unquote there or don't
 pass the quoted url into it.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18442: Documentation references non-existent locale

[Django]

#18442: Documentation references non-existent locale
---+--
 Reporter:  jakul  |Owner:  jakul
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.4
 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 jakul):

 * owner:  nobody => jakul
 * needs_better_patch:   => 0
 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #18442: Documentation references non-existent locale

[Django]

#18442: Documentation references non-existent locale
---+
 Reporter:  jakul  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 https://docs.djangoproject.com/en/1.4/ref/django-admin/ references a
 locale which doesn't exist!
 {{{
 django-admin.py compilemessages --locale=br_PT
 }}}

 `br_PT` should be `pt_BR`

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17181: Allow for specifying multiple locales and domains for makemessages and compilemessages commands

[Django]

#17181: Allow for specifying multiple locales and domains for makemessages and
compilemessages commands
-+-
 Reporter:  aminland |Owner:  jakul
 Type:  New feature  |   Status:  new
Component:   |  Version:  1.3
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  i18n makemessages|  Needs documentation:  0
  compilemessages|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by jakul):

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


Comment:

 I've created a pull request for this
 https://github.com/django/django/pull/121

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16817: Add a guide on code coverage to contributing docs

[Django]

#16817: Add a guide on code coverage to contributing docs
-+-
 Reporter:  julien   |Owner:  pvl
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.3
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by pvl):

 * cc: pvl (added)
 * stage:  Accepted => Ready for checkin


Comment:

 Included this patch and added documentation for coverage installation and
 use (also based on the documentation work of krzysiumed in #4501)

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

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17671: CursorWrapper in Python 2.7 cannot be used as a contextmanager

[Django]

#17671: CursorWrapper in Python 2.7 cannot be used as a contextmanager
-+-
 Reporter:  manfre   |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  regression   |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by akaariai):

 Hmm, IMHO there is reason to block the forwarding. The reason is that what
 the forwarding does is backend specific, and thus could act as transaction
 control mechanism for example, but depending on the backend.

 A shortcut of using "with connection.cursor() as c: ..." in place of "c =
 connection.cursor(); try: ... finally: c.close()" could be nice.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18085: sqllite integer is signed but django recognize as unsigned

[Django]

#18085: sqllite integer is signed but django recognize as unsigned
---+--
 Reporter:  robotr |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.4
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by apollo13):

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


Comment:

 Hi, can you provide more info? Especially a traceback would be 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18179: Management can't load custom commands when separately packaged apps share a common base module

[Django]

#18179: Management can't load custom commands when separately packaged apps 
share a
common base module
-+-
 Reporter:  nOw2 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by ramiro:

Old description:

> django.core.management.find_management_module() loads custom commands for
> manage.py by finding the path of the module and examining file directly.
>
> This fails when apps are within packages that share a common base name,
> but where the files are NOT in the same directories, example:
>
> app 1: company.division.project_a.app1 stored in path
> packages/company.subdivision.project_a.app1
> app 2: company.division.project_b.app2 stored in path
> packages/company.subdivision.project_b.app2
>
> Custom commands in app 2 will not be found.
>
> A code trace from pdb follows. Excuse the rather complicated example, but
> this is from a genuine problem and only the modules names have been
> changed.
>
> {{{
> > site-
> packages/django/core/management/__init__.py(43)find_management_module()
> -> parts.append('management')
> (Pdb) parts
> ['company', 'subdivision', 'project_b', 'app2']
>
> . . .
>
> > site-
> packages/django/core/management/__init__.py(62)find_management_module()
> -> f, path, descr = imp.find_module(part, path and [path] or None)
> (Pdb)
> ImportError: 'No module named project_b'
> > site-
> packages/django/core/management/__init__.py(62)find_management_module()
> -> f, path, descr = imp.find_module(part, path and [path] or None)
> (Pdb) l
>  57 if os.path.basename(os.getcwd()) != part:
>  58 raise e
>  59
>  60 while parts:
>  61 part = parts.pop()
>  62  -> f, path, descr = imp.find_module(part, path and [path] or
> None)
>  63 return path
>  64
>  65 def load_command_class(app_name, name):
>  66 """
>  67 Given a command name and an application name, returns the
> Command
> (Pdb) part
> 'project_b'
> (Pdb) path
> 'packages/company.subdivision.project_a.app1/company/subdivision'
> }}}
>
> Issue was found in 1.3.1 but the code appears the same in the current
> trunk version:
> https://code.djangoproject.com/browser/django/trunk/django/core/management/__init__.py?rev=17842#L60

New description:

 django.core.management.find_management_module() loads custom commands for
 manage.py by finding the path of the module and examining file directly.

 This fails when apps are within packages that share a common base name,
 but where the files are NOT in the same directories, example:

  * app 1: company.division.project_a.app1 stored in path
 `packages/company.subdivision.project_a.app1`
  * app 2: company.division.project_b.app2 stored in path
 `packages/company.subdivision.project_b.app2`

 Custom commands in app 2 will not be found.

 A code trace from pdb follows. Excuse the rather complicated example, but
 this is from a genuine problem and only the modules names have been
 changed.

 {{{
 > site-
 packages/django/core/management/__init__.py(43)find_management_module()
 -> parts.append('management')
 (Pdb) parts
 ['company', 'subdivision', 'project_b', 'app2']

 . . .

 > site-
 packages/django/core/management/__init__.py(62)find_management_module()
 -> f, path, descr = imp.find_module(part, path and [path] or None)
 (Pdb)
 ImportError: 'No module named project_b'
 > site-
 packages/django/core/management/__init__.py(62)find_management_module()
 -> f, path, descr = imp.find_module(part, path and [path] or None)
 (Pdb) l
  57 if os.path.basename(os.getcwd()) != part:
  58 raise e
  59
  60 while parts:
  61 part = parts.pop()
  62  -> f, path, descr = imp.find_module(part, path and [path] or
 None)
  63 return path
  64
  65 def load_command_class(app_name, name):
  66 """
  67 Given a command name and an application name, returns the
 Command
 (Pdb) part
 'project_b'
 (Pdb) path
 'packages/company.subdivision.project_a.app1/company/subdivision'
 }}}

 Issue was found in 1.3.1 but the code appears the same in the current
 trunk version:
 
https://code.djangoproject.com/browser/django/trunk/django/core/management/__init__.py?rev=17842#L60

--

-- 
Ticket URL: 
Django 

Re: [Django] #18064: Allow changing form field properties after form creation

[Django]

#18064: Allow changing form field properties after form creation
-+--
 Reporter:  gcc  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  1.4
 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 apollo13):

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


Comment:

 Actually closing it…

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18432: Chained foreign keys with to_field produce incorrect query

[Django]

#18432: Chained foreign keys with to_field produce incorrect query
-+-
 Reporter:  lwarx|Owner:  Spark23
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Spark23):

 * owner:  nobody => Spark23
 * needs_docs:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * needs_better_patch:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17671: CursorWrapper in Python 2.7 cannot be used as a contextmanager

[Django]

#17671: CursorWrapper in Python 2.7 cannot be used as a contextmanager
-+-
 Reporter:  manfre   |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  regression   |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by manfre):

 The underlying Python "regression" and whether or not the Django code
 should have ever worked is not really relevant. The important question is,
 was it the intention that cursors in Django should be usable as a
 contextmanager? If so, then this is clearly a regression. If not, then is
 there a reason to explicitly block the functionality provided by the
 underlying cursors?

 The expectation for django-mssql has always been that cursors, which must
 be used more frequently than with the core backends, should be usable as a
 contextmanager for the sake of code brevity and readability. I have
 applied a (hopefully temporary monkey) patch to django-mssql v1.1 to
 maintain this expected behavior.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

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

[Django]

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

Comment (by akaariai):

 I had some IRC-discussions with Andrew Godwin today. It was agreed that
 the feature should not aim to support testing on single database instance
 if the database doesn't support namespaced schemas (only PostgreSQL has
 them from Django's perspective). This should simplify the implementation
 somewhat, as there is no need to test-prefix the schema name.

 I will try to rewrite the patch without support for test-prefixing the
 schemas (and also drop support for SQLite's prefix-the-table-name hack
 totally).

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18179: Management can't load custom commands when separately packaged apps share a common base module

[Django]

#18179: Management can't load custom commands when separately packaged apps 
share a
common base module
-+-
 Reporter:  nOw2 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by nOw2):

 The packages don't have a period in their names, but the directory above
 the python path does though I don't believe that has an impact.

 i.e. for:
 packages/company.subdivision.project_a.app1/company/subdivision/project_a/app1/
 PYTHONPATH="packages/company.subdivision.project_a.app1/"
 Python searches this: "company/subdivision/project_a/app1/"
 Package name is "company.subdivision.project_a.app1"

 The issue comes from developing each package separately but in the same
 Python namespace, which is the method we've come up with to handle this
 particular large project.

 The issue comes in because there are many such packages like this:

 packages/company.subdivision.project_a.app1/company/subdivision/project_a/app1/
 packages/company.subdivision.project_a.app2/company/subdivision/project_a/app2/
 packages/company.subdivision.project_b.app1/company/subdivision/project_b/app1/

 The way the current find_management_module() works is to find the first
 file/directory on disk that corresponds to the Python module "company",
 even though there may be many such directories. i.e. the package name
 "company.subdivision.project_a.app1" has a unique __init__.py, but the
 package name "company" is not.

 (nb, the _ _ init _ _.py in the "shared" name components looks like this:
 {{{
 import pkg_resources

 pkg_resources.declare_namespace(__name__)
 }}}
 )

 In the above example, "import company.subdivision.project_b.app1" causes
 find_management_module() to fail when it can't find project_b in the
 directory
 "packages/company.subdivision.project_a.app1/company/subdivision/". That
 directory is first on the path to match company.subdivision but is not the
 correct one for company.subdivision.project_b.app1!

 I recognise that this is something of an edge case.
 I have yet to test if the issue continues when the packages are installed
 via setuptools/distribute, I'm unsure if the issue would persist once
 installed to site-packages or into eggs. My workaround patch is in our
 current production release.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11518: Custom commands cannot be run from cron (or other directory) if project is not on Python Path

[Django]

#11518: Custom commands cannot be run from cron (or other directory) if project 
is
not on Python Path
-+-
 Reporter:  mark.ellul@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Other) |  Version:
 Severity:  Normal   |  1.1-beta-1
 Keywords:  custom commands  |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by lukeplant):

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


Comment:

 AFAICS, the bug can happen only when you are using the old sys.path hack
 that we used to use, in which a module in your project could be importable
 as 'myproj.myapp.mymodule' and 'myapp.mymodule'. I'm marking FIXED on that
 basis, since we've removed/deprecated the sys.path hack -
 https://docs.djangoproject.com/en/1.4/releases/1.4/#django-core-
 management-setup-environ

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18351: Sitemaps should use the X-Robots-Tag HTTP header

[Django]

#18351: Sitemaps should use the X-Robots-Tag HTTP header
-+-
 Reporter:  mlissner |Owner:  mlissner
 Type:  New feature  |   Status:  assigned
Component:  Core (Other) |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by andrewgodwin):

 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #5725: Inspectdb makes too long CharFields

[Django]

#5725: Inspectdb makes too long CharFields
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  introspection mysql  |  checkin
  inspectdb  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by andrewgodwin):

 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17959: Silence output during GIS tests

[Django]

#17959: Silence output during GIS tests
--+
 Reporter:  claudep   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  GIS   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  test logging  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by andrewgodwin):

 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18179: Management can't load custom commands when separately packaged apps share a common base module

[Django]

#18179: Management can't load custom commands when separately packaged apps 
share a
common base module
-+-
 Reporter:  nOw2 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by andrewgodwin):

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


Comment:

 It looks like you've got packages with "." in their directory names -
 that's not a valid Python module name, and while "__import__" may import
 it, it does a lot of things it shouldn't do. Module names (and thus
 directory names) should consist only of letters, numbers and the
 underscore character.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18174: Model inheritance pointers doesn't refer to parent to refer to grandparents

[Django]

#18174: Model inheritance pointers doesn't refer to parent to refer to 
grandparents
-+-
 Reporter:  phowe|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by andrewgodwin):

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


Comment:

 Are you sure the ptr_ids are going to increment at "different rates"?
 Those two queries are functionally equivalent - since ptr_id is always the
 same across all objects - and only the base class will define the PK value
 used for a new object.

 I'm closing this as invalid - it needs a code/console example on what
 exactly the problem is with IDs before I can understand what the problem
 is supposed to be.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18142: sorting in change_list is not distincted

[Django]

#18142: sorting in change_list is not distincted
---+
 Reporter:  nick.mayerhofer@…  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords:  sort distinct  | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by andrewgodwin):

 * needs_better_patch:   => 0
 * component:  Database layer (models, ORM) => contrib.admin
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 Related to #13902 - probably just needs the code that detects distinct-
 setting updated.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18162: Specifying choices to Field overrides any form_class argument (was: formfield in Field class should allow change form_class if choices specified)

[Django]

#18162: Specifying choices to Field overrides any form_class argument
-+
 Reporter:  rafallo  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by andrewgodwin):

 * needs_better_patch:  0 => 1
 * type:  New feature => Bug
 * stage:  Unreviewed => Accepted
 * component:  Database layer (models, ORM) => Forms


Comment:

 Valid bug, but attached patch is not what I would do - instead, just make
 it respect form_class if provided (by changing the default value so
 assignment of it is detectable.)

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18161: Redirection after successful login is not working properly

[Django]

#18161: Redirection after successful login is not working properly
-+
 Reporter:  wolfgang.doll@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.4
 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 andrewgodwin):

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


Comment:

 I think a better patch would be to login() in contrib.admin.sites - that's
 where the redirect is set to request.get_full_path, and should instead be
 only be set to that if the 'next' GET param is missing or pointing off-
 site (for security reasons, it should only redirect to an internal URL).

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15574: IndexError: list index out of range caused by inline formsets

[Django]

#15574: IndexError: list index out of range caused by inline formsets
-+-
 Reporter:  poswald  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  inline formset   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by anonymous):

 visik7: my patch was made for trunk, but it shouldn't be hard to adapt to
 1.3.1.

 Note to those who want to use my patch as a base: there is a case that
 doesn't work: if the user, when using the django admin with the patch,
 submits a form a deleted relation but also containing another error, he'll
 get the form again to get a chance to correct the error, but the formset
 management form will output TOTAL_FORMS/INITIAL_FORMS inconsistent with
 the number of forms, and therefore the user won't be able to submit the
 form.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17845: Provide a way for model formsets to know how many records will be created

[Django]

#17845: Provide a way for model formsets to know how many records will be 
created
-+--
 Reporter:  mstevens@…   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  1.3
 Severity:  Normal   |   Resolution:  invalid
 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 apollo13):

 One (untested) possibility is:
 {{{
 def clean(self):
   super(BlaForm, self).clean()
   c = 0
   for f in self.extra_forms:
 if f.has_changed() and not self._should_delete_form(f):
   c += 1
 }}}

 After that c should tell you how many objects will get created, see
 ''save_new_objects'' and ''save_existing_objects'' for more info.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18153: Erorneous OneToOneField for instances that have pk unset

[Django]

#18153: Erorneous OneToOneField for instances that have pk unset
-+-
 Reporter:  jbzdak@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by andrewgodwin):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * type:  Uncategorized => Bug
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Valid bug, but I think that the SingleRelatedObjectDescriptor should
 return an error in this case, rather than None, as you can't assign to
 that descriptor in that state.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17845: Provide a way for model formsets to know how many records will be created

[Django]

#17845: Provide a way for model formsets to know how many records will be 
created
-+--
 Reporter:  mstevens@…   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  1.3
 Severity:  Normal   |   Resolution:  invalid
 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):

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


Comment:

 Unfortunately, this isn't something you can know in `clean()`.

 The sequence is as follows:
 - 1) `clean()`, well, cleans data received from the browser,
 - 2) existing instances present in the form, if any, are loaded from the
 database,
 - 3) existing instances are saved with the modifications and new instances
 are created.

 That's why it isn't possible to know how many records will be created
 until step 2. However, you could check `len(form.new_objects)` after
 saving.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[django/django] c28e70: Removed references to changes made in 1.2.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c28e700c7e54e3071f173b34a12eb1c4f6e39552
  
https://github.com/django/django/commit/c28e700c7e54e3071f173b34a12eb1c4f6e39552
  Author: Aymeric Augustin 
  Date:   2012-06-07 (Thu, 07 Jun 2012)

  Changed paths:
M docs/faq/models.txt
M docs/howto/custom-model-fields.txt
M docs/howto/custom-template-tags.txt
M docs/internals/contributing/writing-code/submitting-patches.txt
M docs/ref/contrib/admin/index.txt
M docs/ref/contrib/comments/example.txt
M docs/ref/contrib/comments/index.txt
M docs/ref/contrib/csrf.txt
M docs/ref/contrib/formtools/form-preview.txt
M docs/ref/contrib/gis/db-api.txt
M docs/ref/contrib/gis/gdal.txt
M docs/ref/contrib/gis/geoquerysets.txt
M docs/ref/contrib/gis/geos.txt
M docs/ref/contrib/gis/install.txt
M docs/ref/contrib/gis/model-api.txt
M docs/ref/contrib/gis/testing.txt
M docs/ref/contrib/index.txt
M docs/ref/contrib/messages.txt
M docs/ref/contrib/syndication.txt
M docs/ref/databases.txt
M docs/ref/django-admin.txt
M docs/ref/forms/api.txt
M docs/ref/forms/fields.txt
M docs/ref/forms/validation.txt
M docs/ref/middleware.txt
M docs/ref/models/fields.txt
M docs/ref/models/instances.txt
M docs/ref/models/querysets.txt
M docs/ref/settings.txt
M docs/ref/signals.txt
M docs/ref/templates/api.txt
M docs/ref/templates/builtins.txt
M docs/ref/validators.txt
M docs/topics/auth.txt
M docs/topics/cache.txt
M docs/topics/db/models.txt
M docs/topics/db/multi-db.txt
M docs/topics/db/sql.txt
M docs/topics/email.txt
M docs/topics/forms/formsets.txt
M docs/topics/forms/modelforms.txt
M docs/topics/http/urls.txt
M docs/topics/i18n/formatting.txt
M docs/topics/i18n/translation.txt
M docs/topics/serialization.txt
M docs/topics/testing.txt

  Log Message:
  ---
  Removed references to changes made in 1.2.

Thanks Florian Apolloner for the patch.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18150: Uploading a file ending with a backslash fails

[Django]

#18150: Uploading a file ending with a backslash fails
--+
 Reporter:  Peter Kuma|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  File uploads/storage  |  Version:  1.4
 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 Nuno Maltez ):

 * cc: nuno@… (added)
 * needs_better_patch:   => 0
 * needs_docs:   => 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13696: Admin Edit Inline templates don' t output hidden field for PK when it isn't an autoField and has editable=False

[Django]

#13696: Admin Edit Inline templates don' t output hidden field for PK when it 
isn't
an autoField and has editable=False
--+
 Reporter:  evan.reiser@… |Owner:  dArignac
 Type:  Bug   |   Status:  reopened
Component:  contrib.admin |  Version:  1.2
 Severity:  Normal|   Resolution:
 Keywords:  inline templates  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by dArignac):

 I don't get where exactly the problem now is. If I include an AutoField
 setting its property "editable" to True, it still cannot be edited within
 the AdminSite, there is also no problem saving this. For all custom Fields
 being primary keys (primary_key=True) the current fix does work. Please
 explain, thanks!

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17884: Distance lookups using ST_Distance_Sphere fails with PostGis 1.5.3

[Django]

#17884: Distance lookups using ST_Distance_Sphere fails with PostGis 1.5.3
-+
 Reporter:  ogirardot@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  GIS  |  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 aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 Accepting because the description is sufficiently detailed to convince me
 that the problem exists. I can't tell how to resolve it, though.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17866: locale middleware adds Vary Accept-Language when language prefix used

[Django]

#17866: locale middleware adds Vary Accept-Language when language prefix used
---+--
 Reporter:  sero   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  HTTP handling  |  Version:  1.4-beta-1
 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 aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 We should include the "Vary: Accept-Language" header if and only if this
 header was actually used to determine the language used for rendering the
 page.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17869: With RemoteUserMiddleware, users keep being logged in after web server stops sending REMOTE_USER headers

[Django]

#17869: With RemoteUserMiddleware, users keep being logged in after web server
stops sending REMOTE_USER headers
--+---
 Reporter:  lamby |Owner:  bouchardsyl
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+---
Changes (by bouchardsyl):

 * owner:  nobody => bouchardsyl
 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17839: Ordering by an expression containing annotations

[Django]

#17839: Ordering by an expression containing annotations
-+-
 Reporter:  joseph.helfer@…  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 The ORM doesn't intend to cover 100% of what you may want to do with your
 database. In this case, it sounds more reasonable to switch to raw SQL.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16855: select_related doesn't chain as expected

[Django]

#16855: select_related doesn't chain as expected
-+-
 Reporter:  Leo  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by oinopion):

 * cc: tomek@… (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[django/django] 6492e8: Added more precise assertions on two fixture tests...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6492e8e5e6643c5a90d71727af7f17a362b9362b
  
https://github.com/django/django/commit/6492e8e5e6643c5a90d71727af7f17a362b9362b
  Author: Claude Paroz 
  Date:   2012-06-07 (Thu, 07 Jun 2012)

  Changed paths:
M tests/modeltests/fixtures/tests.py

  Log Message:
  ---
  Added more precise assertions on two fixture tests.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14026: Setting for TRANSACTION_LEVEL on db backends

[Django]

#14026: Setting for TRANSACTION_LEVEL on db backends
-+-
 Reporter:  adamnelson   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 I just discussed this with Andrew Godwin. He confirms that both
 `init_command` and raw SQL can be used to control the isolation level.

 If you want more, please explain it in more than one line :) A post to the
 django-developers mailing list would be best. Re-closing until then.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18400: Unexpected {% if %} behavior

[Django]

#18400: Unexpected {% if %} behavior
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  template, if,| Triage Stage:  Design
  length |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * stage:  Unreviewed => Design decision needed


Comment:

 It would be interesting to investigate why the `ignore_failures` argument
 was added and what it does. Apparently it triggers two different
 resolution modes. Isn't that inconsistency a bad idea in itself? If so,
 shouldn't we get rid of this argument?

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16039: syncdb with --database option fails

[Django]

#16039: syncdb with --database option fails
-+-
 Reporter:  yedpodtrzitko|Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


Comment:

 I haven't verified if the patch is correct, but there's definitely
 something wrong here.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14026: Setting for TRANSACTION_LEVEL on db backends

[Django]

#14026: Setting for TRANSACTION_LEVEL on db backends
-+-
 Reporter:  adamnelson   |Owner:  nobody
 Type:  New feature  |   Status:  reopened
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 This ticket is getting confusing: the report says "this would apply to
 MySQL", a correct solution for MySQL is provided in the comments. Then
 it's re-openend, asking for something more generic.

 For the sake of clarity, it'd be better to open a new ticket describing
 exactly what you want (if possible with a patch or pull request), and re-
 close this one. Otherwise I'm afraid your request will just stay buried
 here.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15089: contrib.sites and multitenancy

[Django]

#15089: contrib.sites and multitenancy
-+-
 Reporter:  legutierr|Owner:  apollo13
 Type:  New feature  |   Status:  new
Component:  contrib.sites|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  0
-+-

Comment (by apollo13):

 Updated and minimalistic patch on
 https://github.com/apollo13/django/compare/ticket15089

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11459: QuerySet.count() generates invalid sql when used with select_related() and extra(where=[customWhereClause])

[Django]

#11459: QuerySet.count() generates invalid sql when used with select_related() 
and
extra(where=[customWhereClause])
-+-
 Reporter:  eddified |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18227: locale error on creating superuser

[Django]

#18227: locale error on creating superuser
---+---
 Reporter:  jerry@…|Owner:  bouchardsyl
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  duplicate
 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 ramiro):

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


Comment:

 I'm going to close this one as duplicate of #16017.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11459: QuerySet.count() generates invalid sql when used with select_related() and extra(where=[customWhereClause])

[Django]

#11459: QuerySet.count() generates invalid sql when used with select_related() 
and
extra(where=[customWhereClause])
-+-
 Reporter:  eddified |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Old description:

> Here is the error message:
> (1054, "Unknown column 'beyondStore_artist.name' in 'where clause'")
>
> This is the invalid sql that calling count() is generating that causes
> the above error message:
> SELECT COUNT(*) FROM `sss_song` WHERE (match(sss_song.title)
> against('hits')) or (match(sss_artist.name, sss_artist.description)
> against('hits')) or (match(sss_album.title, sss_album.description)
> against('hits'))
>
> Here is the code that generates the QuerySet:
> songs = models.Song.objects.select_related('album__genre__genre__id',
> 'artist__name').extra(where = [where_clause])
> t = songs.count() # sql error is caused by this call to count()
>
> I know that the query to get the actual data works just fine. It is only
> the COUNT that is not working. The work around was to get the count
> manually (by writing an sql statement that gets the count, and executing
> the statement 'manually' using connection.cursor().execute(sql)).
> The two arguments passed to "select related" are both valid.
>
> The problem is that the 'where' clause uses the two tables that are
> specified by the "select_related" call, but the count() function
> apparently ignores the select_related call.
>
> Perhaps the QuerySet.count() function should be smart enough to take the
> "select_related" args into consideration when generating the COUNT sql.
>
> I did try to specify missing tables using tables=[...] as an argument to
> extra(), but I couldn't get it to work with both the count() and the
> actual data query.

New description:

 Here is the error message:
 {{{
 (1054, "Unknown column 'beyondStore_artist.name' in 'where clause'")
 }}}

 This is the invalid sql that calling count() is generating that causes the
 above error message:
 {{{
 SELECT COUNT(*) FROM `sss_song` WHERE (match(sss_song.title)
 against('hits')) or (match(sss_artist.name, sss_artist.description)
 against('hits')) or (match(sss_album.title, sss_album.description)
 against('hits'))
 }}}

 Here is the code that generates the QuerySet:
 {{{
 songs = models.Song.objects.select_related('album__genre__genre__id',
 'artist__name').extra(where = [where_clause])
 t = songs.count() # sql error is caused by this call to count()
 }}}

 I know that the query to get the actual data works just fine. It is only
 the COUNT that is not working. The work around was to get the count
 manually (by writing an sql statement that gets the count, and executing
 the statement 'manually' using connection.cursor().execute(sql)).
 The two arguments passed to "select related" are both valid.

 The problem is that the 'where' clause uses the two tables that are
 specified by the "select_related" call, but the count() function
 apparently ignores the select_related call.

 Perhaps the QuerySet.count() function should be smart enough to take the
 "select_related" args into consideration when generating the COUNT sql.

 I did try to specify missing tables using tables=[...] as an argument to
 extra(), but I couldn't get it to work with both the count() and the
 actual data query.

--

Comment (by aaugustin):

 Fixed formatting (please use preview).

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17671: CursorWrapper in Python 2.7 cannot be used as a contextmanager

[Django]

#17671: CursorWrapper in Python 2.7 cannot be used as a contextmanager
-+-
 Reporter:  manfre   |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  regression   |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

 * stage:  Unreviewed => Design decision needed


Comment:

 This code should never have worked; see http://bugs.python.org/issue9220
 (and its duplicate http://bugs.python.org/issue9259).

 I'm having a hard time determining if we should change something in
 Django:
 - our documentation states that the cursors implement the standard Python
 DB-API described in PEP 249
 - but PEP 249 doesn't say whether cursors are supposed to work as context
 managers
 - since Python 2.6 sqlite's cursors
 [http://docs.python.org/library/sqlite3#using-the-connection-as-a-context-
 manager act as context managers] for transaction control,
 - but Django implements its own transaction control

 `__enter__` and `__exit__` methods that just forward to `__enter__` and
 `__exit__` wouldn't hurt, but I can't find a real reason to implement
 them.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18427: limit_choices_to won't limit correctly

[Django]

#18427: limit_choices_to won't limit correctly
-+-
 Reporter:  thanos@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Uncategorized|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  limit_choices_to | Triage Stage:  Design
  admin  |  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nuno Maltez ):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Design decision needed
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 I can confirm this really happens: after you create a new object that does
 not fit the limit_choices_to restriction using the "plus icon", it will be
 selected in the form field, and listed in the dropdown.

 However, saving will fail with the appropriate error message and the new
 object is removed from the dropdown.

 I'm changing to "Design decision needed" because I'm not sure there's an
 easy fix and if this widget behaves likes this, well, "by design".

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16802: Core management commands should have defined success/fail semantics

[Django]

#16802: Core management commands should have defined success/fail semantics
-+-
 Reporter:  jdunck   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  1.3
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

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


Comment:

 loaddata does now raises CommandError on failure
 (6fd1950a4e29c1b5ed071a880db64103715ead51).

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18227: locale error on creating superuser

[Django]

#18227: locale error on creating superuser
---+---
 Reporter:  jerry@…|Owner:  bouchardsyl
 Type:  New feature|   Status:  assigned
Component:  Documentation  |  Version:  1.4
 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 bouchardsyl):

 * owner:  nobody => bouchardsyl
 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #18046: document index created for a ForeignKey

[Django]

#18046: document index created for a ForeignKey
--+
 Reporter:  jbauer@…  |Owner:  raulcd
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:  ForeignKey db_index   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by raulcd):

 * cc: raulcumplido@… (added)
 * owner:  nobody => raulcd


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.