[Django] #24051: Tables are not created in specified tablespace when DEFAULT_TABLESPACE is specified

[Django]

#24051: Tables are not created in specified tablespace when DEFAULT_TABLESPACE 
is
specified
--+
 Reporter:  douglasjreynolds  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.7
 Severity:  Normal|   Keywords:  Tablespace
  |  model
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 When DEFAULT_TABLESPACE is specified in the project settings.py using
 database backend, django.db.backends.postgresql_psycopg2, the DDL does not
 include the 'TABLESPACE' keyword, and the table is created in the default
 PostgreSQL tablespace.

 This does not affect the INDEX tablespace.  The INDEXes are always created
 in the correct tablespace (both with just DEFAULT_TABLESPACE  and/or
 DEFAULT_INDEX_TABLESPACE).

 The patch is based off of Django 1.7.1.
 I have attached a patch to correct this issue.  It fixed the issue for me.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/059.035b3e7f4055c7d7c58a51e55d88ca76%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #4529: Allow multiple blocks with the same name in one template

[Django]

#4529: Allow multiple blocks with the same name in one template
-+-
 Reporter:  Noam Raphael |Owner:  nobody
    |
 Type:  Uncategorized|   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Design
 |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by chriskief):

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


Comment:

 Another application for repeating blocks:
 https://github.com/nalourie/django-macros

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/092.6eda716f300e118cb1e6bd46d13d8c29%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22295: admin/base.html only shows #user-tools when user is staff

[Django]

#22295: admin/base.html only shows #user-tools when user is staff
-+-
 Reporter:  wouter@… |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  user-tools admin | Triage Stage:  Accepted
  base template  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by tanner):

 * needs_better_patch:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/078.4303e586299b5d577f50597b67b152a3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #12118: in-memory test database does not work with threads

[Django]

#12118: in-memory test database does not work with threads
-+-
 Reporter:  bluebird75   |Owner:  coldmind
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  threads  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.c89119cee56cfd2ddbe5eaa3c0b5bb9e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21963: makemessages still ignores translations in templates with inline comment tags

[Django]

#21963: makemessages still ignores translations in templates with inline comment
tags
-+-
 Reporter:  Ihor Kaharlichenko   |Owner:  dzhibas
    |
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  1.6
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  makemessages,| Triage Stage:  Accepted
  template, gettext, xgettext|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/098.4a3d343a9ca7ae7985b1a25a1389cc2c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23749: Document how to get the database alias in migrations

[Django]

#23749: Document how to get the database alias in migrations
--+
 Reporter:  alfredperlstein   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  migrations dbrouter   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by iambibhas):

 I just verified that `schema_editor.connection.alias` does return the
 current connection in use, even when `--database=foobar` is used. We could
 mention this in the
 [https://docs.djangoproject.com/en/1.7/topics/migrations/#data-migrations
 data migration doc] and/or the [https://docs.djangoproject.com/en/1.7/ref
 /schema-editor/ `SchemaEditor` doc]. `SchemaEditor` doc could use a
 `Properties` section along with the `Methods` section.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.b748e4e75203a58fd467ba0e1ad4bd4e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23922: Quoting problem in RequestFactory

[Django]

#23922: Quoting problem in RequestFactory
-+-
 Reporter:  berkerpeksag |Owner:
 |  berkerpeksag
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  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
-+-

Comment (by timgraham):

 On further investigation, I think we can simply use the urlencoded version
 of # when updating  that test to use `RequestFactory` like this:
 `rf.get('/needsquoting%23')`. The test passes and works as a regression
 test as originally intended if I remove `urlquote` from
 `urlquote(new_url[1])` in `CommonMiddleware`.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.b716447fa5963d6e85f4ec5dfbd94cbf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23866: Make documentation links in error messages consistent

[Django]

#23866: Make documentation links in error messages consistent
-+-
 Reporter:  nikolas  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"ffa548fb561d4e32b42566cc67a2499a5e321944"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ffa548fb561d4e32b42566cc67a2499a5e321944"
 Updated link to CSRF docs

 Refs #23866.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.b591d274b64508cd172abb748a437faf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23866: Make documentation links in error messages consistent

[Django]

#23866: Make documentation links in error messages consistent
-+-
 Reporter:  nikolas  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"234a2e0b6bcad5536d5d6cbb398eb6b7cc4eb67e"]:
 {{{
 #!CommitTicketReference repository=""
 revision="234a2e0b6bcad5536d5d6cbb398eb6b7cc4eb67e"
 Fixed #23866 -- Harmonized refs to Django documentation from code
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.e0b37ea317ffae79b3e8656e9b52c816%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23866: Make documentation links in error messages consistent

[Django]

#23866: Make documentation links in error messages consistent
-+-
 Reporter:  nikolas  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timgraham):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.3c403bd2304e59e9399a5af10004ae85%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23328: get_javascript_catalog bug

[Django]

#23328: get_javascript_catalog bug
-+-
 Reporter:  liminspace   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  master
  Internationalization   |
 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
-+-

Old description:

> There is a project with two languages: "en" and "uk" (ukrainian).
> Default language is "uk".
>
> There are pharases:
> locale/
> en/
> djangojs.po
> msgid "Всім привіт!"
> msgstr "Hello everyone!"
> uk/
> djangojs.po
> msgid "Всім привіт!"
> msgstr ""
>
> In this case, the activated language "uk" phrase "Всім привіт!" will be
> in "en" -- "Hello everyone!".
> It's a bug, because must be "uk".
>
> I propose remove loading "en" translation as default (is better).
> Or change update method for other default language:
> {{{
> if default_locale != 'en':
> for path in paths:
> try:
> catalog = gettext_module.translation(domain, path,
> [default_locale])
> except IOError:
> catalog = None
> if catalog is not None:
> # t.update(catalog._catalog)  # remove it
> t = catalog._catalog  # <- add it
> }}}

New description:

 There is a project with two languages: "en" and "uk" (ukrainian).
 Default language is "uk".

 There are pharases:
 {{{
 locale/
 en/
 djangojs.po
 msgid "Всім привіт!"
 msgstr "Hello everyone!"
 uk/
 djangojs.po
 msgid "Всім привіт!"
 msgstr ""
 }}}
 In this case, the activated language "uk" phrase "Всім привіт!" will be in
 "en" -- "Hello everyone!".
 It's a bug, because must be "uk".

 I propose remove loading "en" translation as default (is better).
 Or change update method for other default language:
 {{{
 if default_locale != 'en':
 for path in paths:
 try:
 catalog = gettext_module.translation(domain, path,
 [default_locale])
 except IOError:
 catalog = None
 if catalog is not None:
 # t.update(catalog._catalog)  # remove it
 t = catalog._catalog  # <- add it
 }}}

--

Comment (by timgraham):

 Could you give simple steps to reproduce the issue (or attach a sample
 project)? I'm not an expert on translation or javascript_catalog, but my
 understanding is that we use `t.update(catalog._catalog)` in the code you
 mentioned so that any strings that don't have translations to the current
 locale will fallback to English.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.afe4cea1a1ded1b5e7a42665e924c223%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17494: Query Methods

[Django]

#17494: Query Methods
-+-
 Reporter:  zacharyvoase |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by oinopion):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.4e8b0f65ec9b00d66675b26940138342%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17494: Query Methods

[Django]

#17494: Query Methods
-+-
 Reporter:  zacharyvoase |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |
 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 oinopion):

 I'd say this has been addressed by `as_manager` method of QuerySet, here:
 https://docs.djangoproject.com/en/1.7/topics/db/managers/#creating-
 manager-with-queryset-methods

 I'm closing this ticket as fixed. If anyone disagrees, it can always be
 reopened 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.a4183bea63b9b81fa952ad9c9ac7f4e9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22822: Javascript en_* translations ignored if no en or en_us translations exist

[Django]

#22822: Javascript en_* translations ignored if no en or en_us translations 
exist
-+-
 Reporter:  pforth@… |Owner:  anonymous
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  1.6
  Internationalization   |
 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 timgraham):

 * component:  Translations => Internationalization
 * stage:  Unreviewed => Accepted


Comment:

 I haven't used `javascript_catalog` before, but this does seems like a
 funny restriction. If it cannot be fixed for some reason, we should at
 least document 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/078.2498b3c4ab24d4347ad0bf7474da6336%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17494: Query Methods

[Django]

#17494: Query Methods
-+-
 Reporter:  zacharyvoase |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |
 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 luzfcb):

 * cc: bnafta@… (added)


Comment:

 What is the status of this issue? It is still valid?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.7b0fd33741c9ac6d78aa423307a362e4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24028: Related instance caching causes abstraction leaks from Field.get_db_prep_save

[Django]

#24028: Related instance caching causes abstraction leaks from
Field.get_db_prep_save
-+-
 Reporter:  jdunck   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.5
  (models, ORM)  |
 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 timgraham):

 * stage:  Unreviewed => Accepted


Comment:

 Marking as accepted as depending on the results of the discussion we could
 at least document this behavior as it comes up in support channels once in
 a while.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.a25a0cbb6db1d85d9fb4f82a703f7cc5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24042: Custom AutoField fields do not work correctly on postgres

[Django]

#24042: Custom AutoField fields do not work correctly on postgres
-+-
 Reporter:  lucaswiman   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 timgraham):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.eba1e83357cbe0d8acadb7af438f46b0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23994: ModelFormsets do not check pk fields of deleted forms in validation

[Django]

#23994: ModelFormsets do not check pk fields of deleted forms in validation
---+--
 Reporter:  rtpg   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Forms  |  Version:  1.6
 Severity:  Normal |   Resolution:  duplicate
 Keywords:  formset| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timgraham):

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


Comment:

 Please reopen if so.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.9eec299cd5aab19caf9d578eda28c904%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24044: filtering by annotation executes sql function twice

[Django]

#24044: filtering by annotation executes sql function twice
-+-
 Reporter:  Tim-Erwin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  annotate filter  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * version:  1.7 => master
 * needs_docs:   => 0
 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 Not sure how difficult this might be to implement or if there are problems
 with doing so that I'm not seeing. If not, we could document the
 limitation.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.b2f0afdf77c95d79c4df46283a2f1cc8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24047: Cannot combine values_list querysets that do subqueries

[Django]

#24047: Cannot combine values_list querysets that do subqueries
-+-
 Reporter:  danni|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |
 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 timgraham):

 * needs_better_patch:   => 0
 * component:  Uncategorized => Database layer (models, ORM)
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 I am not sure if this can be made to work easily, but if not we could
 document the limitation.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.facb74a2f3a30f38d2d988e0125e73d3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24050: Downloadable documentation in various formats

[Django]

#24050: Downloadable documentation in various formats
---+--
 Reporter:  saidbakr   |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Uncategorized  |  Version:  1.7
 Severity:  Normal |   Resolution:  worksforme
 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 timgraham):

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


Comment:

 We do have PDF and ePub available for download --see the sidebar of
 https://docs.djangoproject.com/.

 If there are problems with these files, they should be tracked separately
 (e.g. #23751).

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.57736f6e202a13ca32730c67b960de27%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #12772: Allow loading template tags by fully qualified python module path

[Django]

#12772: Allow loading template tags by fully qualified python module path
-+
 Reporter:  patrys   |Owner:  patrys
 Type:  New feature  |   Status:  assigned
Component:  Template system  |  Version:  1.2-beta
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by timgraham):

 See also #2539 for discussion on the problem of namespace collisions.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.088489024e4bf483847f6ffa35622253%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24050: Downloadable documentation in various formats

[Django]

#24050: Downloadable documentation in various formats
---+
 Reporter:  saidbakr   |  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Uncategorized  |Version:  1.7
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I think that it is very important to add a downloadable versions of the
 documentation like those found for Python and others. CHM, pdf formats or
 even a packed project.

 Indeed there are some websites offers Django's documentation for download,
 but it has many issues in presentation.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.a57cfa696962be2c738e79d4d4ec9acf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.