Re: [Django] #16552: Missing app in Django admin dependency list.

[Django]

#16552: Missing app in Django admin dependency list.
+---
   Reporter:  zelo  |  Owner:  teraom
   Type:  Bug   | Status:  assigned
  Milestone:|  Component:  Documentation
Version:  1.3   |   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 teraom):

 * status:  new => assigned
 * owner:  nobody => teraom


-- 
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] #16597: FormWizard doco mentions get_template_names() but does not document it.

[Django]

#16597: FormWizard doco mentions get_template_names() but does not document it.
--+---
 Reporter:  FunkyBob  |  Owner:  nobody
 Type:  Bug   | Status:  new
Milestone:|  Component:  Documentation
  Version:  SVN   |   Severity:  Normal
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  1
UI/UX:  0 |
--+---
 Under the section "Creating templates for the forms" in
 https://docs.djangoproject.com/en/dev//ref/contrib/formtools/form-wizard
 /#creating-templates-for-the-forms it says "You can change this template
 name by overriding either the template_name attribute or the
 get_template_names() method, which is documented below", but it is not
 listed anywhere else on the page.

 Given it inherits from a TemplateView, it should probably link off to the
 TemplateView.get_template_names doco:
 https://docs.djangoproject.com/en/dev//ref/class-based-
 views/#django.views.generic.base.TemplateResponseMixin.get_template_names

-- 
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] #16565: An issue in databrowse's template object_detail.html

[Django]

#16565: An issue in databrowse's template object_detail.html
-+-
   Reporter:  leopku |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  contrib.databrowse
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:  databrowse,
   Triage Stage:  Ready for  |  template
  checkin|  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by anonymous):

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


Comment:

 looks good, I need it too so please check in :)

-- 
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] #16596: Tags within {% blocktrans %} blocks should work.

[Django]

#16596: Tags within {% blocktrans %} blocks should work.
--+--
 Reporter:  llugosch@…|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Milestone:|  Component:  Translations
  Version:  1.3   |   Severity:  Normal
 Keywords:  translation   |   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+--
 Tags within {% blocktrans %} blocks break. Presumably, Django's developers
 have it this way so that long {% if %} blocks and other switches don't get
 thrown at a helpless translator. An unfortunate consequence is that
 translated sentences containing tags need to be rewritten, and sometimes
 this is completely impossible. The alternative is to split the sentence
 awkwardly where the tag occurs. For example,

 This sentence was translated at {% now %} by the good linguists at {% get
 url etc. etc. %}!

 would have to be formatted as something awful like

 {% trans "This sentence was translated at" %}{% now %}{% trans " by the
 good linguists at" %} {% get url etc. etc. %}!

 Wouldn't it be better for Djangonaut and translator alike if it could be
 done like this:

 {% blocktrans %}This sentence was translated at {% now %} by the good
 linguists at {% get url etc. etc. %}!{% endblocktrans %}

 ?

-- 
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] #16591: Bad reference to YEAR_CHOICES

[Django]

#16591: Bad reference to YEAR_CHOICES
-+-
   Reporter: |  Owner:  elbarto
  santi.romero@… | Status:  new
   Type:  Bug|  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:  example, reference,
 Resolution: |  name
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
Changes (by elbarto):

 * has_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #16595: SessionBase docs don't mention pop()

[Django]

#16595: SessionBase docs don't mention pop()
--+---
 Reporter:  wilfred@… |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Milestone:|  Component:  Documentation
  Version:  1.3   |   Severity:  Normal
 Keywords:  SessionBase pop   |   Triage Stage:  Unreviewed
Has patch:  1 |  Easy pickings:  0
UI/UX:  0 |
--+---
 The functionality has been there since 2007, and it would be nice to
 mention that you can do `request.session.pop('foo')`.

-- 
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] #16594: Missing altitude (z) on Point on admin interface for geodjango

[Django]

#16594: Missing altitude (z) on Point on admin interface for geodjango
+
 Reporter:  info@…  |  Owner:  nobody
 Type:  Bug | Status:  new
Milestone:  |  Component:  GIS
  Version:  1.3 |   Severity:  Normal
 Keywords:  |   Triage Stage:  Unreviewed
Has patch:  0   |  Easy pickings:  0
UI/UX:  0   |
+
 I am using a model with a 3d Point field, although in the database I can
 see correctly the z component in the admin section for the Point field I
 see only the x,y component i.e. POINT(x_value y_value ) instead of
 POINT(x_value y_value z_value).

 Thanks!

 Luca

-- 
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] #16590: ContentType does not have name attribute

[Django]

#16590: ContentType does not have name attribute
+---
   Reporter:  oinopion  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Milestone:|  Component:  Documentation
Version:  SVN   |   Severity:  Normal
 Resolution:|   Keywords:  files
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  1
  UI/UX:  0 |
+---

Comment (by oinopion):

 How about empty string by default and optional __init__ parameter? Not
 perfect solution, but will make !ContentFile substitutable for File in
 more places (http://en.wikipedia.org/wiki/Liskov_substitution_principle)

 I use !ContentFile a lot in tests, where I don't want to touch file system
 if not needed. Having to check ```hasattr(file, 'name')``` is a bit
 frustrating.

-- 
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] #11665: django.test.TestCase should flush constraints

[Django]

#11665: django.test.TestCase should flush constraints
+---
   Reporter:  Glenn |  Owner:
   Type:  Bug   | Status:  new
  Milestone:|  Component:  Testing framework
Version:  SVN   |   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 jsdalton):

 Quick clarification to my comment above. The errors I came across in MySQL
 are not related to this patch or ticket, and they all have tickets opened
 for them.

 Here's the test output:


 {{{
 $ ./runtests.py --settings=testproject.settings
 Creating test database for alias 'default'...
 Creating test database for alias 'other'...
 

[Django] #16593: Quick fix for proxy_model_inheritance tests

[Django]

#16593: Quick fix for proxy_model_inheritance tests
+--
 Reporter:  jsdalton|  Owner:  nobody
 Type:  | Status:  new
  Cleanup/optimization  |  Component:  Database layer (models, ORM)
Milestone:  |   Severity:  Normal
  Version:  SVN |   Triage Stage:  Unreviewed
 Keywords:  |  Easy pickings:  1
Has patch:  0   |
UI/UX:  0   |
+--
 The error I just now reported in #16592 revealed another fairly minor
 problem with the proxy_model_inheritance tests which should be easy to
 fix.

 The test is exercising the syncdb command and then verifying the existence
 of certain tables. However, the call to syncdb is being made in the
 `setUp()` method instead of the test case itself. As a result, if there is
 an error when executing it (as happens with #16592), the tearDown() method
 is not called. This means the remainder of the test suite will be executed
 with a modified sys.path and settings.INSTALLED_APPS. Sure enough, this
 causes some other unrelated failures which do not occur when the tests are
 run in isolation.

 Reproduce it with:

 {{{
 $ ./runtests.py --settings=testproject.settings unmanaged_models
 proxy_model_inheritance bug8245
 Creating test database for alias 'default'...
 Creating test database for alias 'other'...
 ...EF
 ==
 ERROR: test_table_exists
 (modeltests.proxy_model_inheritance.tests.ProxyModelInheritanceTests)
 --
 Traceback (most recent call last):
   File
 
"/Users/jsdalton/webs/testproject/src/django/tests/modeltests/proxy_model_inheritance/tests.py",
 line 25, in setUp
 call_command('syncdb', verbosity=0)
   File
 
"/Users/jsdalton/webs/testproject/src/django/django/core/management/__init__.py",
 line 166, in call_command
 return klass.execute(*args, **defaults)
   File
 "/Users/jsdalton/webs/testproject/src/django/django/core/management/base.py",
 line 220, in execute
 output = self.handle(*args, **options)
   File
 "/Users/jsdalton/webs/testproject/src/django/django/core/management/base.py",
 line 351, in handle
 return self.handle_noargs(**options)
   File
 
"/Users/jsdalton/webs/testproject/src/django/django/core/management/commands/syncdb.py",
 line 121, in handle_noargs
 custom_sql = custom_sql_for_model(model, self.style, connection)
   File
 "/Users/jsdalton/webs/testproject/src/django/django/core/management/sql.py",
 line 150, in custom_sql_for_model
 app_dir =
 
os.path.normpath(os.path.join(os.path.dirname(models.get_app(model._meta.app_label).__file__),
 'sql'))
   File
 "/Users/jsdalton/webs/testproject/src/django/django/db/models/loading.py",
 line 151, in get_app
 raise ImproperlyConfigured("App with label %s could not be found" %
 app_label)
 ImproperlyConfigured: App with label unmanaged_models could not be found

 ==
 FAIL: test_bug_8245 (regressiontests.bug8245.tests.Bug8245Test)
 --
 Traceback (most recent call last):
   File
 
"/Users/jsdalton/webs/testproject/src/django/tests/regressiontests/bug8245/tests.py",
 line 18, in test_bug_8245
 'autodiscover should have raised a "Bad admin module" error.')
 AssertionError: autodiscover should have raised a "Bad admin module"
 error.

 --
 Ran 5 tests in 2.417s

 FAILED (failures=1, errors=1)
 Destroying test database for alias 'default'...
 Destroying test database for alias 'other'...
 }}}

 That second failure seems to be caused by the test structure.

 The attached patch moves the call where it should be (part of the test
 case) and resolves the issue. A minor cleanup, but will save other
 developers time in the future if a regression occurs.

-- 
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] #16592: In MySQL, table names in unmanaged intermediate models are being lower cased

[Django]

#16592: In MySQL, table names in unmanaged intermediate models are being lower
cased
--+--
 Reporter:  jsdalton  |  Owner:  nobody
 Type:  Bug   | Status:  new
Milestone:|  Component:  Database layer (models, ORM)
  Version:  SVN   |   Severity:  Normal
 Keywords:  mysql |   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+--
 This is an obscure error, but it's causing an error in the MySQL (InnoDB)
 test suite when the entire suite is run. The error can be replicated as
 follows:


 {{{
 $ ./runtests.py --settings=testproject.settings unmanaged_models
 proxy_model_inheritance
 Creating test database for alias 'default'...
 Creating test database for alias 'other'...
 ...E
 ==
 ERROR: test_table_exists
 (modeltests.proxy_model_inheritance.tests.ProxyModelInheritanceTests)
 --
 Traceback (most recent call last):
   File
 
"/Users/jsdalton/webs/testproject/src/django/tests/modeltests/proxy_model_inheritance/tests.py",
 line 25, in setUp
 call_command('syncdb', verbosity=0)
   File
 
"/Users/jsdalton/webs/testproject/src/django/django/core/management/__init__.py",
 line 166, in call_command
 return klass.execute(*args, **defaults)
   File
 "/Users/jsdalton/webs/testproject/src/django/django/core/management/base.py",
 line 220, in execute
 output = self.handle(*args, **options)
   File
 "/Users/jsdalton/webs/testproject/src/django/django/core/management/base.py",
 line 351, in handle
 return self.handle_noargs(**options)
   File
 
"/Users/jsdalton/webs/testproject/src/django/django/core/management/commands/syncdb.py",
 line 121, in handle_noargs
 custom_sql = custom_sql_for_model(model, self.style, connection)
   File
 "/Users/jsdalton/webs/testproject/src/django/django/core/management/sql.py",
 line 150, in custom_sql_for_model
 app_dir =
 
os.path.normpath(os.path.join(os.path.dirname(models.get_app(model._meta.app_label).__file__),
 'sql'))
   File
 "/Users/jsdalton/webs/testproject/src/django/django/db/models/loading.py",
 line 151, in get_app
 raise ImproperlyConfigured("App with label %s could not be found" %
 app_label)
 ImproperlyConfigured: App with label unmanaged_models could not be found

 --
 Ran 4 tests in 2.080s

 FAILED (errors=1)
 Destroying test database for alias 'default'...
 Destroying test database for alias 'other'...
 }}}


 In brief, the syncdb command is hiccoughing in the proxy_model_inheritance
 test because the previously installed model `Intermediate` (from
 unmanaged_model) is not getting filtered properly. The reason it is not
 getting filtered properly is that the db_table specified in the model
 definition is "D01" but the MySQL table name is "d01". In Postegres and
 other backends, the table name is correct as "D01".

 I'm digging around trying to find where this is happening but I don't know
 this part of the code base very well. If anyone has a lead let me know and
 I'd be happy to put together a 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.

Re: [Django] #16589: ModelForm documentation error (saving unbound form)

[Django]

#16589: ModelForm documentation error (saving unbound form)
--+---
   Reporter:  toby@…  |  Owner:  nobody
   Type:  Bug | Status:  new
  Milestone:  |  Component:  Documentation
Version:  1.3 |   Severity:  Normal
 Resolution:  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+---
Changes (by aaugustin):

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


Comment:

 Since `ArticleForm` receives an `instance` argument, it is bound, isn't
 it? Did I miss something obvious?

-- 
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] #16554: Unnecessary join when using a reverse foreign-key relationship in separate filter or aggregate calls

[Django]

#16554: Unnecessary join when using a reverse foreign-key relationship in 
separate
filter or aggregate calls
-+-
   Reporter: |  Owner:  nobody
  bendavis78 | Status:  closed
   Type:  Bug|  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  SVN|   Severity:  Normal
 Resolution:  invalid|   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by akaariai):

 If I am not mistaken, the aggregate example is valid - it produces wrong
 results. Author having two different SCIFI books will have pages
 calculated twice.

 But the chained filters is not valid, as one query is asking for a model
 which has a book with genre of SCIFI and more than 500 pages, the other is
 asking for a model which has a book with genre of SCIFI and a book which
 has more than 500 pages. So, in the first example there must be one
 matching book, in the second example the books matching the condition can
 be different ones.

 I am leaving this as closed, as I don't know what to do for a half-valid
 ticket and I haven't actually verified that the aggregate example produces
 wrong results.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #16591: Bad reference to YEAR_CHOICES

[Django]

#16591: Bad reference to YEAR_CHOICES
-+-
   Reporter: |  Owner:  nobody
  santi.romero@… | Status:  new
   Type:  Bug|  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:  example, reference,
 Resolution: |  name
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
Changes (by aaugustin):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #16549: In Django models, modified-rows count would help in handling optimistic concurrency control problems

[Django]

#16549: In Django models, modified-rows count would help in handling optimistic
concurrency control problems
-+-
   Reporter: |  Owner:  nobody
  estebistec | Status:  new
   Type:  New|  Component:  Database layer
  feature|  (models, ORM)
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  0
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by estebistec):

 A sub-class is fair enough, yeah. Especially given that the situations are
 probably off the beaten path.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #5423: "dumpdata" should stream output one row at a time

[Django]

#5423: "dumpdata" should stream output one row at a time
-+-
   Reporter:  adrian |  Owner:  ramiro
   Type:  New| Status:  assigned
  feature|  Component:  Core
  Milestone: |  (Serialization)
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:  dumpdata fixtures
   Triage Stage:  Accepted   |  memory
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  1  |Needs tests:  0
  UI/UX:  0  |  Easy pickings:  0
-+-
Changes (by ben@…):

 * cc: ben@… (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] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
-+-
   Reporter:  Marcob |  Owner:  nobody
    | Status:  new
   Type:  New|  Component:  contrib.admin
  feature|   Severity:  Normal
  Milestone: |   Keywords:  raw-id-fields nfa-
Version:  SVN|  someday design_ux
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  1
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  1  |
  UI/UX:  1  |
-+-

Comment (by ramiro):

 Latest path is using !AdminSite's `root_path` that  doesn't exit anymore
 (see r16575). Also, I don't like it is reintroducing using
 `'../../..'`-style paths we are trying to move away from (see r16578,
 #15294)

-- 
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] #16587: get_or_create duplicate entry with together_unique

[Django]

#16587: get_or_create duplicate entry with together_unique
-+-
   Reporter: |  Owner:  nobody
  lazzaroleonardo@…  | Status:  closed
   Type:  Bug|  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  SVN|   Severity:  Normal
 Resolution:  invalid|   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by llazzaro):

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


Comment:

 the problemas was with auto_now_add=True in DateField

-- 
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] #15252: get_static_url in static templatetags

[Django]

#15252: get_static_url in static templatetags
-+-
   Reporter:  ohardy |  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  contrib.staticfiles
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by streeter):

 * cc: streeter (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] #16591: Bad reference to YEAR_CHOICES

[Django]

#16591: Bad reference to YEAR_CHOICES
--+---
 Reporter:  santi.romero@…|  Owner:  nobody
 Type:  Bug   | Status:  new
Milestone:|  Component:  Documentation
  Version:  1.3   |   Severity:  Normal
 Keywords:  example, reference, name  |   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+---
 Example in the following URL ("Setting arguments for widgets") has invalid
 references to YEAR_CHOICES, RADIO_CHOICES and CHECKBOX_CHOICES. Names used
 in definitions are BIRTH_YEAR_CHOICES, GENDER_CHOICES and
 FAVOURITE_COLORS_CHOICES, respectively.

 https://docs.djangoproject.com/en/dev/ref/forms/widgets/#setting-
 arguments-for-widgets

-- 
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] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
-+-
   Reporter:  Marcob |  Owner:  nobody
    | Status:  new
   Type:  New|  Component:  contrib.admin
  feature|   Severity:  Normal
  Milestone: |   Keywords:  raw-id-fields nfa-
Version:  SVN|  someday design_ux
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  1
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  1  |
  UI/UX:  1  |
-+-

Comment (by Stanislas Guerra ):

 Patch against trunk 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] #116: Default admin media doesn't display for 'django-admin runserver'

[Django]

#116: Default admin media doesn't display for 'django-admin runserver'
-+-
   Reporter:  espen@…|  Owner:  adrian
   Type: | Status:  closed
  Uncategorized  |  Component:  contrib.admin
  Milestone: |   Severity:  normal
Version: |   Keywords:
 Resolution: |  Has patch:  1
  worksforme |Needs tests:  0
   Triage Stage:  Ready for  |  Easy pickings:  0
  checkin|
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by jezdez):

 * status:  reopened => closed
 * needs_docs:  1 => 0
 * resolution:   => worksforme
 * needs_tests:  1 => 0


Comment:

 Please don't reopen tickets that have been closed as WORKSFORME.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #11948: Linear referencing for Django

[Django]

#11948: Linear referencing for Django
--+
   Reporter:  novalis |  Owner:  nobody
   Type:  New feature | Status:  new
  Milestone:  |  Component:  GIS
Version:  SVN |   Severity:  Normal
 Resolution:  |   Keywords:
   Triage Stage:  Design decision needed  |  Has patch:  1
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
Changes (by anonymous):

 * ui_ux:   => 0
 * easy:   => 0


Comment:

 I needed to use linearref feature from my application and so patched my
 django code. The patch targets an older version of django, so a little
 refresh was needed, but now it works nicely.

 I attach the patch used for building a 1.3 for ubuntu maverick
 (http://ppa.launchpad.net/chris-lea/python-django/ubuntu)

-- 
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] #116: Default admin media doesn't display for 'django-admin runserver'

[Django]

#116: Default admin media doesn't display for 'django-admin runserver'
-+-
   Reporter:  espen@…|  Owner:  adrian
   Type: | Status:  reopened
  Uncategorized  |  Component:  contrib.admin
  Milestone: |   Severity:  normal
Version: |   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  1
  checkin|  Easy pickings:  0
Needs documentation:  1  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by nnseva):

 * status:  closed => reopened
 * cc: nnseva (added)
 * type:  defect => Uncategorized
 * needs_tests:  0 => 1
 * easy:   => 0
 * needs_docs:  0 => 1
 * has_patch:  0 => 1
 * ui_ux:   => 0
 * resolution:  worksforme =>


Comment:

 The issue has been reopened for django developers who can apply the patch
 to the 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #16590: ContentType does not have name attribute

[Django]

#16590: ContentType does not have name attribute
--+--
 Reporter:  oinopion  |  Owner:  nobody
 Type:  Bug   | Status:  new
Milestone:|  Component:  Core (Other)
  Version:  SVN   |   Severity:  Normal
 Keywords:  files |   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  1
UI/UX:  0 |
--+--
 !ContentFile is subclass of File and it should inherit it's interface, but
 name attribute is not set in constructor.

 -
 
[https://code.djangoproject.com/browser/django/trunk/django/core/files/base.py#L121
 ConentFile source]
 - [https://docs.djangoproject.com/en/dev/ref/files/file/#the-contentfile-
 class ContentFile 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] #16589: ModelForm documentation error (saving unbound form)

[Django]

#16589: ModelForm documentation error (saving unbound form)
+---
 Reporter:  toby@…  |  Owner:  nobody
 Type:  Bug | Status:  new
Milestone:  |  Component:  Documentation
  Version:  1.3 |   Severity:  Normal
 Keywords:  |   Triage Stage:  Unreviewed
Has patch:  0   |  Easy pickings:  0
UI/UX:  0   |
+---
 The ModelForm documentation has the following snippet:

 {{{
 # Create a form to edit an existing Article.
 >>> a = Article.objects.get(pk=1)
 >>> f = ArticleForm(instance=a)
 >>> f.save()
 }}}

 Since the form is unbound, that f.save() is going to fail. Maybe that
 should be:

 {{{
 print f
 }}}

-- 
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] #15252: get_static_url in static templatetags

[Django]

#15252: get_static_url in static templatetags
-+-
   Reporter:  ohardy |  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  contrib.staticfiles
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by jezdez):

 * needs_docs:  1 => 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] #9268: Pass custom form values from post-comment to preview-comment

[Django]

#9268: Pass custom form values from post-comment to preview-comment
-+-
   Reporter:  taojian|  Owner:  stuartk
   Type: | Status:  closed
  Uncategorized  |  Component:  contrib.comments
  Milestone:  1.1|   Severity:  Normal
Version:  SVN|   Keywords:  comment preview
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  1  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by anonymous):

 http://www.firminite.com/treatments-for-erectile-dysfunction.php
 http://www.firminite.com/how-can-i-to-do-last-longer.php
 http://www.firminite.com/how-to-men-last-longer-in-bed.php
 http://www.firminite.com/how-to-last-longer-in-bed-for-men.php
 http://www.firminite.com/testosterone-levels-for-men.php

-- 
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] #9268: Pass custom form values from post-comment to preview-comment

[Django]

#9268: Pass custom form values from post-comment to preview-comment
-+-
   Reporter:  taojian|  Owner:  stuartk
   Type: | Status:  closed
  Uncategorized  |  Component:  contrib.comments
  Milestone:  1.1|   Severity:  Normal
Version:  SVN|   Keywords:  comment preview
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  1  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by fedrik):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 Thanks for the nice article.
 http://www.firminite.com/treatments-for-erectile-dysfunction.php
 http://www.firminite.com/how-can-i-to-do-last-longer.php
 http://www.firminite.com/how-to-men-last-longer-in-bed.php
 http://www.firminite.com/how-to-last-longer-in-bed-for-men.php
 http://www.firminite.com/testosterone-levels-for-men.php
 http://www.firminite.com/last-longer-pills.php
 http://www.firminite.com/how-to-last-longer-in-bed.php

-- 
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.