Re: [Django] #20003: URLValidator does not accept urls with usernames or passwords in them

[Django]

#20003: URLValidator does not accept urls with usernames or passwords in them
---+
 Reporter:  marshall@… |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords:  URLValidator   | 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):

 * stage:  Unreviewed => Accepted


Comment:

 http://url.spec.whatwg.org/#concept-url-userinfo

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20004: move test helpers out of TransactionTestCase

[Django]

#20004: move test helpers out of TransactionTestCase
--+
 Reporter:  zalew |Owner:  zalew
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Testing framework |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  testing   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20005: Document that Oracle databases need execute permission on SYS.DBMS_LOB.

[Django]

#20005: Document that Oracle databases need execute permission on SYS.DBMS_LOB.
-+-
 Reporter:  jafula   |  Owner:  nobody
 Type:   | Status:  new
  Uncategorized  |Version:  1.5
Component:   |   Keywords:  oracle database permission dbms_lob
  Documentation  |  Has patch:  0
 Severity:  Normal   |  UI/UX:  0
 Triage Stage:   |
  Unreviewed |
Easy pickings:  0|
-+-
 The oracle database back-end uses SYS.DBMS_LOB. Could the documentation
 about Oracle on the database page be updated to include this?

 You can find the reference to dbms_lob in
 django\db\backends\oracle\base.py

 The permission required is:

 grant execute on SYS.DBMS_LOB to SCHEMA_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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19582: Add tutorial on static files

[Django]

#19582: Add tutorial on static files
-+-
 Reporter:  jpic |Owner:  timo
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  docs, static files,  |  Needs documentation:  0
  sprint2013 |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-

Comment (by timo):

 Updated pull request (includes #19897):
 https://github.com/django/django/pull/889
 rendered: http://techytim.com/django/19897/intro/tutorial06.html

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19897: Improve static files documentation

[Django]

#19897: Improve static files documentation
--+
 Reporter:  wimfeijen |Owner:  timo
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  staticfiles   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * stage:  Ready for checkin => Accepted


Comment:

 Forgive me if I've missed IRC conversations that discuss the following. I
 appreciate the clarity this change adds by removing some redundant
 information, however, it seems to remove some potentially useful
 information as well.

 1. The instructions for upgrading from django-staticfiles were removed.
 I'm assuming this is fine since we still have those instructions in older
 versions of the docs and they aren't useful in the long run as we have
 less people upgrading as time goes on.

 2. The discussion of `STATIC_URL` and `TEMPLATE_CONTEXT_PROCESSORS` was
 removed. I understand if we don't want to promote this method.

 {{{

 The included context processor is the easy way. Simply make sure
 ``'django.core.context_processors.static'`` is in your
 :setting:`TEMPLATE_CONTEXT_PROCESSORS`. It's there by default, and if
 you're
 editing that setting by hand it should look something like::

 TEMPLATE_CONTEXT_PROCESSORS = (
 'django.core.context_processors.debug',
 'django.core.context_processors.i18n',
 'django.core.context_processors.media',
 'django.core.context_processors.static',
 'django.contrib.auth.context_processors.auth',
 'django.contrib.messages.context_processors.messages',
 )

 Once that's done, you can refer to :setting:`STATIC_URL` in your
 templates:

 .. code-block:: html+django

  

 If ``{{ STATIC_URL }}`` isn't working in your template, you're probably
 not
 using :class:`~django.template.RequestContext` when rendering the
 template.

 As a brief refresher, context processors add variables into the contexts
 of
 every template. However, context processors require that you use
 :class:`~django.template.RequestContext` when rendering templates. This
 happens
 automatically if you're using a :doc:`generic view `,
 but in views written by hand you'll need to explicitly use
 ``RequestContext``
 To see how that works, and to read more details, check out
 :ref:`subclassing-context-requestcontext`.

 Another option is the :ttag:`get_static_prefix` template tag that is part
 of
 Django's core.
 }}}

 ... as well as a note describing the differences between
 `MEDIA_ROOT`/`MEDIA_URL` and `STATIC_ROOT`/`STATIC_URL`. While it
 references "previous versions of Django", it still seems useful to me in
 describing the differences even for those who are coming to Django for the
 first time.

 {{{

 .. note::

In previous versions of Django, it was common to place static assets in
:setting:`MEDIA_ROOT` along with user-uploaded files, and serve them
 both
at :setting:`MEDIA_URL`. Part of the purpose of introducing the
``staticfiles`` app is to make it easier to keep static files separate
from user-uploaded files.

For this reason, you need to make your :setting:`MEDIA_ROOT` and
:setting:`MEDIA_URL` different from your :setting:`STATIC_ROOT` and
:setting:`STATIC_URL`. You will need to arrange for serving of files in
:setting:`MEDIA_ROOT` yourself; ``staticfiles`` does not deal with
user-uploaded files at all. You can, however, use
:func:`django.views.static.serve` view for serving
 :setting:`MEDIA_ROOT`
in development; see :ref:`staticfiles-other-directories`.

 }}}

 4. The documentation for `django.views.static.serve` and
 `django.conf.urls.static.static` was removed. I don't think we should
 remove them since our policy is that anything that's documented is "stable
 API."

 {{{
 .. _staticfiles-other-directories:

 Serving other directories
 --

 .. currentmodule:: django.views.static
 .. function:: serve(request, path, document_root, show_indexes=False)

 There may be files other than your project's static assets that, for
 convenience, you'd like to have Django serve for you in local development.
 The :func:`~django.views.static.serve` view can be used to serve any
 directory
 you give it. (Again, this view is **not** hardened for production
 use, and should be used only as a development aid; you should serve these
 files
 in production using a real front-end webserver).

 The most likely example is user-uploaded content in :setting:`MEDIA_ROOT`.
 

Re: [Django] #20004: move test helpers out of TransactionTestCase

[Django]

#20004: move test helpers out of TransactionTestCase
-+-
 Reporter:  zalew|Owner:  zalew
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.5
Component:  Testing framework|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  testing  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by zalew):

 * status:  new => assigned
 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20004: move test helpers out of TransactionTestCase

[Django]

#20004: move test helpers out of TransactionTestCase
--+-
 Reporter:  zalew |  Owner:  zalew
 Type:  Cleanup/optimization  | Status:  new
Component:  Testing framework |Version:  1.5
 Severity:  Normal|   Keywords:  testing
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 django.test.testcases.TestCase inherits from TransactionTestCase, so when
 django.db is not used in the project, it complains during testing about
 "ImproperlyConfigured: settings.DATABASES". A solution is to use
 SimpleTestCase (which TransactionTestCase inherits from), but this class
 doesn't contain the useful test helpers currently located in
 TransactionTestCase, which aren't in any way related to db handling:

 * assertRedirects
 * assert(Not)Contains
 * assertFormError
 * assertTemplate(Not)Used
 * _urlconf_setup(teardown).

 Proposal: move them out either to SimpleTestCase, or a separate class
 other tests (including TransactionTestCase) can inherit from, so they can
 be used in non-db test cases.

 ref: https://github.com/django/django/blob/master/django/test/testcases.py

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19992: Put protection against unsafe redirects into `HttpResponseRedirectBase`

[Django]

#19992: Put protection against unsafe redirects into `HttpResponseRedirectBase`
---+
 Reporter:  coolRR |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  security   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by coolRR):

 I agree with the idea of a `safe` flag to functions that do a redirect.
 (Which I guess is `redirect` and the constructor for the redirect
 response, possibly several more?)

 I would think though whether it's correct to call it `safe`, because it
 might just mean "local", and calling it safe might give an illusion of
 safety. But I don't feel strongly about the name.

 Now, the thing is, since we'll have `safe=True` by default, existing apps
 will break. So I think that this functionality needs to be turned on and
 off on an app-by-app basis. I suggest it being off by default, but that
 you could turn it on for each app individually, so you could turn it on
 for your apps without breaking the third-party apps that you're using.

 What do you think?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20003: URLValidator does not accept urls with usernames or passwords in them

[Django]

#20003: URLValidator does not accept urls with usernames or passwords in them
---+--
 Reporter:  marshall@… |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Uncategorized  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords:  URLValidator   | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by marshall@…):

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


Comment:

 Sorry, readline munged the display, what you should see for the first two
 lines are:

 {{{
 In [1]: from django.core.validators import URLValidator

 In [2]: URLValidator()('https://user:p...@domain.com')
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20003: URLValidator does not accept urls with usernames or passwords in them

[Django]

#20003: URLValidator does not accept urls with usernames or passwords in them
---+--
 Reporter:  marshall@… |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.5
 Severity:  Normal |   Keywords:  URLValidator
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 {{{
 In [1]: URLValidator()('https://user:pass@from django.core.validators
 import URLValidator

 In [2]: from django.core.validators
 importURLValidator()('https://user:p...@domain.com')
 ---
 ValidationError   Traceback (most recent call
 last)
  in ()
 > 1 URLValidator()('https://user:p...@domain.com')

 /Users/marshall/.virtualenvs/django/lib/python2.7/site-
 packages/django/core/validators.pyc in __call__(self, value)
  72 raise e
  73 url = urlparse.urlunsplit((scheme, netloc, path,
 query, fragment))
 ---> 74 super(URLValidator, self).__call__(url)
  75 else:
  76 raise

 /Users/marshall/.virtualenvs/django/lib/python2.7/site-
 packages/django/core/validators.pyc in __call__(self, value)
  42 """
  43 if not self.regex.search(smart_unicode(value)):
 ---> 44 raise ValidationError(self.message, code=self.code)
  45
  46 class URLValidator(RegexValidator):

 ValidationError: [u'Enter a valid value.']
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #11569: django.core.cache.backends.db has bad transaction handling

[Django]

#11569: django.core.cache.backends.db has bad transaction handling
-+-
 Reporter:  Glenn|Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Core (Cache system)  |  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):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #6623: commit_manually decorator: Better error message (show exception)

[Django]

#6623: commit_manually decorator: Better error message (show exception)
-+-
 Reporter:  guettli  |Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * owner:  jacob => aaugustin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #10744: transaction.leave_transaction_management leaks

[Django]

#10744: transaction.leave_transaction_management leaks
-+-
 Reporter:  Glenn|Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #10813: Database errors in the shell should roll back the transaction

[Django]

#10813: Database errors in the shell should roll back the transaction
-+-
 Reporter:  Glenn|Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #11156: Unnecessary savepoints with Oracle

[Django]

#11156: Unnecessary savepoints with Oracle
-+-
 Reporter:  Richard Davies   |Owner:  aaugustin
   |   Status:  assigned
 Type:   |  Version:  master
  Cleanup/optimization   |   Resolution:
Component:  Database layer   | Triage Stage:  Accepted
  (models, ORM)  |  Needs documentation:  0
 Severity:  Normal   |  Patch needs improvement:  0
 Keywords:  oracle savepoints|UI/UX:  0
Has patch:  1|
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19916: contrib.comments's templatetags use token.contents.split()

[Django]

#19916: contrib.comments's templatetags use token.contents.split()
-+-
 Reporter:  bmispelon|Owner:  bmispelon
 Type:  Bug  |   Status:  closed
Component:  contrib.comments |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by claudep):

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


Comment:

 Pull request merged in 81804ae474d6fe5d3ab9348cfe86ee3779473a2a (Fix
 19916. Smarter tokenizing of contrib.comment's templatetags arguments. )

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13870: Document transaction/connection management outside the web server context

[Django]

#13870: Document transaction/connection management outside the web server 
context
---+-
 Reporter:  patrys |Owner:  aaugustin
 Type:  New feature|   Status:  assigned
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by aaugustin):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #15117: get_or_create() raises "DatabaseError: no such savepoint" instead of IntegrityError (PostgreSQL)

[Django]

#15117: get_or_create() raises "DatabaseError: no such savepoint" instead of
IntegrityError (PostgreSQL)
-+-
 Reporter:  akaihola |Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
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 aaugustin):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16367: Exceptions thrown by middleware.process_response don't get to middleware.process_exception

[Django]

#16367: Exceptions thrown by middleware.process_response don't get to
middleware.process_exception
-+-
 Reporter:  bob84123 |Owner:  aaugustin
 Type:  New feature  |   Status:  assigned
Component:  Core (Other) |  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  1|  Needs documentation:  1
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17341: Model.save() commits transactions after every parent class save

[Django]

#17341: Model.save() commits transactions after every parent class save
-+-
 Reporter:  akaariai |Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.3
  (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 aaugustin):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #15694: Overriding Django admin views and nested transactions

[Django]

#15694: Overriding Django admin views and nested transactions
-+-
 Reporter:  etianen  |Owner:  aaugustin
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  1|  Needs documentation:  1
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16374: ExceptionReporter may re-evaluate error-causing queryset, leading to a later DatabaseError that masks the original one

[Django]

#16374: ExceptionReporter may re-evaluate error-causing queryset, leading to a
later DatabaseError that masks the original one
-+-
 Reporter:  aaron|Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  1.3
 Severity:  Normal   |   Resolution:
 Keywords:  ExceptionReporter| Triage Stage:  Accepted
  DatabaseError current transaction  |  Needs documentation:  0
  aborted error queryset |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18004: Django should not use `force_unicode(..., errors='replace')` when parsing POST data.

[Django]

#18004: Django should not use `force_unicode(..., errors='replace')` when 
parsing
POST data.
-+-
 Reporter:  mrmachine|Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  HTTP handling|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  post data unicode| Triage Stage:  Design
  utf8 encode decode transaction |  decision needed
  aborted|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * status:  new => assigned


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17887: postgresql_psycopg2 sometimes leaves connections "idle in transaction"

[Django]

#17887: postgresql_psycopg2 sometimes leaves connections "idle in transaction"
-+-
 Reporter:  brodie   |Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  psycopg2 |  Needs documentation:  0
  transactions   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #8320: Admin Transaction Management Error

[Django]

#8320: Admin Transaction Management Error
---+
 Reporter:  holdenweb  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin transaction  | 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):

 * status:  reopened => new


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #13906: REPEATABLE READ (as used by default on MySQL) breaks atleast QuerySet.get_or_create().

[Django]

#13906: REPEATABLE READ (as used by default on MySQL) breaks atleast
QuerySet.get_or_create().
-+-
 Reporter:  sebastian_noack  |Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:  mysql transaction|  Patch needs improvement:  1
  isolation  |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #8320: Admin Transaction Management Error

[Django]

#8320: Admin Transaction Management Error
---+-
 Reporter:  holdenweb  |Owner:  aaugustin
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin transaction  | 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):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20002: Model inheritance depth may result in invalid SQL queries

[Django]

#20002: Model inheritance depth may result in invalid SQL queries
--+
 Reporter:  Keryn Knight    |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 This is an example pulled out of the test case I was writing as a baseline
 for something kind of crazy, and on '''1.4''' to boot.

 Using
 {{{
 DATABASES = {
 'default': {
 'ENGINE': 'django.db.backends.sqlite3',
 'NAME': None,
 }
 }
 }}}
 for settings (to get an in-memory database for tests), and the following
 models:
 {{{
 class A(Model):
 subcontent_type = models.ForeignKey(ContentType, null=True,
 related_name='+',
 editable=False)
 objects = Manager()

 def __unicode__(self):
 return unicode(self.pk)

 class Meta:
 ordering = ('pk',)

 class B(A): pass
 class C(B): pass
 class D(C): pass
 }}}
 The following test case fails at evaluating D:
 {{{
 from django.test import TestCase as DjangoTestCase

 class PolymorphTestCase(DjangoTestCase):
 def setUp(self):
 self.objects = [A.objects.create(), B.objects.create(),
 C.objects.create(), D.objects.create(),
 C.objects.create(), B.objects.create()]

 def test_default_manager(self):
 with self.assertNumQueries(4):
 all = list(A.objects.all())
 self.assertEqual(all, [
 A(pk=1), A(pk=2), A(pk=3), A(pk=4), A(pk=5), A(pk=6),
 ])
 all = list(B.objects.all())
 self.assertEqual(all, [
 B(pk=2), B(pk=3), B(pk=4), B(pk=5), B(pk=6),
 ])

 all = list(C.objects.all())
 self.assertEqual(all, [C(pk=3), C(pk=4), C(pk=5)])

 import pdb; pdb.set_trace()
 all = list(D.objects.all())
 self.assertEqual(all, [D(pk=4)])
 }}}

 The stack trace is:
 {{{
 Traceback (most recent call last):
   File "/path/to/tests.py", line 411, in test_default_manager
 all = list(D.objects.all())
   File "/path/python2.7/site-
 packages/Django-1.4.5-py2.7.egg/django/db/models/query.py", line 87, in
 __len__
 self._result_cache.extend(self._iter)
   File "/path/python2.7/site-
 packages/Django-1.4.5-py2.7.egg/django/db/models/query.py", line 291, in
 iterator
 for row in compiler.results_iter():
   File "/path/python2.7/site-
 packages/Django-1.4.5-py2.7.egg/django/db/models/sql/compiler.py", line
 763, in results_iter
 for rows in self.execute_sql(MULTI):
   File "/path/python2.7/site-
 packages/Django-1.4.5-py2.7.egg/django/db/models/sql/compiler.py", line
 818, in execute_sql
 cursor.execute(sql, params)
   File "/path/python2.7/site-
 packages/Django-1.4.5-py2.7.egg/django/db/backends/util.py", line 40, in
 execute
 return self.cursor.execute(sql, params)
   File "/path/python2.7/site-
 packages/Django-1.4.5-py2.7.egg/django/db/backends/sqlite3/base.py", line
 344, in execute
 return Database.Cursor.execute(self, query, params)
 DatabaseError: no such column: T5.a_ptr_id
 }}}

 the query used for D.objects.all() is:
 {{{
 'SELECT "testmodel_a"."id", "testmodel_a"."subcontent_type_id",
 "testmodel_b"."a_ptr_id", "testmodel_c"."b_ptr_id",
 "testmodel_d"."c_ptr_id" FROM "testmodel_d" INNER JOIN "testmodel_a" ON
 ("testmodel_d"."c_ptr_id" = "testmodel_a"."id") INNER JOIN "testmodel_b"
 ON ("testmodel_d"."c_ptr_id" = "testmodel_b"."a_ptr_id") INNER JOIN
 "testmodel_c" ON ("testmodel_d"."c_ptr_id" = "testmodel_c"."b_ptr_id")
 INNER JOIN "testmodel_a" T6 ON (T5."a_ptr_id" = T6."id") ORDER BY
 "testmodel_d"."c_ptr_id" ASC'
 }}}

 I had a look at the model_inheritance tests, and couldn't see any that
 were testing to the depth I'm doing there, so either I'm doing something
 wrong, SQlite is (as always) being a pain, or the tests may not go far
 enough.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 81804a: Fix 19916. Smarter tokenizing of contrib.comment's...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 81804ae474d6fe5d3ab9348cfe86ee3779473a2a
  
https://github.com/django/django/commit/81804ae474d6fe5d3ab9348cfe86ee3779473a2a
  Author: Baptiste Mispelon 
  Date:   2013-03-07 (Thu, 07 Mar 2013)

  Changed paths:
M django/contrib/comments/templatetags/comments.py
M tests/comment_tests/tests/templatetag_tests.py

  Log Message:
  ---
  Fix 19916. Smarter tokenizing of contrib.comment's templatetags arguments.


  Commit: 477d737e1e6bdf93950c8a381906925c594fac2f
  
https://github.com/django/django/commit/477d737e1e6bdf93950c8a381906925c594fac2f
  Author: Aymeric Augustin 
  Date:   2013-03-07 (Thu, 07 Mar 2013)

  Changed paths:
M django/contrib/comments/templatetags/comments.py
M tests/comment_tests/tests/templatetag_tests.py

  Log Message:
  ---
  Merge pull request #850 from bmispelon/ticket-19916

Fix 19916. Smarter tokenizing of contrib.comment's templatetags arguments


Compare: https://github.com/django/django/compare/1b81f328f4fb...477d737e1e6b

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 1b81f3: Adde two "versionadded" markers, thanks to mYk for...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1b81f328f4fb74d35a8397385fbc18aef03ac297
  
https://github.com/django/django/commit/1b81f328f4fb74d35a8397385fbc18aef03ac297
  Author: Alex Gaynor 
  Date:   2013-03-07 (Thu, 07 Mar 2013)

  Changed paths:
M docs/ref/models/fields.txt

  Log Message:
  ---
  Adde two "versionadded" markers, thanks to mYk for noticing.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] bbbd69: Added a ManyToManyField(db_constraint=False) optio...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: bbbd698c7a4dd19e6394660bece7e6e907b0a824
  
https://github.com/django/django/commit/bbbd698c7a4dd19e6394660bece7e6e907b0a824
  Author: Alex Gaynor 
  Date:   2013-03-07 (Thu, 07 Mar 2013)

  Changed paths:
M django/db/models/fields/related.py
M docs/ref/models/fields.txt
M docs/releases/1.6.txt
M tests/backends/models.py
M tests/backends/tests.py

  Log Message:
  ---
  Added a ManyToManyField(db_constraint=False) option, this allows not creating 
constraints on the intermediary models.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20000: Allow overriding `label`, `help_text` and `error_messages` for the default fields in `ModelForm`

[Django]

#2: Allow overriding `label`, `help_text` and `error_messages` for the 
default
fields in `ModelForm`
-+-
 Reporter:  loic84   |Owner:  loic84
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by carljm):

 * status:  closed => new
 * resolution:  wontfix =>
 * stage:  Unreviewed => Design decision needed


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20000: Allow overriding `label`, `help_text` and `error_messages` for the default fields in `ModelForm`

[Django]

#2: Allow overriding `label`, `help_text` and `error_messages` for the 
default
fields in `ModelForm`
-+--
 Reporter:  loic84   |Owner:  loic84
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by carljm):

 FWIW, I think this patch would be a positive improvement. It makes common
 customization cases simpler, and avoids the error-prone alternative of
 overriding the field entirely and the extra-boilerplate alternative of
 overriding `__init__` and patching fields there. I also think the supplied
 new customization points are very similar in nature to the existing
 `Meta.widgets`, and it's an odd inconsistency to have one but not the
 others. What argument is there for `Meta.widgets` that does not apply
 equally to labels, help texts, and error messages?

 In other words, if you decide to bring it up on django-developers, I am +1
 for the change.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19990: showAddAnotherPopup _popup need a fix

[Django]

#19990: showAddAnotherPopup _popup need a fix
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  contrib.admin   |  Version:  1.5
 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 aaugustin):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20001: BigAutoField for Django 1.5 (patch included)

[Django]

#20001: BigAutoField for Django 1.5 (patch included)
-+-
 Reporter:  jim@…|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:  BigAutoField |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jacob):

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


Comment:

 Duplicate of #14286; can you please add the patch over there instead?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19993: Allow accessing the resolver match and the view name on the `Request`

[Django]

#19993: Allow accessing the resolver match and the view name on the `Request`
-+-
 Reporter:  coolRR   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 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):

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


Comment:

 Unless I missed something, this is a dupe of #15695 which is fixed in 1.5.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14286: Support for BigAutoField

[Django]

#14286: Support for BigAutoField
-+-
 Reporter:  hongrich |Owner:  mmcnickle
 Type:  New feature  |   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:  1|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by jacob):

 #20001 has an alternate patch.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19999: first app not running

[Django]

#1: first app not running
-+--
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.5
 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 jacob):

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


Comment:

 This is almost certainly an error in your code. As such, the right place
 for help is the django-users mailing list or #django on IRC. If this does
 prove to be a bug in Django feel free to reopen, but please try one of
 those other venues first.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19998: loaddata --ignorenonexistent not working for XML based fixtures

[Django]

#19998: loaddata --ignorenonexistent not working for XML based fixtures
--+
 Reporter:  sigi  |Owner:  sigi
 Type:  Bug   |   Status:  assigned
Component:  Core (Serialization)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  fixtures  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by jacob):

 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19995: [Django Testing Framework] Client.get() and UnicodeEncodeError

[Django]

#19995: [Django Testing Framework] Client.get() and UnicodeEncodeError
-+-
 Reporter:  david.delassus@… |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  1.4
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  test client unicode  | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by jacob):

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


Comment:

 Closing as "needsinfo" - as Claude says without more specific info we
 can't verify if this is a bug in Django or in your code. My suspicion is
 that it's something related to your app's unicode handling, but if you've
 got more info that can help us reproduce this problem and prove it either
 way please feel free to reopen.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19993: Allow accessing the resolver match and the view name on the `Request`

[Django]

#19993: Allow accessing the resolver match and the view name on the `Request`
-+
 Reporter:  coolRR   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (URLs)  |  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 jacob):

 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19992: Put protection against unsafe redirects into `HttpResponseRedirectBase`

[Django]

#19992: Put protection against unsafe redirects into `HttpResponseRedirectBase`
---+
 Reporter:  coolRR |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  security   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by jacob):

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


Comment:

 I think this is a good idea.

 However, we do need to think a bit about whether it should be enabled by
 default. If we do, it'll break existing code, but if we don't then we're
 violating "safe by default." My preference would be something like
 `redirect(..., safe=False)` with `safe` defaulting to True, but that may
 be too backwards-incompatible.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19991: Introduce `saved_forms` property to `BaseModelFormSet`

[Django]

#19991: Introduce `saved_forms` property to `BaseModelFormSet`
-+--
 Reporter:  coolRR   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 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 jacob):

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


Comment:

 This seems somewhat domain-specific; I can't see a good reason to include
 this in Django. If you think I'm missing something, please start a thread
 on django-dev and maybe explain a bit more about your motivation?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19990: showAddAnotherPopup _popup need a fix

[Django]

#19990: showAddAnotherPopup _popup need a fix
+--
 Reporter:  riccardodivirgilio  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  1.5
 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 jacob):

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


Comment:

 I'm sorry, but I'm having trouble understanding what's being reported
 here. Can you clarify, please?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #16238: TECHNICAL_*_TEMPLATE change

[Django]

#16238: TECHNICAL_*_TEMPLATE change
-+-
 Reporter:  haras|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  1
-+-
Changes (by jacob):

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


Comment:

 There's already a mechanism
 (https://docs.djangoproject.com/en/dev/ref/urls/#django.conf.urls.handler500)
 to do custom error pages; adding a second method to do the same violates
 the Zen of Python.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19987: Basic host validation performed even when DEBUG=True

[Django]

#19987: Basic host validation performed even when DEBUG=True
---+
 Reporter:  Will Hardy |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  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 jacob):

 * needs_better_patch:   => 0
 * version:  1.5 => master
 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #4287: FloatField will not handle infinity values

[Django]

#4287: FloatField will not handle infinity values
-+-
 Reporter:  oBeattie (oliver@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  nan, infinity,   |  Needs documentation:  0
  mysql, float   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by maxime.bargiel@…):

 * keywords:  infinity, mysql, float => nan, infinity, mysql, float
 * cc: maxime.bargiel@… (added)


Comment:

 There was a similar issue with DecimalField validation (see
 https://code.djangoproject.com/ticket/) that has been fixed by simply
 rejecting float('inf') and float('nan') values during validation.

 In Django 1.4.2, custom validation needs to be implemented by the
 developers to exclude NaN and Inf, otherwise the error described in this
 ticket will occur. Nothing leads me to believe it's different in Django
 1.5. Is there a reason why FloatFields should behave differently than
 DecimalFields with regards to NaN/Inf? While I understand that it might be
 interesting to have support for NaN/Inf saved in the DB, I think it's more
 important to have a robust system until this feature is supported.

 If necessary, I'll open a new ticket.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19981: Pass request to WizardView.get_prefix

[Django]

#19981: Pass request to WizardView.get_prefix
---+
 Reporter:  joshdrake  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.formtools  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by jacob):

 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19978: Technical 500 response as HTML for Ajax request

[Django]

#19978: Technical 500 response as HTML for Ajax request
-+-
 Reporter:  rodrigopmatias@… |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Core (Other) |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  debug 500 error  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jacob):

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


Comment:

 I really don't like adding another setting for something this domain-
 specific. You can fairly easily get the same effect with a custom
 exception middleware; marking wontfix.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19977: Test database not auto-flushing

[Django]

#19977: Test database not auto-flushing
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:  needsinfo
 Severity:  Normal   | Triage Stage:
 Keywords:  test database flush  |  Unreviewed
  inconsistent   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by jacob):

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


Comment:

 Without more details of how you're running tests unfortunately we probably
 can't fix this. I understand that you can't share private info, but with
 just your description to go on it sounds like you're doing something
 rather out of the ordinary. So I'm going to close this; if you can provide
 a minimal test case that reproduces the problem please feel free to reopen
 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19967: iBooks shows error in ePub documentation

[Django]

#19967: iBooks shows error in ePub documentation
---+
 Reporter:  boloomka@… |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by jacob):

 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19966: Allow for silent or conditional loading of custom template tags

[Django]

#19966: Allow for silent or conditional loading of custom template tags
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jacob):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Someday/Maybe
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 This is a good idea in theory, but without a practical suggestion (API,
 patch, etc.) there isn't much we can do to move it forward. Moving to
 "someday"; if someone comes up with a concrete proposal we can look at
 this 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19965: Problem with __unicode__ in your tutorial

[Django]

#19965: Problem with __unicode__ in your tutorial
-+-
 Reporter:  petergoldsborough@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Uncategorized|  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:  unicode, tutorial,   | Triage Stage:  Accepted
  python 3.2 |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by jacob):

 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19955: Make contrib.comments form customizable

[Django]

#19955: Make contrib.comments form customizable
-+-
 Reporter:  dgl  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.comments |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by jacob):

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


Comment:

 I'm proposing that django.contrib.comments be deprecated and removed, so
 I'm going to place this ticket on hold until that's been decided.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19949: Cached template loader doesn't cache TemplateDoesNotExist

[Django]

#19949: Cached template loader doesn't cache TemplateDoesNotExist
--+
 Reporter:  Kronuz|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Template system   |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:  templates cache   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by jacob):

 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19947: weakref'd signal receivers may cause deadlock when gc'd

[Django]

#19947: weakref'd signal receivers may cause deadlock when gc'd
--+
 Reporter:  john@…|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  1.5
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by jacob):

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


Comment:

 Do you have some code that can reproduce this?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19944: django 1.5 is not compatible with pypy 1.9 because of django.test._doctest

[Django]

#19944: django 1.5 is not compatible with pypy 1.9 because of 
django.test._doctest
---+
 Reporter:  kmike  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.5
 Severity:  Normal |   Resolution:
 Keywords:  pypy   | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by jacob):

 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19940: Regression: setup_databases in test.simple.DjangoTestSuiteRunner doesn't handle aliases for 'default'

[Django]

#19940: Regression: setup_databases in test.simple.DjangoTestSuiteRunner doesn't
handle aliases for 'default'
---+
 Reporter:  simonpercivall |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.5-rc-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 jacob):

 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19931: Deleting from Site model won't cascade delete related models

[Django]

#19931: Deleting from Site model won't cascade delete related models
-+-
 Reporter:  james_lin|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.sites|  Version:  1.4
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  cascade, delete, | Triage Stage:
  sites  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by jacob):

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


Comment:

 There isn't anything that `Site` does differently from any other model, so
 I don't think this is a bug in Django. I'm guessing this has to do with
 whatever this "core_staticpage" table/model is, but without seeing that I
 can't be sure.

 If you can provide a minimal test case that reproduces the problem without
 this external dependency please feel free to reopen the ticket, but for
 now I'm going to close it as I'm fairly sure this doesn't represent a bug
 with Django.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19924: Some jQuery selectors in actions.js use hardcoded values instead of pulling from options.

[Django]

#19924: Some jQuery selectors in actions.js use hardcoded values instead of 
pulling
from options.
--+
 Reporter:  anonymous |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  javascript| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by jacob):

 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #15896: unittest docs say import django.utils, should be djanto.test

[Django]

#15896: unittest docs say import django.utils, should be djanto.test
---+--
 Reporter:  RoySmith   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.3
 Severity:  Normal |   Resolution:  wontfix
 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 jacob):

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


Comment:

 They really are two different things, used for two different purposes. I'm
 going to close this again; if you feel strongly, please take it to django-
 dev for 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19998: loaddata --ignorenonexistent not working for XML based fixtures

[Django]

#19998: loaddata --ignorenonexistent not working for XML based fixtures
-+-
 Reporter:  sigi |Owner:  sigi
 Type:  Bug  |   Status:  assigned
Component:  Core |  Version:  master
  (Serialization)|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  fixtures |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by sigi):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 4cccb8: Fixed #19997 -- Added custom EMPTY_VALUES to form ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4cccb85e292fea01b3459cd97d751ed35179a7b7
  
https://github.com/django/django/commit/4cccb85e292fea01b3459cd97d751ed35179a7b7
  Author: Claude Paroz 
  Date:   2013-03-07 (Thu, 07 Mar 2013)

  Changed paths:
M AUTHORS
M django/forms/fields.py
M django/forms/models.py
M django/test/testcases.py
M docs/topics/testing/overview.txt
M tests/forms_tests/tests/forms.py

  Log Message:
  ---
  Fixed #19997 -- Added custom EMPTY_VALUES to form fields

Thanks Loic Bistuer for the report and the patch.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20001: BigAutoField for Django 1.5 (patch included)

[Django]

#20001: BigAutoField for Django 1.5 (patch included)
--+--
 Reporter:  jim@… |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.5
 Severity:  Normal|   Keywords:  BigAutoField
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+--
 This week we upgraded to from 1.3 -> 1.5, and discovered BigAutoField was
 not yet included in Django. I know this issue has been referenced in a
 number of tickets over the years. In Django 1.3, we went with the
 mmcnickle approach discussed in ticket 14286
 (https://code.djangoproject.com/ticket/14286), but found this difficult to
 merge into 1.5.

 This time, we went with the approach approach suggested by pzinovkin in
 ticket 56
 (https://code.djangoproject.com/attachment/ticket/56/56_bigint.diff). It
 required tweaking to get it to work cleanly with 1.5

 Attached are patches derived from a git clone this morning.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 25ce17: Added missing method in the dummy database backend...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 25ce177e66fb0e88a39806f5a493e03f1801775a
  
https://github.com/django/django/commit/25ce177e66fb0e88a39806f5a493e03f1801775a
  Author: Aymeric Augustin 
  Date:   2013-03-07 (Thu, 07 Mar 2013)

  Changed paths:
M django/db/backends/dummy/base.py

  Log Message:
  ---
  Added missing method in the dummy database backend.



-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19999: first app not running

[Django]

#1: first app not running
-+--
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.5
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by claudep):

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


Comment:

 Please add the `--traceback` option to `manage.py syncdb` and provide us
 the full traceback. Which Python version are you running?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19954: Storing of Binary fields leads to Exceptions

[Django]

#19954: Storing of Binary fields leads to Exceptions
-+-
 Reporter:  marcel.ryser.ch@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by marcel.ryser.ch@…):

 Fit's for me, because I don't need to log the binary value, I just expect
 django to not crash when I have some binary fields in my model.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #7571: named groups in the regexes of include() urls break reverse()

[Django]

#7571: named groups in the regexes of include() urls break reverse()
--+
 Reporter:  trevor|Owner:  nobody
 Type:  Bug   |   Status:  reopened
Component:  Core (Other)  |  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
--+

Comment (by micfan):

 it seems okay now:
 {{{
 reverse('test', args=['foo', 'bar', 'bat'])
 # gives:
 '/foo/bar/bat/'
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20000: Allow overriding `label`, `help_text` and `error_messages` for the default fields in `ModelForm`

[Django]

#2: Allow overriding `label`, `help_text` and `error_messages` for the 
default
fields in `ModelForm`
-+--
 Reporter:  loic84   |Owner:  loic84
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by jezdez):

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


Comment:

 This has been previously discussed and wontfixed before. Feel free to
 raise the issue on the developer list.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20000: Allow overriding `label`, `help_text` and `error_messages` for the default fields in `ModelForm`

[Django]

#2: Allow overriding `label`, `help_text` and `error_messages` for the 
default
fields in `ModelForm`
-+--
 Reporter:  loic84   |Owner:  loic84
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by loic84):

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


Comment:

 https://github.com/loic/django/compare/ticket2

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #20000: Allow overriding `label`, `help_text` and `error_messages` for the default fields in `ModelForm`

[Django]

#2: Allow overriding `label`, `help_text` and `error_messages` for the 
default
fields in `ModelForm`
-+
 Reporter:  loic84   |  Owner:  loic84
 Type:  New feature  | Status:  new
Component:  Forms|Version:  master
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  0|  UI/UX:  0
-+
 Currently `ModelForm` requires to completely redefine fields in order to
 customize user-facing strings such as `labels`, `help_texts` and
 `error_messages`.

 This leads to a lot of boilerplate code to anyone who wants to customize
 these, but most importantly it's an error prone process. The bigger the
 ModelForm becomes, the more difficult it is to ensure functional parity
 between the `Model` fields and the `Form` fields for the critical parts
 such as blank/required, default, validators, etc.

 One shouldn't be at risk of completely breaking a form functionality in
 order to make small cosmetic changes.

 It's understood that we have to draw a line somewhere, else we would have
 field definitions in the `Meta`, but I believe that line should be drawn
 at "anything cosmetic" available through `Meta` overrides, and "anything
 functional" through fields overrides. I believe the currently provided
 `widgets` lie in between the two, so it's almost surprising that it was
 added as a convenience in a first place instead of the purely cosmetic
 options.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #17615: Unique field validation with multi-table inheritance

[Django]

#17615: Unique field validation with multi-table inheritance
-+-
 Reporter:  ungenio  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |   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 johan.holman@…):

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


Comment:

 I'm sorry didn't find the time yesterday to create a complete example, but
 here it is:

 a table with some values:

 {{{
 CREATE TABLE test_contact (
   `id` int(11) NOT NULL auto_increment,
   `subject` varchar(64) NOT NULL,
   `email` varchar(64) NOT NULL,
   PRIMARY KEY  (`id`),
   UNIQUE KEY `subject` (`subject`)
 ) ENGINE=InnoDB;
 INSERT INTO test_contact VALUES (1,'aaa','a...@test.com');
 INSERT INTO test_contact VALUES (2,'bbb','b...@test.com');
 INSERT INTO test_contact VALUES (3,'ccc','c...@test.com');
 }}}

 python manage.py shell

 {{{
 import django
 django.get_version()
 '1.5'

 from django.db import models

 class ContactSubjectManager(models.Manager):
def get_query_set(self):
return Contact.objects.values('id','subject').all()

 class ContactSubject(models.Model):
 subject = models.CharField(max_length=64, unique=True)
 objects = ContactSubjectManager()
 class Meta:
 abstract = True
 app_label = 'test'

 class ContactEmailManager(models.Manager):
def get_query_set(self):
return Contact.objects.values('id','email').all()

 class ContactEmail(models.Model):
 email = models.CharField(max_length=64)
 objects = ContactEmailManager()
 class Meta:
 abstract = True
 app_label = 'test'

 class Contact(ContactSubject,ContactEmail):
 objects = models.Manager()
 class Meta:
 app_label = 'test'
 def __unicode__(self):
 return u'%s - %s' % (self.subject, self.email)

 from django import forms

 class ContactSubjectForm(forms.ModelForm):
 subject = forms.RegexField(
 regex  = r'^[ 0-9a-zA-Z()-]+$',
 max_length = 30,
 min_length = 3,
 error_messages = {'invalid':  u'Please enter a valid subject.'})
 class Meta:
 abstract = True
 model = ContactSubject

 class ContactEmailForm(forms.ModelForm):
 email = forms.EmailField(
 error_messages = {'invalid':  u'Please enter a valid email
 address.'})
 class Meta:
 abstract = True
 model = ContactEmail

 class ContactForm(ContactSubjectForm,ContactEmailForm):
 class Meta:
 model = Contact

 f = Contact.objects.all()
 f
 [, , ]

 data = { 'subject': 'aaa' , 'email' : 'a...@test.com' }
 f = ContactForm(data)
 f.is_valid()
 False
 f.errors
 {'subject': [u'Contact with this Subject already exists.']}

 data = { 'subject': 'aaa'}
 f = ContactSubjectForm(data)
 f.is_valid()
 Traceback (most recent call last):
   File "", line 1, in 
   File "…/lib/python2.7/site-packages/django/forms/forms.py", line 126, in
 is_valid
 return self.is_bound and not bool(self.errors)
   File "…/lib/python2.7/site-packages/django/forms/forms.py", line 117, in
 _get_errors
 self.full_clean()
   File "…l/lib/python2.7/site-packages/django/forms/forms.py", line 274,
 in full_clean
 self._post_clean()
   File "…/lib/python2.7/site-packages/django/forms/models.py", line 344,
 in _post_clean
 self.validate_unique()
   File "…/lib/python2.7/site-packages/django/forms/models.py", line 353,
 in validate_unique
 self.instance.validate_unique(exclude=exclude)
   File "…/lib/python2.7/site-packages/django/db/models/base.py", line 731,
 in validate_unique
 errors = self._perform_unique_checks(unique_checks)
   File "…/lib/python2.7/site-packages/django/db/models/base.py", line 823,
 in _perform_unique_checks
 model_class_pk = self._get_pk_val(model_class._meta)
   File "…/lib/python2.7/site-packages/django/db/models/base.py", line 466,
 in _get_pk_val
 return getattr(self, meta.pk.attname)
 AttributeError: 'NoneType' object has no attribute 'attname'
 }}}

 The output should be:

 {{{
 f.is_valid()
 False
 f.errors
 {'subject': [u'Contact subject with this Subject already exists.']}
 }}}

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

Re: [Django] #15519: Custom SQL location

[Django]

#15519: Custom SQL location
-+-
 Reporter:  vzima|Owner:  vzima
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by vzima):

 * owner:  nobody => vzima
 * status:  new => assigned
 * has_patch:  0 => 1
 * version:  1.2 => master
 * needs_tests:  1 => 0


Comment:

 Pull request is backward-compatible and contains tests. I am not sure
 about documentation.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.