Re: [Django] #18878: syncdb for secondary non-default database generates error due to django_content_type

[Django]

#18878: syncdb for secondary non-default database generates error due to
django_content_type
-+-
 Reporter:  robertpayne@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Isn't this a duplicate of #16039?

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #18879: FilteredSelectMultiple loses data

[Django]

#18879: FilteredSelectMultiple loses data
---+
 Reporter:  simon29|  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  1
---+
 If page loading breaks at just the right time, it's possible we've seen
 that the currently selected options are not transferred from the
 underlying form's select element into the javascript-powered
 FilteredSelectMultiple widget.

 Then, if the user goes ahead and presses save, the options are
 wiped/overridden.

 A solution here would be to set a flag once the options are safely
 transferred to the widget, and only pass the widget's selections back into
 the form's select element during submit if the flag is set.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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 https://groups.google.com/groups/opt_out.

[Django] #18878: syncdb for secondary non-default database generates error due to django_content_type

[Django]

#18878: syncdb for secondary non-default database generates error due to
django_content_type
+
 Reporter:  robertpayne@…   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Core (Management commands)  |Version:  1.4
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  1   |  UI/UX:  0
+
 This is against Django 1.4.1

 If you configure multiple databases in settings like such:


 {{{
 DATABASES = {
 'production': {
 'ENGINE': 'django.db.backends.mysql',
 'NAME': 'XXX_pro',
 'USER': 'XXX',
 'PASSWORD': 'satmed88',
 'HOST': 'localhost',
 'PORT': '3306',
 },
 'default': {
 'ENGINE': 'django.db.backends.mysql',
 'NAME': 'XXX_dev',
 'USER': 'XXX',
 'PASSWORD': 'XXX',
 'HOST': 'localhost',
 'PORT': '3306',
 },
 'test': {
 'ENGINE': 'django.db.backends.mysql',
 'NAME': 'XXX_test',
 'USER': 'XXX',
 'PASSWORD': 'XXX',
 'HOST': 'localhost',
 'PORT': '3306',
 },
 }
 }}}

 Then you run {{{ manage.py syncdb --database=production }}} it will fail
 with an error django.db.utils.DatabaseError: (1146, "Table
 'XXX_dev.django_content_type' doesn't exist")

 Here is what I believe is happening:

 1) django.core.management.syncdb.py runs
 2) django.core.management.syncdb.py hits line 106 and commits a
 transaction {{{ transaction.commit_unless_managed(using=db) }}}
 3) django.core.management.syncdb.py hits line 110 and fires
 post_sync_signal {{{ emit_post_sync_signal(created_models, verbosity,
 interactive, db) }}}
 4) django.contrib.contentypes.management.py handles this post_sync_signal
 and while it does receive the selected db in the kwargs it never uses the
 db but just runs against the default routed database.


 Simple fix would be to patch django.contrib.contentypes.management.py to
 use the kwarg['db']

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18192: If translation not exist: 'NoneType' object has no attribute '_info'

[Django]

#18192: If translation not exist: 'NoneType' object has no attribute '_info'
-+-
 Reporter:  jedie|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.4
  Internationalization   |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by paulo.koch@…):

 This clearly needs a better error 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 https://groups.google.com/groups/opt_out.

Re: [Django] #18877: Selecting app for testing - dot in app name

[Django]

#18877: Selecting app for testing - dot in app name
---+--
 Reporter:  rrafal@…   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Testing framework  |  Version:  1.4
 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 anonymous):

 I was not aware that apps were give shorter names like that. Thank you for
 the explanation. Everything works again!

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18877: Selecting app for testing - dot in app name

[Django]

#18877: Selecting app for testing - dot in app name
---+--
 Reporter:  rrafal@…   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Testing framework  |  Version:  1.4
 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 russellm):

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


Comment:

 From Django's point of view, the app isn't called "django.contrib.auth";
 it's called "auth" -- only the last part of the dotted name is used. If
 you want to run the test suite for auth, you should use

 {{{
 ./manage.py test auth
 }}}

 This is something that is quite deep ingrained in the application loading
 infrastructure, so it isn't really plausible to change 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 https://groups.google.com/groups/opt_out.

[Django] #18877: Selecting app for testing - dot in app name

[Django]

#18877: Selecting app for testing - dot in app name
---+
 Reporter:  rrafal@…   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Testing framework  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I'm trying to execute the following command:
 python manage.py test django.contrib.auth

 I'm getting this message:
 App with label django could not be found

 When searching the tests, django assumes that the app has no dot "." in
 the name. I believe the assumption is too strict and unnecessary. I'm
 using django 1.4.1

 I run into this problem because my own apps include dot in the name.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #10929: Support a default value for Sum (and possibly other aggregation functions)

[Django]

#10929: Support a default value for Sum (and possibly other aggregation 
functions)
-+-
 Reporter:  nolan|Owner:
 Type:  New feature  |   Status:  new
Component:  ORM aggregation  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  aggregate annotate   | Triage Stage:  Accepted
  default|  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by cvrebert):

 * cc: cvrebert (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 https://groups.google.com/groups/opt_out.

Re: [Django] #10227: OneToOne fields with null=True raise DoesNotExist exception on related model

[Django]

#10227: OneToOne fields with null=True raise DoesNotExist exception on related
model
-+-
 Reporter:  rvdrijst |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  onetoone related |  Needs documentation:  0
  expection null |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by cvrebert):

 * cc: cvrebert (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 https://groups.google.com/groups/opt_out.

Re: [Django] #3544: Fix {% include %} to allow recursive includes

[Django]

#3544: Fix {% include %} to allow recursive includes
-+-
 Reporter:  David Danier |Owner:  nobody
  |   Status:  new
 Type:  New feature  |  Version:  master
Component:  Template system  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  tplrf-patched|  Needs documentation:  1
Has patch:  0|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by cvrebert):

 * cc: cvrebert (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 https://groups.google.com/groups/opt_out.

[django/django] 723c9a: [py3] Ported the 'shell' management command.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 723c9a8c6db60108f584972498fa6bbd3b408444
  
https://github.com/django/django/commit/723c9a8c6db60108f584972498fa6bbd3b408444
  Author: Aymeric Augustin 
  Date:   2012-08-29 (Wed, 29 Aug 2012)

  Changed paths:
M django/core/management/commands/shell.py

  Log Message:
  ---
  [py3] Ported the 'shell' management command.

The user module and the execfile function were removed in Python 3.

Thanks Linovia for the report.



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18876: Use less error output

[Django]

#18876: Use less error output
-+-
 Reporter:  patroqueeet  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Core (Management |   Resolution:  duplicate
  commands)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 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
 * needs_better_patch:   => 0
 * resolution:   => duplicate
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 You are right in that masking exceptions is a bad thing. We are trying to
 improve the situation (see for example #18845). However, we have already
 improved things in current code, notably with
 [694bc0f22bdb30a472de6fec05a44adf5c0f1f2c] and
 [f2b6763ad7cb281ca8699a9c3d532a82f965be4f]. If you find something that's
 still not good enough in current code, feel free to reopen with a real
 case.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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 https://groups.google.com/groups/opt_out.

[Django] #18876: Use less error output

[Django]

#18876: Use less error output
+
 Reporter:  patroqueeet |  Owner:  nobody
 Type:  Cleanup/optimization| Status:  new
Component:  Core (Management commands)  |Version:  1.4
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 after upgrading from 1.2.7 to 1.3.1 I ran into error messages like "cannot
 import name XY". I had to use the PDB lib and heavy debugging to find out
 why. It should print the error source.

 I found out:
 in /django/core/management/base.py:206-207

 that
 {{{
 import traceback
 sys.stderr.write("%s" % traceback.print_tb(sys.exc_info()[2]))
 }}}

 helped a lot to tell me about the errors source.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18874: README should be referenced as README.rst

[Django]

#18874: README should be referenced as README.rst
--+
 Reporter:  brutasse  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  closed
Component:  Uncategorized |Version:  master
 Severity:  Normal| Resolution:  fixed
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  1 |  Easy pickings:  0
UI/UX:  0 |
--+
Changes (by Claude Paroz ):

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


Comment:

 In [adbdb18adc37eaffd2ff174853f8026bd29fb998]:
 {{{
 #!CommitTicketReference repository=""
 revision="adbdb18adc37eaffd2ff174853f8026bd29fb998"
 Fixed #18874 -- Updated new name of README.rst to auxiliary files
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] adbdb1: Fixed #18874 -- Updated new name of README.rst to ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: adbdb18adc37eaffd2ff174853f8026bd29fb998
  
https://github.com/django/django/commit/adbdb18adc37eaffd2ff174853f8026bd29fb998
  Author: Bruno Renié 
  Date:   2012-08-29 (Wed, 29 Aug 2012)

  Changed paths:
M MANIFEST.in
M setup.cfg

  Log Message:
  ---
  Fixed #18874 -- Updated new name of README.rst to auxiliary files



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #12698: ValidationError bug when passing a string message argument in model validation

[Django]

#12698: ValidationError bug when passing a string message argument in model
validation
-+-
 Reporter:  orokusaki|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  core.exceptions, |  Needs documentation:  0
  core.forms.models, model   |  Patch needs improvement:  0
  validation |UI/UX:  0
Has patch:  1|
  Needs tests:  1|
Easy pickings:  0|
-+-

Comment (by Kapura):

 I also tried to override validate_unique for one of my models that would
 check the name field against other data in the app to verify uniqueness
 before the save. In my opinion, the documentation should specify the
 limitations of validate_unique to discourage its use for raising errors,
 or deprecate it entirely and move all of the relevant code to clean().

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 4e70ad: Made FileSystemStorage accept both text and byte s...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4e70ad11d29bde54b846920ce0dcf8d10741d3ae
  
https://github.com/django/django/commit/4e70ad11d29bde54b846920ce0dcf8d10741d3ae
  Author: Claude Paroz 
  Date:   2012-08-29 (Wed, 29 Aug 2012)

  Changed paths:
M django/core/files/storage.py
M tests/regressiontests/file_storage/tests.py

  Log Message:
  ---
  Made FileSystemStorage accept both text and byte streams

Thanks Alexey Boriskin for his help on 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 https://groups.google.com/groups/opt_out.

Re: [Django] #4555: New html-util/filter: unescape

[Django]

#4555: New html-util/filter: unescape
-+-
 Reporter:  Johan Bergström  |Owner:  nobody
 |   Status:  closed
 Type:  Uncategorized|  Version:  master
Component:  Template system  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  unescape util|  decision needed
  filter |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 Well, that'd be lovely ... if my library wasn't handling the view layer
 also (and therefore preventing me from unescaping the code in the view).
 However, if Django REST framework is just following a bad practice, it's
 certainly not reasonable to add a filter just for one bad case.  I guess
 I'll just have to dig through the source for some underscored method to
 override or something ...

 Thanks for the explanation on the re-close!

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #13774: add optional rel_db_type() method for model field

[Django]

#13774: add optional rel_db_type() method for model field
-+-
 Reporter:  Suor |Owner:  Suor
 Type:  New feature  |   Status:  reopened
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  db, ForeignKey,  |  Needs documentation:  1
  related fields |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by sergeykolosov):

 * cc: sergeykolosov (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 https://groups.google.com/groups/opt_out.

[Django] #18875: Document that models.Options.get_latest_by supports integers

[Django]

#18875: Document that models.Options.get_latest_by supports integers
--+
 Reporter:  adamnelson|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 In the documentation
 
(https://docs.djangoproject.com/en/dev/ref/models/options/#django.db.models.Options.get_latest_by)
 , models.Options.get_latest_by specifies that !DateField and
 !DateTimeField are the only types supported for get_latest_by.  In fact,
 any orderable field type is supported
 (https://github.com/django/django/blob/master/django/db/models/query.py#L477).
 The documentation should simply replace "The name of a DateField or
 DateTimeField in the model." with "The name of a field in the model -
 typically a DateField, DateTimeField, or IntegerField."

 Using get_latest_by('id') is very useful for large tables where reverse
 sorting by 'id' is a proxy for latest.

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #18874: README should be referenced as README.rst

[Django]

#18874: README should be referenced as README.rst
--+
 Reporter:  brutasse  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Uncategorized |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 After this change:

 
https://github.com/django/django/commit/2cadd8623915227d594be2b5a2749435215dd240

 `MANIFEST.in` and `setup.cfg` still use README instead of README.rst. This
 prompts a warning during installation:

 {{{
 warning: no files found matching 'README'
 }}}

 The attached patch fixes that.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18871: admin.Site not exists

[Django]

#18871: admin.Site not exists
---+--
 Reporter:  mail6543210@…  |Owner:  nobody
 Type:  Bug|   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 thikonom):

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


Comment:

 Yes that's true. It should be admin.AdminSite

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18853: get_template_names() does not consider the queryset-only case

[Django]

#18853: get_template_names() does not consider the queryset-only case
---+--
 Reporter:  msopacua   |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Generic views  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  CBV| Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by msopacua):

 Replying to [comment:1 charettes]:
 > IMHO replacing the `hasattr(self, 'queryset') and self.queryset is not
 None` part by `getattr(self, 'queryset', None) is not None` would increase
 readability.

 Agreed, but it's inline with the coding style of the file, see line 150
 right above. Style fixes are the committers' realm. ;)

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #11739: ContentFile() does not support unicode data

[Django]

#11739: ContentFile() does not support unicode data
--+
 Reporter:  adamnelson|Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  File uploads/storage  |  Version:  1.1
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by aaugustin):

 I'm late to the party (I only noticed this ticket because it was fixed)
 but I liked lrekucki's proposal -- file content *is* binary.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #11739: ContentFile() does not support unicode data

[Django]

#11739: ContentFile() does not support unicode data
--+
 Reporter:  adamnelson|Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  File uploads/storage  |  Version:  1.1
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Claude Paroz ):

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


Comment:

 In [361d6738f89f8443855d4378d3241566d9fca6e9]:
 {{{
 #!CommitTicketReference repository=""
 revision="361d6738f89f8443855d4378d3241566d9fca6e9"
 Fixed #11739 -- Made ContentFile support Unicode input
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 361d67: Fixed #11739 -- Made ContentFile support Unicode i...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 361d6738f89f8443855d4378d3241566d9fca6e9
  
https://github.com/django/django/commit/361d6738f89f8443855d4378d3241566d9fca6e9
  Author: Claude Paroz 
  Date:   2012-08-29 (Wed, 29 Aug 2012)

  Changed paths:
M django/core/files/base.py
M docs/ref/files/file.txt
M tests/regressiontests/file_storage/tests.py

  Log Message:
  ---
  Fixed #11739 -- Made ContentFile support Unicode input


  Commit: b5240d25c1bf724f0008478e7f6cccd0a6d6bd1e
  
https://github.com/django/django/commit/b5240d25c1bf724f0008478e7f6cccd0a6d6bd1e
  Author: Claude Paroz 
  Date:   2012-08-29 (Wed, 29 Aug 2012)

  Changed paths:
M tests/modeltests/files/tests.py
M tests/regressiontests/file_storage/tests.py

  Log Message:
  ---
  Removed unnecessary bytes prefix for ContentFile


Compare: https://github.com/django/django/compare/ebc773ada3e4...b5240d25c1bf

-- 
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 https://groups.google.com/groups/opt_out.

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

[Django]

#18870: QuerySet.count() generates invalid sql when used with select_related() 
and
extra()
-+-
 Reporter:  bkvaiude@…   |Owner:  B001
 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|
-+-

Comment (by anonymous):

 As I checked in my app version is,
 import django; print(django.get_version())
 '''1.3.1'''

 There is no intention.

 BTW ,
 I solved it following way[[BR]]

 total=total.annotate().count() #Bug #18870 Link Reference:
 https://code.djangoproject.com/ticket/11459

 Thanks for reply.

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] ebc773: Replaced many smart_bytes by force_bytes

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ebc773ada3e4f40cf5084268387b873d7fe22e8b
  
https://github.com/django/django/commit/ebc773ada3e4f40cf5084268387b873d7fe22e8b
  Author: Claude Paroz 
  Date:   2012-08-29 (Wed, 29 Aug 2012)

  Changed paths:
M django/contrib/admin/util.py
M django/contrib/admin/views/main.py
M django/contrib/admindocs/utils.py
M django/contrib/auth/hashers.py
M django/contrib/gis/sitemaps/views.py
M django/contrib/markup/templatetags/markup.py
M django/contrib/sessions/backends/base.py
M django/contrib/staticfiles/storage.py
M django/core/cache/backends/db.py
M django/core/cache/backends/filebased.py
M django/core/files/base.py
M django/core/serializers/json.py
M django/core/serializers/pyyaml.py
M django/db/backends/oracle/base.py
M django/db/backends/util.py
M django/http/__init__.py
M django/templatetags/cache.py
M django/test/client.py
M django/test/testcases.py
M django/utils/cache.py
M django/utils/crypto.py
M django/utils/encoding.py
M django/utils/html.py
M django/views/debug.py
M docs/ref/models/instances.txt
M docs/ref/settings.txt
M docs/releases/1.5.txt
M docs/topics/cache.txt
M tests/regressiontests/admin_util/tests.py
M tests/regressiontests/admin_views/tests.py
M tests/regressiontests/file_uploads/tests.py
M tests/regressiontests/file_uploads/views.py

  Log Message:
  ---
  Replaced many smart_bytes by force_bytes

In all those occurrences, we didn't care about preserving the
lazy status of the strings, but we really wanted to obtain a
real bytestring.



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #17922: Add default "required" css classes to form labels

[Django]

#17922: Add default "required" css classes to form labels
-+
 Reporter:  hanson2010   |Owner:  nobody
 Type:  New feature  |   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:  0
Easy pickings:  0|UI/UX:  1
-+
Changes (by d1ffuz0r):

 * cc: d1fffuz0r@… (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 https://groups.google.com/groups/opt_out.

Re: [Django] #18063: repr() should return only ascii, not unicode

[Django]

#18063: repr() should return only ascii, not unicode
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by guettli):

 I read the documentation again:
 http://docs.python.org/reference/datamodel.html?highlight=repr#object.__repr__

 I admit that this is not a good solution:
 {{{
 []
 }}}

 What do you think about this solution? I can be used to recreate the
 object like suggested in the above link.

 {{{
 []
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18063: repr() should return only ascii, not unicode

[Django]

#18063: repr() should return only ascii, not unicode
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by guettli):

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


Comment:

 The Python documentation says about repr:

 {{{
 ... so it is important that the representation is information-rich and
 unambiguous
 }}}

 It should be **unambiguous**. For me a utf8 byte string is ambiguous. It
 could by a pure binary string, or it could be an other encoding like
 latin1. You get strange UnicodeErrors if you pass around utf8 byte strings
 in Python 2.x. It is hard to get to the root of the problem, especially if
 you are new to python.

 I understand Karen that she is worried about []
 looking strange and broken. But this output is much better than a unicode
 exception without any usable output.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #7005: add orphans support for object_list pagination

[Django]

#7005: add orphans support for object_list pagination
-+-
 Reporter:  shadfc   |Owner:  shadfc
 Type:  New feature  |   Status:  assigned
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  orphans object_list  | Triage Stage:  Accepted
  paginator  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by mjtamlyn):

 Seems to me it may be better to implement this in the context of CBVs as
 get_paginator_kwargs, a bit like get_form_kwargs rather than a separate
 method for each variable. Obviously we've got most of them already which
 we couldn't get rid of without backwards compat, but it's much more future
 proof.

-- 
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 https://groups.google.com/groups/opt_out.